Subject: RE: Problem with noninteractive bash initialization
From: Larry Hall <[email-masked]>
To: Wirawan Purwanto <[email-masked]>, Morche Matthias <[email-masked]>
Cc: [email-masked]
Date: Thu, 20 Nov 2003 10:45:08 -0500

Perhaps.  But it's more likely to be something local in your environment.  
As stated in <http://cygwin.com/ml/cygwin/2003-11/msg00787.html>, your 
problem is not reproducible generally so you're going to need to dig a little 
deeper to find its source.

Larry

At 10:38 AM 11/20/2003, Wirawan Purwanto you wrote:
>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.
>
>Wirawan
>
>On Thu, 20 Nov 2003, Morche Matthias wrote:
>
>> Dunno where Your read, but the document You referenced says: "When an
>> interactive shell that is not a login shell is started, Bash reads and
>> executes commands from `~/.bashrc', if that file exists."
>> 
>>   matthias
>> 
>> 
>> > -----Original Message-----
>> > From: Wirawan Purwanto [mailto:[email-masked]]
>> > Sent: Wednesday, November 19, 2003 9:47 PM
>> > To: [email-masked]
>> > Subject: Problem with noninteractive bash initialization
>> > 
>> > 
>> > Hi,
>> > 
>> > 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
>> > 
>> >   http://www.gnu.org/manual/bash-2.05a/html_mono/bashref.html#SEC62 ,
>> > 
>> > NO initialization files would be read. But cygwin's bash (version
>> ..
>> 
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Problem reports:       http://cygwin.com/problems.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/