This is the mail archive of the
mailing list for the Cygwin project.
RE: Problem with noninteractive bash initialization
- From: "Morche Matthias" <Matthias dot Morche at szm dot de>
- To: <cygwin at cygwin dot com>, "Wirawan Purwanto" <wirawan at camelot dot physics dot wm dot edu>
- Date: Thu, 20 Nov 2003 17:06:29 +0100
- Subject: RE: Problem with noninteractive bash initialization
the section "Invoked non-interactively" of "http://www.gnu.org/manual/bash-2.05a/html_mono/bashref.html#SEC62" describes the differences to the other forms of invoking bash. There is no reference to the .bashrc startup script. That states only that there is no other invoking of startupscripts than in the sections above.
~/.bashrc IS executed and that IS the prescribed behavior and is has been ever since. You can avoid this by calling "bash --norc scriptfile" or "bash --rcfile rcfile scriptfile".
But I think too, it would have been more accurate to mention the invoking of ~/.bashrc explicitly.
> -----Original Message-----
> From: Wirawan Purwanto [mailto:email@example.com]
> Sent: Thursday, November 20, 2003 4:38 PM
> To: Morche Matthias
> Cc: firstname.lastname@example.org
> Subject: RE: Problem with noninteractive bash initialization
> Yes, BUT I suppose that the shell used for executing a script is a
> NON-interactive shell, because it doesn't take _commands_
> from the user,
> rather from the script. Isn't this right? Therefore it does
> not agree with
> the prescribed behavior in the documentation.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html