bug-bash
[Top][All Lists]
Advanced

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

Re: Feature request: prompt strings in output from edit-and-execute-comm


From: Chet Ramey
Subject: Re: Feature request: prompt strings in output from edit-and-execute-command readline function ( was About `M-C-e` expand result `'` failed )
Date: Tue, 6 Feb 2024 15:25:09 -0500
User-agent: Mozilla Thunderbird

On 2/6/24 1:39 PM, Oğuz wrote:
On Tuesday, February 6, 2024, Chet Ramey <chet.ramey@case.edu <mailto:chet.ramey@case.edu>> wrote:

    What's the specific request here?


That bash interpret multiline commands retrieved from command history as a whole and not run the rest of the lines as separate commands when the first line is changed.

Ah, I see: you want any "lines" that readline returns that contain embedded
newlines to be parsed as a compound_list instead of a series of newline-
terminated commands (what bash calls a simple_list). Kind of like they had
been enclosed in braces. I'm not sure I could do that much violence to the
parser.

--
``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/




reply via email to

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