Re: Absolute file-path under bash (cygwin32)

[Hawkeye <hawkeye at tcp dot com>]

> 
> Mikey wrote:
> > 
> > Not from bash.
> > 
> > vim(){
> > vim.exe `dospwd.sh $*`
> > }
> > 
> > try that,it's a little slow ;^), but I think it will work, and you only
> > have to set it up once, in .bashrc.
> 
> Once per non-cygwin executable that you want to use from within bash!
> What if "ld" marked cygwin executables with some sort of magic code?
> Then bash could fix up arguments to non-cygwin executables.

That could only ever work partially, at best.  Filenames aren't
necessarily distinct words in the argument list (consider an option
like "-I/usr/local/include"), and every word in the argument list
shouldn't necessarily be interpeted as a cygwin filename (consider
"echo dir /w >foo.bat").  The only "right" place to interpret filenames
is in the API calls made by an application.

===========================================================================
Ken Keys            hawkeye@tcp.com            http://tf.tcp.com/~hawkeye/
---------------------------------------------------------------------------
TinyFugue info: http://tf.tcp.com/~hawkeye/tf/
TF version 3.5 beta 4 for UNIX and OS/2 is available at:
  ftp://tf.tcp.com/pub/tinyfugue/ and ftp://ftp.tcp.com/pub/mud/Clients/tf/
TF mailing list: mail to majordomo@tcp.com, with body "subscribe tinyfugue"
===========================================================================
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".