delorie.com/archives/browse.cgi | search |
Sender: | rich AT phekda DOT freeserve DOT co DOT uk |
Message-ID: | <3E1813E5.F8D828C0@phekda.freeserve.co.uk> |
Date: | Sun, 05 Jan 2003 11:15:49 +0000 |
From: | Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk> |
X-Mailer: | Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586) |
X-Accept-Language: | de,fr |
MIME-Version: | 1.0 |
To: | DJGPP newsgroup <djgpp AT delorie DOT com>, "Mark E." <snowball3 AT softhome DOT net> |
Subject: | Re: Handling of TMPDIR, TEMP by various DJGPP programs |
References: | <3E14606E DOT E5B4D1A9 AT phekda DOT freeserve DOT co DOT uk> <7458-Thu02Jan2003202306+0200-eliz AT is DOT elta DOT co DOT il> <1041532689 DOT 964798 AT queeg DOT ludd DOT luth DOT se> <3E14D4D7 DOT 7847EB0C AT phekda DOT freeserve DOT co DOT uk> |
Reply-To: | djgpp AT delorie DOT com |
Hello. Richard Dawe wrote: [snip] > One thing I noticed is that bash 2.04 does not set $SHELL. If I set $SHELL > to point at the bash 2.04 executable, it does not affect the results. bash > 2.05 does set $SHELL. [snip] Hmmm. This isn't entirely true. If I invoke bash 2.05b from bash 2.04, then bash 2.05b doesn't set $SHELL to point to itself. It seems that bash 2.04 sets $SHELL to point to COMMAND.COM and then bash 2.05b keeps the setting. If I invoke bash 2.05b from an MS-DOS prompt, then it does set $SHELL to the full path of the bash 2.05b executable. Regards, -- Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |