Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Robert Elz Newsgroups: gnu.bash.bug Subject: Re: greater-than + number sign = newlines in history Date: Sun, 03 May 2020 21:48:51 +0700 Lines: 43 Approved: bug-bash@gnu.org Message-ID: References: <0c8f8899-0421-0aa7-2ecd-2167018c3924@gmx.de> <11091.1588510206@jinx.noi.kre.to> <16697.1588517331@jinx.noi.kre.to> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1588517361 25362 209.51.188.17 (3 May 2020 14:49:21 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bug-bash@gnu.org To: Tobias Wendorff Envelope-to: bug-bash@gnu.org In-Reply-To: <0c8f8899-0421-0aa7-2ecd-2167018c3924@gmx.de> Received-SPF: permerror client-ip=2001:3c8:9009:181::2; envelope-from=kre@munnari.OZ.AU; helo=munnari.OZ.AU X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <16697.1588517331@jinx.noi.kre.to> X-Mailman-Original-References: <0c8f8899-0421-0aa7-2ecd-2167018c3924@gmx.de> <11091.1588510206@jinx.noi.kre.to> Xref: csiph.com gnu.bash.bug:16269 Date: Sun, 3 May 2020 15:58:59 +0200 From: Tobias Wendorff Message-ID: <0c8f8899-0421-0aa7-2ecd-2167018c3924@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'd expect unplanned (ie: a bug). | 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. Interesting, an option I haven't used. If it acts like it says it should, the only downside should be the appearance of multi-line history entries, for the command while sleep 4 do echo awake done instead of the normal while sleep 4; do echo awake; done in the historu, you get the original, with the newlines embedded (though it appears some semi-colons are still added), that is, I got while sleep 4; do echo awake done (I didn't really type the indented "echo" as shown above). That ';' is harmless. The longer form just makes history entries occupy more vertical space, and be slightly harder (IMO) to edit, otherwise there should be no difference. kre