bug#55236: [PATCH v2] 29.0.50; Surprising behaviors with Eshell expansions

[Jim Porter]

On 5/2/2022 8:45 PM, Jim Porter wrote:
> 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.

Spelling is hard. I fixed a typo in the documentation for the second 
patch (`eshell-convert-numeric-agument' -> 
`eshell-convert-numeric-arguments').

0001-Eshell-variable-expansion-should-always-return-strin.patch
Description: Text document

0002-Return-a-list-of-numbers-if-all-lines-of-an-Eshell-s.patch
Description: Text document

0003-Improve-the-behavior-of-concatenating-parts-of-Eshel.patch
Description: Text document