From: mh AT mike DOT franken DOT de (Michael Hirmke)
Subject: Re: .BASHRC-problem
19 Jan 1998 16:36:40 -0800
Message-ID: <6m4yRYJ$pfB.cygnus.gnu-win32@mike.franken.de>
References: <34BE3D4E DOT 5943B5F3 AT utu DOT fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: gnu-win32 AT cygnus DOT com

Hi Juha,

[...]
>  Obviously it does not "keep" the exported variable but it also sets it all
>wrong! Where did the "//d/cygnus/b18/tcl/bin:" part come from??? I am at a
>total loss here. When I export variables, they should always be global, am I
>right? Any ideas or fixes?

Cygbus bash behaves like Unix systems do, i.e. you can only change your
current variables, if you "source" you .bashrc.
Call it with ". ~/.bashrc" and it will set your variables as you want.

>[system: NT40, intel, b18, coolview, bash-2.01]

Bye.
Michael.
--
Michael Hirmke           | Telefon +49 (911) 557999
Georg-Strobel-Strasse 81 | FAX     +49 (911) 557664
90489 Nuernberg          | E-Mail  mailto:mh AT mike DOT franken DOT de
                         | WWW     http://minimike.franken.de/
-
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".