This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Problem with noninteractive bash initialization

Perhaps.  But it's more likely to be something local in your environment.  
As stated in <>, your 
problem is not reproducible generally so you're going to need to dig a little 
deeper to find its source.


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.
>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 []
>> > Sent: Wednesday, November 19, 2003 9:47 PM
>> > To:
>> > 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
>> > 
>> > ,
>> > 
>> > NO initialization files would be read. But cygwin's bash (version
>> ..
>Unsubscribe info:
>Problem reports:

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]