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: Torka Noda
Subject: Re: Is it normal for `bash -s foo` not to make 1=foo available from ~/.bashrc?
Date: Tue, 28 Mar 2017 19:13:55 +0200

On Mon, 27 Mar 2017 10:04:16 -0400
Daniel Mills <address@hidden> wrote:
>
> Because you want the positional parameters set with bash -s
> to take precedence over anything set in the startup files.
> Otherwise anything in .bashrc would simply override what you
> set with bash -s.
>


They could simply be copied.

Modifying positional parameters with `set --` isn't supposed to
modify the shell's behavior live, anyway. The command line is
already parsed and options already set. So Bash should always
use the original arguments specified on the command line, to
pass them to the possible commands fed to its stdin, regardless
of whether position parameters which could be made available to
Bash initialization files are modified.



reply via email to

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