From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20893 invoked by alias); 17 Apr 2015 10:53:02 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 34906 Received: (qmail 23171 invoked from network); 17 Apr 2015 10:52:59 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 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== MIME-Version: 1.0 X-Received: by 10.42.236.132 with SMTP id kk4mr2867620icb.46.1429267976900; Fri, 17 Apr 2015 03:52:56 -0700 (PDT) In-Reply-To: <20150417101600.09a17a9e@pwslap01u.europe.root.pri> References: <20150417101600.09a17a9e@pwslap01u.europe.root.pri> Date: Fri, 17 Apr 2015 12:52:56 +0200 Message-ID: Subject: Re: PATCH: unwanted error aborting continued command substitution From: Mikael Magnusson To: Peter Stephenson Cc: zsh workers Content-Type: text/plain; charset=UTF-8 On Fri, Apr 17, 2015 at 11:16 AM, Peter Stephenson wrote: > On Fri, 17 Apr 2015 06:39:29 +0200 > Mikael Magnusson 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