On 11/05/2010 12:17 PM, Jonathan Nieder wrote:
Hi,
Current shells differ in how they split words in the arguments to
'export' and similar builtins:
A. Costa wrote:
% foo() { export x=$@ ; }
% foo -f --c
export: 4: --c: bad variable name
% echo $?
Eric Blake wrote:
...
I would love to require altered word splitting behavior for export and
readonly (the standard doesn't touch local yet). In fact, it has
independently come up on the GNU coreutils development lists that the
standard is long overdue for requiring shells to support 'local'
cc: agco...@gis.net 381...@bugs.debian.org
Subject: Re: Word splitting in 'export' arguments (Re: bash: expands $@ within
double-quotes inconsistently)
Hi,
Current shells differ in how they split words in the arguments to
'export' and similar builtins:
A. Costa wrote:
Eric Blake wrote:
Would you like me to take a stab at writing the bug report(s) to add
support for 'local' in the next revision of the standard, and to require
the ksh/bash behavior of suppressing word splitting after shell builtins
that take arguments which can modify the current set of
On 11/08/2010 03:09 PM, Jonathan Nieder wrote:
Eric Blake wrote:
Would you like me to take a stab at writing the bug report(s) to add
support for 'local' in the next revision of the standard, and to require
the ksh/bash behavior of suppressing word splitting after shell builtins
that take
Hi,
Current shells differ in how they split words in the arguments to
'export' and similar builtins:
A. Costa wrote:
% foo() { export x=$@ ; }
% foo -f --c
export: 4: --c: bad variable name
% echo $?
2
It seems like it should be standard code.
6 matches
Mail list logo
