From: crd AT inversenet DOT com (Craig Dickson) Subject: Fw: bash and ~ 27 Feb 1998 16:02:58 -0800 Message-ID: <00cc01bd43d8$333a5620$168cdad0.cygnus.gnu-win32@crd.inversenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit To: I sent this a few days ago, but it hasn't shown up in my inbox, so I think it may have gotten lost in the recent Cygnus power failure. My apologies to anyone who is receiving it for a second time. Craig Pierre A. Humblet wrote: >The real fix is to have emacs understand "/users/pierre" ot really, because this is more generally a problem of interfacing cygwin to non-cygwin applications. It seems sort of silly to me to suggest that all other apps should understand cygwin's insistence on pretending that Win32 is Unix. Another approach to this problem might be to have cygwin translate the environment for all child processes to use native paths (e.g., translate /users/pierre to c:\users\pierre or whatever it's mounted as), and have cygwin programs perform the reverse translation during their C library initialization (before main() gets called). Thus, any non-cygwin app will see what it expects (Win32 drive letters and paths), and any cygwin app will also see what it expects (Unix-style paths based on cygwin's mount points), whether launched from bash or a non-cygwin shell. Since the environment is fairly small and modern machines are fairly fast, this should not add significant performance overhead. Craig - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".