"The PATH problem"

[Christopher Faylor]

On Fri, Jan 12, 2001 at 09:33:06AM -0500, Earnie Boyd wrote:
>Soren Andersen wrote:
>> 
>> On 12 Jan 2001, an entity purporting to be Schaible, Joerg [Schaible, Joerg
>> <Joerg.Schaible@gft.com>] wrote [regarding RE: "The PATH problem"]
>> 
>> > Hi Soren,
>> >
>> > >Cygwin doesn't allow modification or unset on the PATH variable after
>> > >login, so it has to be set right from 'Doze before bash gets fired up, no?
>> >
>> > Who has told you that? This is simply not true, but it depends on the shell
>> > you're using.
>> 
>> I am *quite* sure I just read it in documentation, but I am sorry, I have
>> been multitasking at least a half-dozen projects for days now, and I do not
>> have a pointer to cite to the location of this statement.
>> 
>> I exhaustively tried to alter my PATH inside bash (using statements
>> identical to what you cited) before I found the documentary confirmation
>> that it doesn't work.
>> 
>>    "YMMV".
>> 
>
>YMMV???  Joerg is correct.  This is an impartial nature of the shell,
>all shells, including command.com and cmd.exe.  I don't think that your
>systems are a special case, but YMMV.

Right.  There is *no* documentation which says that setting your PATH
inside of bash doesn't work.  This is simply not true.

What kind of UNIX emulation would Cygwin be if you couldn't modify your
PATH???

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple