Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2
-fdebug-prefix-map=/build/bash-2bxm7h/bash-5.0=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wno-parentheses$
uname output: Linux inwis-woh
Date:Sun, 3 May 2020 08:28:30 +0200
From:Tobias Wendorff
Message-ID:
| When creating a here document containing the greater-than sign followed
| by number sign, newlines get added to Bash history:
The example given showed a less than, rather than greater than,
b
Am 03.05.2020 um 14:50 schrieb Robert Elz:
> The example given showed a less than, rather than greater than,
> but that turns out to be irrelevant, it is the '#' that is triggering
> this.
Whoops, sorry.
> Any line in a here doc that contains a # gets an extra \n appended
> to it in history (does
Date:Sun, 3 May 2020 15:58:59 +0200
From:Tobias Wendorff
Message-ID: <0c8f8899-0421-0aa7-2ecd-2167018c3...@gmx.de>
| Is this behavior planned or unplanned? The problem doesn't seem to
| appear on Bash 4 (Debian Jessie, Cygwin on Windows).
Not for me to say, but I
I reported this 5 months ago:
https://lists.gnu.org/archive/html/bug-bash/2019-10/msg00093.html
3 Mayıs 2020 Pazar tarihinde Tobias Wendorff yazdı:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -g -O2
Greg Wooledge writes:
> Perl is a programming language. It makes sense that perl would evolve
> in a way that makes it more useful for writing programs.
>
> Bash, on the other hand, is first and foremost a *shell*. It's designed
> to act as an interface for executing commands, either interactive
This patch amends bash.1 to explain the sequence of places the
inputrc is found (INPUTRC, ~/.inputrc, /etc/inputrc) in the same
way as in readline.3 and bash.info.
The existing text had me puzzled for a bit, as it seemed to say
that /etc/inputrc wasn't part of Bash's own behavior, even though
I kn
