On Saturday 25 August 2007, Chet Ramey wrote:
> Mike Frysinger wrote:
> > a side note ... if you change any of BASH_{ARGC,ARGV,LINENO,SOURCE}
> > before setting a readonly variable, bash will not spit out the error
> > message about the variable being readonly ...
> > (UID=1)
> > -bash: UID: readon
Mike Frysinger wrote:
> a side note ... if you change any of BASH_{ARGC,ARGV,LINENO,SOURCE} before
> setting a readonly variable, bash will not spit out the error message about
> the variable being readonly ...
> (UID=1)
> -bash: UID: readonly variable
> (BASH_ARGC= UID=1)
>
> this regression s
On Saturday 25 August 2007, Chet Ramey wrote:
> Mike Frysinger wrote:
> >> Bug-Description:
> >>> In some cases of error processing, a jump back to the top-level
> >>> processing loop from a builtin command would leave the shell in an
> >>> inconsistent state.
> >>
> >> this appears to break handl
Mike Frysinger wrote:
>> Bug-Description:
>>>
>>> In some cases of error processing, a jump back to the top-level
>>> processing loop from a builtin command would leave the shell in an
>>> inconsistent state.
>> this appears to break handling of read only variables in source statements
>
> this m
On Saturday 25 August 2007, Mike Frysinger wrote:
> On Friday 24 August 2007, Chet Ramey wrote:
> > BASH PATCH REPORT
> > =
> >
> > Bash-Release: 3.2
> > Patch-ID: bash32-020
> >
> > Bug-Reported-by:Ian A Watson <[EMAIL PROTECTED
On Friday 24 August 2007, Chet Ramey wrote:
>BASH PATCH REPORT
>=
>
> Bash-Release: 3.2
> Patch-ID: bash32-020
>
> Bug-Reported-by: Ian A Watson <[EMAIL PROTECTED]>
> Bug-Reference-ID:
> [EMAIL PROTECTED]> Bug-Referen
