GNU bug report logs - #55236
29.0.50; Surprising behaviors with Eshell expansions

Previous Next

Full log

Message #8 received at 55236 <at> debbugs.gnu.org (full text, mbox):

From: Jim Porter <jporterbugs <at> gmail.com>
To: 55236 <at> debbugs.gnu.org
Subject: Re: bug#55236: [PATCH] 29.0.50; Surprising behaviors with Eshell
 expansions
Date: Mon, 2 May 2022 20:45:25 -0700

[Message part 1 (text/plain, inline)]

Here are the patches. Each patch corresponds to one of the headings in 
the original email. Hopefully they're fairly self-explanatory since I've 
added documentation to the manual as well as NEWS entries for each. I 
debated whether these should count as incompatible changes, but for most 
cases, I think there shouldn't be any incompatibility.

The highest-risk patch is the second one, since it converts multi-line 
numeric output from subcommands into a list of numbers. However, this 
helps a lot in fixing some of the problems in the third issue 
(concatenating expansions), and I think it's more consistent overall 
than before. However, it could make sense to provide a defcustom to opt 
out of the behavior if people think that would be helpful.

[0001-Eshell-variable-expansion-should-always-return-strin.patch (text/plain, attachment)]

[0002-Return-a-list-of-numbers-if-all-lines-of-an-Eshell-s.patch (text/plain, attachment)]

[0003-Improve-the-behavior-of-concatenating-parts-of-Eshel.patch (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.