Re: [Mingw-msys] Question about translation of paths from shell vars

[Andrew B. <ab...@cs...>]

On Friday, April 26, 2002, at 03:57  AM, Earnie Boyd wrote:

> Andrew Begel wrote:
>>
>> I wrote a path into a bash shell var:
>>
>> #!/bin/sh
>>
>> LOADPATH=/h/foo/bar
>>
>
> What happens if you LOADPATH=h:/foo/bar?

If I change LOADPATH to a DOS path like that, then it works fine. 
Unfortunately, my scripts are a bit more complicated. There's a first 
script that does:

export HARMONIA_HOME /h/harmonia/src  (actually uses pwd and ls and 
friends to figure it out)

exec $HARMONIA_HOME/second-script.sh

and the second script does

LOADPATH=$HARMONIA_HOME/lib/xemacs

so, it's not so easy to fix without munging this (supposedly) 
platform-independent script (should act the same on windows and unix).

>
>> and then I used it in an exec string:
>>
>> exec "/e/xemacs/xemacs-21.4/src/xemacs" -eval \
>>     "(setq load-path (cons \"$LOADPATH\" load-path))" $rest
>>
>> When I look at what XEmacs shows for the value of load-path, it's in
>> MSYS form (posix-ish), rather than Windows (drive letter, colon, path).
>>
>> How can I fix this? I want the path to be passed to exec as a Windows
>> path, not an MSYS one.
>>
>
> If the above suggestion doesn't work for you then I'll supply a
> different workaround.  Eventually the environment variables will be
> converted as well.

What's the other workaround? I did try (getenv "LOADPATH") from within 
XEmacs, but this got the same msys path too.

How will convert the env variables? theoretically, I could have a script 
that wants to concat two env variables together to form a new msys path; 
how would you know not to convert them then? or would it not matter 
unless you were messing with the / at the beginning of the first path?

andrew

>
> Earnie.
>

-----------
Andrew Begel
Ph.D. Candidate
Computer Science Division
University of California, Berkeley