Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: unwanted error aborting continued command substitution
- X-seq: zsh-workers 34906
- From: Mikael Magnusson <mikachu@xxxxxxxxx>
- To: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- Subject: Re: PATCH: unwanted error aborting continued command substitution
- Date: Fri, 17 Apr 2015 12:52:56 +0200
- Cc: zsh workers <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UDMHkeEJFj0xIk0ZE+sC9JKedC3lFdWa5MxYrZps8As=; b=XunCs9G75Uej7eUEoVlVjOCNd2V93CFG7t23thLO0edpym90XyuYeqiQNgxH+QXq5W 7dxUkkGd0Am1PNNg9i1fBGvGV0a/ULIplpJE3LU6LVPGM2bi/xPArmqFWaex8JYZCaHx O9ynA5LyxFo0quc/OX8RkK3Zv+0K5zphPxIwPa29mY3VI7w1P7Fh0Zp5/gPO6WEqeRhS GIXrE6e/DilwEttoyLr5hJC3LzD9Z7rbxO6Uitv3S7lxZagTFB86H4+vIM4v3mQC4qEx Mjj9hivnJ8bnshCEALBQFA0xsmzH4vNW3ccJ7dZVUJRwlBgsibR1Z81YnQuzXoXlDYop 2J/w==
- In-reply-to: <20150417101600.09a17a9e@pwslap01u.europe.root.pri>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CAHYJk3T2jd238ZCh1mtNorNKZJ0H8U6wQeTA_VYX2aDiXmAt=w@mail.gmail.com> <20150417101600.09a17a9e@pwslap01u.europe.root.pri>
On Fri, Apr 17, 2015 at 11:16 AM, Peter Stephenson
<p.stephenson@xxxxxxxxxxx> wrote:
> On Fri, 17 Apr 2015 06:39:29 +0200
> Mikael Magnusson <mikachu@xxxxxxxxx> wrote:
>> % $(
>> cmdsubst> [press ctrl-c here]
>> zsh: parse error near `$('
>>
>> I would expect to not get an error message about syntax after pressing
>> ctrl-c.
>
> I think that means we can handle this case as part of a general tidy up
> rather than agonising over the complexities of the nested parsing ---
> which means we can reap the benefit [sorry, leverage the synergy] of
> breaking out the interrupt flag. The following looks plausible, though
> the interactions are complicated.
>
> I believe the fix for only resetting the interrupt flag when resetting
> the local keymap if there actually *was* a local keymap has to be
> correct, but you never quite know if there are scary special cases that
> use things differently...
I didn't think to try this yesterday, but invoking push-input gives
the same error (sorry).
--
Mikael Magnusson
Messages sorted by:
Reverse Date,
Date,
Thread,
Author