On 1/15/13 11:30 AM, DJ Mills wrote:
> I believe that's referring to var=value command, as in the syntax to export
> a variable into "command"s environment.
>
> readonly a=3
> a=2 echo foo
I believe this is the bug:
set -o posix
readonly a=0
a=1 command : 2>/dev/null # or use true in place of c
On 01/16/2013 01:59 AM, Dan Douglas wrote:
Oops nevermind, I see the issue now. Couldn't reproduce here either. Neither
with compat modes nor the real versions.
Thanks for your help any way
it seems to remain a problem
Oops nevermind, I see the issue now. Couldn't reproduce here either. Neither
with compat modes nor the real versions.
--
Dan Douglas
On Tuesday, January 15, 2013 11:51:28 AM Greg Wooledge wrote:
> On Tue, Jan 15, 2013 at 11:30:39AM -0500, DJ Mills wrote:
> > I believe that's referring to var=value command, as in the syntax to export
> > a variable into "command"s environment.
> >
> > readonly a=3
> > a=2 echo foo
>
> I thought
On Tue, Jan 15, 2013 at 11:30:39AM -0500, DJ Mills wrote:
> I believe that's referring to var=value command, as in the syntax to export
> a variable into "command"s environment.
>
> readonly a=3
> a=2 echo foo
I thought that was what it meant, too, but I couldn't reproduce the "bug"
that it was c
On Mon, Jan 14, 2013 at 10:03 PM, douxin wrote:
> Hello:
> i am from China and i am working on investigating the difference
> between bash V4.2 and V4.1
>
> according to official log there is a new feature description
>
> "Posix mode shells no longer exit if a variable assignment err
Hello:
i am from China and i am working on investigating the difference
between bash V4.2 and V4.1
according to official log there is a new feature description
"Posix mode shells no longer exit if a variable assignment error
occurs with an assignment preceding a command that is n
