bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is it normal for `bash -s foo` not to make 1=foo available from ~/.b


From: Chet Ramey
Subject: Re: Is it normal for `bash -s foo` not to make 1=foo available from ~/.bashrc?
Date: Tue, 28 Mar 2017 10:29:57 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0

On 3/27/17 8:32 AM, Torka Noda wrote:
> On Sat, 25 Mar 2017 15:33:47 -0400
> Chet Ramey <address@hidden> wrote:
>>>
>>> Is it normal for Bash positional parameters not to be
>>> available from ~/.bashrc during initialization?  
>>
>> Yes. Bash has always worked like this.  The startup files are
>> read before the positional parameters are assigned.
>>
> 
> 
> For any particular reason?

I can't remember whether there was any particular rationale; the decision
was made almost 30 years ago.  Brian and I certainly never talked about it.
Is there a compelling reason to change it now, since there are other ways
to accomplish it?

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]