Paul Eggert <[EMAIL PROTECTED]> writes:
> Andreas Schwab <[EMAIL PROTECTED]> writes:
>
>> But note that bash interprets -n as an option, which is not compliant with
>> XSI.
>
> Bash doesn't claim conformance to XSI, so that's OK as far as Bash is
> concerned.
I understand that. It doesn't even c
> Paul Eggert <[EMAIL PROTECTED]> writes:
>
> > Hence Bash can interpret \123 as an octal escape as well, if it so
> > chooses, and still conform to POSIX+XSI.
>
> But note that bash interprets -n as an option, which is not compliant with
> XSI.
Bash claims XSI conformance when in posix mode wit
Linda W <[EMAIL PROTECTED]> writes:
> I believe bash is broken in regards to using "any" number after
> "\" as an octal value. The shell specifications require the leading
> zero for an octal constant
I'm afraid this is backwards. This POSIX+XSI requirement constrains
applications, not implemen
Andreas Schwab <[EMAIL PROTECTED]> writes:
> But note that bash interprets -n as an option, which is not compliant with
> XSI.
Bash doesn't claim conformance to XSI, so that's OK as far as Bash is
concerned. Autoconf (and I assume Squid) is supposed be portable to
all POSIX hosts, not merely POS
READLINE PATCH REPORT
=
Readline-Release: 5.1
Patch-ID: readline51-004
Bug-Reported-by: Mike Stroyan <[EMAIL PROTECTED]>
Bug-Reference-ID: <[EMAIL PROTECTED]>
Bug-Reference-URL:
http://lists.gnu.org/archive/html/bug-bash/2
BASH PATCH REPORT
=
Bash-Release: 3.1
Patch-ID: bash31-013
Bug-Reported-by: Bob Rossi <[EMAIL PROTECTED]>
Bug-Reference-ID: <[EMAIL PROTECTED]>
Bug-Reference-URL:
Bug-Description:
In some cases, readline will reference fr
Phillip Susi <[EMAIL PROTECTED]> wrote:
> cat file | ( head --lines=1 ; sed -e x )
>
> I thought that head should consume the first line from the pipe, leaving
> the rest queued for sed to consume, but this does not seem to be the
> case.
head may read an arbitrary amount of data from the pi
Paul Eggert <[EMAIL PROTECTED]> writes:
> Hence Bash can interpret \123 as an octal escape as well, if it so
> chooses, and still conform to POSIX+XSI.
But note that bash interprets -n as an option, which is not compliant with
XSI.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE
I'm a bit confused by the results I'm seeing with a pipeline to a
group. I was trying to parse a text file in such a way as the first n
lines are passed straight through, and then a sed script is applied to
the rest. I thought I could do that with something like this:
cat file | ( head --lin
BASH PATCH REPORT
=
Bash-Release: 3.1
Patch-ID: bash31-012
Bug-Reported-by: Alexander Kshevetskiy <[EMAIL PROTECTED]>
Bug-Reference-ID: <[EMAIL PROTECTED]>
Bug-Reference-URL:
http://lists.gnu.org/archive/html/bug-bash/2006
On Thu, Mar 16, 2006 at 08:28:28PM -0800, laura fairhead wrote:
>
>
> Hello,
Hi Laura,
> I just found a bug that affects a number of shells (pressumably the
> code there is from the same roots) in the parser.
>
> The following code;
>
> l='eval "$l"'
> eval "$l"
>
> Which sets off an infinit
BASH PATCH REPORT
=
Bash-Release: 3.1
Patch-ID: bash31-014
Bug-Reported-by: Mike Stroyan <[EMAIL PROTECTED]>
Bug-Reference-ID: <[EMAIL PROTECTED]>
Bug-Reference-URL:
http://lists.gnu.org/archive/html/bug-bash/2006-02/msg00
Might I put forth a suggestion?
I would like to suggest that the "0" be required after a
"\" when expanding octal or hex values.
It would be consistent to allow hex values by using
"\0xHH", but it is confusingto POSIX compatible scripts
for "\1" to be accepted as an octal sequence.
Perhaps the
13 matches
Mail list logo
