Re: Bash Environment (Was: Bash history?)

["Wei Ku" <weiku at utkux dot utcc dot utk dot edu>]

 Only th login shell will read the .bash_profile. To run bash as a login
shell try:
bash -login

Wei ku


-----Original Message-----
From: Michael A. Chase <mchase@ix.netcom.com>
To: Sergey Okhapkin <sos@prospect.com.ru>; gnu-win32@cygnus.com
<gnu-win32@cygnus.com>; 'Andy Piper' <andyp@parallax.co.uk>
Date: Tuesday, September 16, 1997 8:49 PM
Subject: Bash Environment (Was: Bash history?)



>I have similar problems.  It appears that the only environment variable
>that gets changed from MSDOS form to UNIX form is $PATH.  All the others
>keep their backslashes and semicolons.
>
>I put code in /etc/profile to fix the environment (attached).
>Unfortunately, I have never seen /etc/profile run by default so I added a
>check for it to .bashrc (which does work) to run both /etc/profile and
>.bash_profile.
>
>Is there something else I should be doing to get the correct environment
>at bash startup?
>
>Mac :})
>-----Original Message-----
>From: Sergey Okhapkin <sos@prospect.com.ru>
>To: gnu-win32@cygnus.com <gnu-win32@cygnus.com>; 'Andy Piper'
><andyp@parallax.co.uk>
>Date: Sunday, September 07, 1997 22:02
>Subject: RE: Bash history?
>
>
>
>>Andy Piper wrote:
>>> 1) ~ seems to be interpreted wrongly. If I do `cd ~' I get:
>>> bash.exe: C:WINNTProfilesandyp: No such file or directory
>>> cd $HOME works fine. Somehow the /'s are getting stripped out.
>>
>>I'm sure, there are backslashes instead of slashes in your HOME env.
>var. Set HOME to
>>c:/WINNT/Profiles/andyp.
>>
>>>
>>> 2) History is not preserved between sessions. Although bash
>>> writes out a history file - .bash_history - correctly. It is not read
>when
>>
>>Fix the first problem, and the second one should came out.
>>
>>--
>>Sergey Okhapkin, http://www.lexa.ru/sos
>>Moscow, Russia
>>Looking for a job
>
>

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".