On Sun, Jan 26, 2003 at 06:30:23PM -0500, Larry Hall (RFK Partners, Inc) wrote: >At 05:55 PM 1/26/2003, David Christensen wrote: >>However, I still say there is a Bash/Cygwin bug -- if Bash/Cygwin reads >>the Windows HOME environment variable and gets "%USERPROFILE%", it >>should evaluate that to get "C:\Documents and Settings\dpchrist" and >>set my home directory to "/cygdrive/c/Documents and Settings/dpchrist". >>Starting in, and setting HOME to, "/usr/bin/%USERPROFILE%" is bad. > >Sorry, I can't reproduce this bug with Cygwin 1.3.17 or 1.3.19 (and >latest bash). If I set HOME="%USERPROFILE%" at my command (cmd) >prompt, start bash with "bash --login -i", and "echo $HOME", I get >exactly what I expect. I see the name of the directory specified by >"%USERPROFILE%". If I "cd ~", I get there too. Can you provide any >insight as to how you get HOME set to "/usr/bin/%USERPROFILE%" in bash? >This seems to be the root of the problem you saw but I can't reproduce >it.
I think the assumption is that bash should be doing expansion of any %DELIMITED% variables it sees in the environment. It is possible to set an environment variable to %SOMETHING% via the control panel, I think. And, the %SOMETHING% will not be expanded as it would when you set HOME above. bash just reads the environment variables directly via a Win32 API. It doesn't and shouldn't be doing any % expansion. 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/
