On 9/9/17 8:10 PM, Martijn Dekker wrote:
> The bug test suite in my modernish shell library exposed a bug in the
> current bash development snapshot. As far as I've been able to trace,
> the following bug was introduced by bash-snap-20170620 (commit
> d7d836dfc55b937f463f601ba5117d6442053089).
Yes
2017-09-10 14:56:50 -0400, Chet Ramey:
> On 9/10/17 11:11 AM, Stephane Chazelas wrote:
> > When running bash as:
> >
> > bash -s foo bar
> >
> > "$@" is not available inside .bashrc. Same for $ENV (POSIX
> > conformance issue?), $BASH_ENV, or ~/.bash_profile (with bash
> > --login -s).
> >
> > I
On 9/8/17 4:18 AM, Philipp Sasse wrote:
> Executing something like
> echo "foo
> bar" | sed '/foo/!d'
> results in an error. Apparently the history expansion considers only
> quoting characters on the same input line, so the closing double quote is
> taken as opening double quote, es
On 9/10/17 11:11 AM, Stephane Chazelas wrote:
> When running bash as:
>
> bash -s foo bar
>
> "$@" is not available inside .bashrc. Same for $ENV (POSIX
> conformance issue?), $BASH_ENV, or ~/.bash_profile (with bash
> --login -s).
>
> In the case of bash -c, that also affects $0.
Bash has alwa
When running bash as:
bash -s foo bar
"$@" is not available inside .bashrc. Same for $ENV (POSIX
conformance issue?), $BASH_ENV, or ~/.bash_profile (with bash
--login -s).
In the case of bash -c, that also affects $0.
ksh88, ksh93, mksh, dash, zsh, posh, busybox sh can access $@ in
$ENV
Reprod
