This is the mail archive of the
mailing list for the Cygwin project.
Problem with noninteractive bash initialization
- From: Wirawan Purwanto <wirawan at camelot dot physics dot wm dot edu>
- To: cygwin at cygwin dot com
- Date: Wed, 19 Nov 2003 15:47:17 -0500 (EST)
- Subject: Problem with noninteractive bash initialization
How should a noninteractive bash begin (i.e. for executing a script)?
Should bash read init files like ~/.bashrc, ~/.bash_profile, or
/etc/profile? According to bash documentation on
NO initialization files would be read. But cygwin's bash (version
2.05b.0(1)-release) DOES reads and executes ~/.bashrc BEFORE executing the
actual script itself. Why is this? Is this not a deviation from the
prescribed behavior, or what?
<---- long explanation
To find out whether the .bashrc is executed, simply create a trivial
script "xyz". For simplicity let's assume it contains only an echo
$ bash -x xyz
According to BASH standard, it should result in the following printout:
+ echo 'Hellow'
This is what happens on my linux box (a Mandrake 9.1, with bash version
2.05b.0(1)-release also). But in my cygwin window [under Windows 2000], it
spits out lots of initialization commands from ~/.bashrc before finally
executing the echo "Hellow" statement.
end long explanation ---->
Can somebody explain what's wrong with this?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html