...is at
https://www.netbsd.org/~agc/bozo-20160517.diff
Does anyone have any objections?
Thanks,
Alistair
Oh, and while I am here, another possible change, especially if we are
doing things only in posix mode, is in the way the ! word is processed.
In posix, ! is allowed in exactly one place (and there can be only one ! there).
That one place is before a pipeline (note that all simple commands
are al
Date:Tue, 17 May 2016 16:05:57 + (UTC)
From:chris...@astron.com (Christos Zoulas)
Message-ID:
| I think we should probably have "strict posix mode" for this (via an
| environment variable or command line switch?) ...
That we have already. (Both variants, an
On Tue, May 17, 2016 at 04:05:57PM +, Christos Zoulas wrote:
> In article <17323.1463479...@andromeda.noi.kre.to>,
> Robert Elz wrote:
> >The posix shell standard does not allow empty sub-shells, or command
> >groups. That is, both
> >( )
> >and
> >{ }
> >(even if you write
In article <17323.1463479...@andromeda.noi.kre.to>,
Robert Elz wrote:
>The posix shell standard does not allow empty sub-shells, or command
>groups. That is, both
> ( )
>and
> { }
>(even if you write the latter as "{ ; }" though it turns out the ';'
>there is not actually required,
The posix shell standard does not allow empty sub-shells, or command
groups. That is, both
( )
and
{ }
(even if you write the latter as "{ ; }" though it turns out the ';'
there is not actually required, as it, or a \n, usually is before '}')
are both syntax errors.
NetBSD's shel
