Date:Sun, 13 Feb 2022 22:38:47 -0600
From:Dennis Williamson
Message-ID:
| It occurs to me that the -r option of read is related.
It is - if a backslash is the final char of input (ie: no newline follows)
when read is used without -r, what happens to that \ will
On Sun, Feb 13, 2022, 9:48 PM Robert Elz wrote:
> Date:Sun, 13 Feb 2022 21:38:19 -0500
> From:"Dale R. Worley"
> Message-ID: <87o83a895w@hobgoblin.ariadne.com>
>
> | The two a-priori plausable behaviors are for the backslash to be taken
> | literally (which
Date:Sun, 13 Feb 2022 21:38:19 -0500
From:"Dale R. Worley"
Message-ID: <87o83a895w@hobgoblin.ariadne.com>
| The two a-priori plausable behaviors are for the backslash to be taken
| literally (which is what happens) or for it to vanish as some sort of
|
vzvz...@gmail.com writes:
> The mentioned bug is indeed fixed by this change. However, in case of
> another edge case following new behaviour is observable:
>
> $ bash -c 'echo \'
> \
> $ # backslash appears on output
It's an interesting case, since the command that Bash is executing is
On Sun, Feb 13, 2022, 22:23 wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -g -O2
> -fdebug-prefix-map=/build/bash-a6qmCk/bash-5.0=. -fstack-protector-strong
> -Wformat -Werror=format-security
On 2/12/22 4:11 AM, Mihai Moldovan wrote:
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-gcc
Compilation CFLAGS: -march=native -mtune=native -Wall -pipe -g3 -ggdb3 -gdwarf-4
-O2
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fdebug-prefix-map=/build/bash-a6qmCk/bash-5.0=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wno-parentheses -Wno-format-security
uname
On 2/12/22 1:24 PM, David Hobach wrote:
I guess 99% of programmers would either expect "Finished" to be printed
or some syntax error.
Well, 99% of shell programmers will (hopefully ;-) ) put a blank between
"{" and "echo" in the line
foo="$(testCode)" || {echo "foo";}
Yes, the interesting
On 2/12/22 5:20 PM, David Hobach wrote:
Thanks a lot for the detailed explanations, much appreciated!
So essentially it's no bug - just a rather uncommon choice of keywords.
I still don't agree with that choice since it can be abused to somewhat
hide code in pull requests to less experienced
