From: "deckerben" Newsgroups: comp.os.msdos.djgpp References: <3d2f4d48$0$28398$9b622d9e AT news DOT freenet DOT de> <3D2F5A9A DOT 61162235 AT phekda DOT freeserve DOT co DOT uk> Subject: Re: _bashrc somewhere else? Date: Sat, 13 Jul 2002 04:44:38 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Lines: 31 Message-ID: <3d2f936f$0$15191$9b622d9e@news.freenet.de> NNTP-Posting-Host: 213.7.10.232 X-Trace: 1026528112 news.freenet.de 15191 213.7.10.232 X-Complaints-To: abuse AT freenet DOT de To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Richard Dawe" wrote in message news:3D2F5A9A DOT 61162235 AT phekda DOT freeserve DOT co DOT uk... > "When bash is started non-interactively, to run a shell > script, for example, it looks for the variable BASH_ENV in > the environment, expands its value if it appears there, > and uses the expanded value as the name of a file to read > and execute. Bash behaves as if the following command > were executed: > if [ -n "$BASH_ENV" ]; then . "$BASH_ENV"; fi > but the value of the PATH variable is not used to search > for the file name." I did read that. So what I understood from that is that I should define %BASH_ENV% like %DJGPP% in the DOS environment. That is what what I think I have been trying to do. What could be wrong with: set BASH_ENV=D:\user\DJGPP\etc\profile ...when D:\user\DJGPP\etc\profile is exactly the same file sas the %HOME%\_bashrc, which works for me? Maybe I misunderstood the man page? Ben