[Top][All Lists]

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

Re: Latest push for command substitutions

From: Chet Ramey
Subject: Re: Latest push for command substitutions
Date: Thu, 24 Jun 2021 11:38:55 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.11.0

On 6/24/21 5:18 AM, Koichi Murase wrote:
Please run it through any tests or scripts you have so we can shake out any
bugs early.

I haven't thoroughly tested it, but I found with a quick trial that
the parser state seems to remain broken in the new command line after
a syntax error:

Thanks for the report. This is a new class of error, I suppose is the best
way to put it, introduced with this new implementation. In the previous ad-
hoc implementation, the "parse" would succeed until word expansion, then
fail when the string was run through the parser again to find the closing

There's already code in there to handle this case, it just needs different
return values to handle the error differently. There are a couple of ways
to deal with this interactive-only error, so I'll pick one.


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