On Tue, 15 Aug 2023 at 01:41, Chet Ramey wrote:
> On 8/11/23 4:19 PM, Martin D Kealey wrote:
> > I think it would be helpful to start this sentence with "The selected
> > line…", to differentiate from the line just entered containing a "!".
>
> It's both, actually. The line being expanded is brok
So this behavior of `bash`s seems like a bug to me. I stumbled across it by
accident.
>From within a stack of x3 functions called from a case within a for loop,
when trying to assign a value to a read-only variable, `printf` and `read`
both fail with exit codes of 1, and the functions, `case` and
On Tue, Aug 15, 2023 at 8:57 PM Wiley Young wrote:
> So this behavior of `bash`s seems like a bug to me. I stumbled across it by
> accident.
>
> From within a stack of x3 functions called from a case within a for loop,
> when trying to assign a value to a read-only variable, `printf` and `read`
>
At 2023-08-15T23:24:31-0500, Dennis Williamson wrote:
> From man bash:
>
> readonly [-aAf] [-p] [name[=word] ...]
> The given names are marked readonly; the values of these
> names may not be changed by subsequent assignment. If the -f option is
> supplied, the functions
>
I find it usefull and keep it :-) Thanx tons.
readonly [-aAf] [-p] [name[=word] ...]
> The given names are marked readonly; the values of these
> names
> may not be changed by subsequent assignment. If the -f
> option
> is supplied, the funct
