Re: Q: bash parameter expansion

2008-04-21 Thread Andreas Schwab
"Dmitry V. Levin" <[EMAIL PROTECTED]> writes: > I wonder whether such difference in parameter expansion is valid: > > $ env -i sh -c 'fun() { echo "[${*#foo }]"; }; fun foo bar' > [foo bar] > $ env -i sh -c 'fun() { echo "[${*#foo}]"; }; fun foo bar' > [ bar] Works as documented: `${PARAMETER#WO

Re: Q: bash parameter expansion

2008-04-21 Thread Dmitry V. Levin
On Mon, Apr 21, 2008 at 10:06:10AM +0200, Andreas Schwab wrote: > Dmitry V. Levin writes: > > > I wonder whether such difference in parameter expansion is valid: > > > > $ env -i sh -c 'fun() { echo "[${*#foo }]"; }; fun foo bar' > > [foo bar] > > $ env -i sh -c 'fun() { echo "[${*#foo}]"; }; fun

Re: Q: bash parameter expansion

2008-04-21 Thread Chet Ramey
Dmitry V. Levin wrote: On Mon, Apr 21, 2008 at 10:06:10AM +0200, Andreas Schwab wrote: Dmitry V. Levin writes: I wonder whether such difference in parameter expansion is valid: $ env -i sh -c 'fun() { echo "[${*#foo }]"; }; fun foo bar' [foo bar] $ env -i sh -c 'fun() { echo "[${*#foo}]"; };

bash PO file typos/query

2008-04-21 Thread Clytie Siddall
Hello :) I have just translated the file bash-3.2 for the Translation Project. In doing so, I've encountered the following typos, which I thought you might like to weed out in a future release. 1. duplicate word #: builtins/caller.def:133 msgid "Without EXPR, returns returns \"$line $