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

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: greater-than + number sign = newlines in history
Date	2020-05-04 09:11 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.2062.1588597924.3066.bug-bash@gnu.org> (permalink)
References	<bb08b099-59bd-5f04-4074-bbc046e99c6c@gmx.de> <11091.1588510206@jinx.noi.kre.to> <0c8f8899-0421-0aa7-2ecd-2167018c3924@gmx.de> <1c0e2e58-f379-6fa9-dbea-27c82721bbc3@case.edu>

Show all headers | View raw

On 5/3/20 9:58 AM, Tobias Wendorff wrote:

> 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.

It means that the history list contains the command as you typed it, with
bash in command-oriented history mode trying its best to keep multi-line
commands in the same history entry.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: greater-than + number sign = newlines in history Chet Ramey <chet.ramey@case.edu> - 2020-05-04 09:11 -0400

csiph-web