[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: greater-than + number sign = newlines in history

From: Tobias Wendorff
Subject: Re: greater-than + number sign = newlines in history
Date: Sun, 3 May 2020 15:58:59 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0

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 (doesn't matter if the end marker is quoted or not,
> doesn't seem to matter what else is on the line, if anything, with the '#'.
> (Obviousl;y I haven't tested every possibility).

Is this behavior planned or unplanned? The problem doesn't seem to
appear on Bash 4 (Debian Jessie, Cygwin on Windows).

> If the history entry is used (up-arrow, return) to replay the command, a
> new entry will be made with extra \n chars in it (the repeated command
> is not seen as a duplicate - I have the var set to have dup commands
> saved just once).

It's also stored in Bash's history file.

On IRC, an user gave me the hint to set `shopt -s lithist`, which seems
to work. The documentation of `lithist` is very ambiguous, so I don't
know the downside of this option.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]