Got it. Thanks. :)
On Wed, Dec 23, 2020 at 10:19 AM Chet Ramey wrote:
> On 12/23/20 11:10 AM, Travis Everett wrote:
> > I think I'm missing or misreading something. If I understood, the
> > assignment and expansion errors are both shell errors that should have
> the
> > same exit behavior?
> >
On 12/23/20 11:10 AM, Travis Everett wrote:
I think I'm missing or misreading something. If I understood, the
assignment and expansion errors are both shell errors that should have the
same exit behavior?
But I see the assignment error ending the list and returning to the top
level, and the
I think I'm missing or misreading something. If I understood, the
assignment and expansion errors are both shell errors that should have the
same exit behavior?
But I see the assignment error ending the list and returning to the top
level, and the expansion exiting the script:
readonly sigh=1
if
On 12/23/20 10:34 AM, Ilkka Virta wrote:
Regardless, my point is that "as with word splitting" is not exactly true,
and misleading statements
have no place in documentation if it's meant to be of any use to a user who
needs the documentation
to begin with.
I'll look at doing something for
Regardless, my point is that "as with word splitting" is not exactly true,
and misleading statements
have no place in documentation if it's meant to be of any use to a user who
needs the documentation
to begin with.
In any case, adding "A backslash can be used to escape a delimiter or a
newline."
On 12/22/20 12:21 PM, Travis Everett wrote:
I don't understand what distinction you're trying to make; any example you
can give?
I added an extra near-copy of the script to the gist replacing the
assignment with unset
`unset' is a different thing. It's a special builtin, so POSIX requires a
On 12/21/20 11:28 PM, Travis Everett wrote:
Bash Version: 5.
0Patch Level: 18
Release Status: release
Description:
While trying to intentionally trap/ignore EXIT in a sourced script, I
noticed that I couldn't keep it from exiting when it tried to overwrite
PATH, which I had set to
On 12/22/20 9:13 AM, Ilkka Virta wrote:
Arguably it's a bug that 'help read' doesn't mention the effect of
backslashes, other than what can be extrapolated from the description of
-r. It only says "The line is split into fields _as with word splitting_",
but word splitting doesn't recognize
