Mail Archives: cygwin/2001/10/02/15:15:14
On Tue, Oct 02, 2001 at 09:01:32PM +0200, Ehud Karni wrote:
>On Tue, 2 Oct 2001 13:44:19 -0400, Christopher Faylor <cgf AT redhat DOT com> wrote:
>>
>> On Tue, Oct 02, 2001 at 10:33:36AM -0400, Matt Landau wrote:
>> >At 05:37 AM 10/2/2001, David Starks-Browning wrote:
>> >>If your non-Cygwin application (like Emacs) requires HOME be set in a
>> >>non-Cygwin way, then don't start emacs from your Cygwin bash shell.
>> >
>> >Let me clarify the problem.
>> >
>> >Emacs doesn't care what $HOME is set to, it cares what path it sees on
>> >the command line. The issue is that bash, by default, expands
>> >~/filename to a posix-style path, resulting in commands like "emacs
>> >/c/users/matt/.bashrc", which doesn't work for any non-Cygwin program.
>> >
>>
>> It is unlikely that anyone who is working on cygwin development, a large
>> part of which is devoted to providing unix path handling, is going to be
>> overly interested in modifying bash to handle MS-DOS paths.
>>
>> So, as has been suggested elsewhere, the best solution is to inspect the
>> bash source code and provide a fix. I can't speak for anyone else but I
>> know that I, personally, have no interest in making bash work with
>> MS-DOS paths.
>
>Cygwin has a small program cygpath.exe for this purpose. I wrote a little
>bash script that I think work around the problem. I call it run-win.sh and
>you run the M$Windows command thru it. e.g. run-win.sh emacs ~/.bashrc
You left out the part of my email which actually mentions how to solve this
problem. There should be no need for cygpath in this case.
Just set the HOME environment variable to a UNIX path. It should work fine
with native windows apps since HOME will be translated back to MS-DOS format
prior to executing the program. That's how cygwin works.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -