From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21229 invoked by alias); 2 Sep 2015 14:09:39 -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: 36402 Received: (qmail 16965 invoked from network); 2 Sep 2015 14:09:39 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=LVenE7hvAIHtT3hztpzCs3Y9+o5yeJueUXwa+rUGPm0=; b=hPawpkGPv0n5KLzB3iQi1EsZBQnZ8xmQv7aDT7/vPBptU+DZ/E+m7uf4p6WsNwabdr T66wgTJwrz+GwuPJ0zgpjuc++KQ5W0iKU8p00o6BE6cLvqxMMqgK2KnPRrNRyMoxib6t SqqGi0yR7eg3SQn/xvyRlyXP2QM9dk2xARyFVOgtFHuH8R5bbiYW69dIVlQ8UnLw0wlV ZExrZMEptf7BGH3tw+vm+036T6VWk3/l9TfNN0yeZ/o5cpFUEzGw/9SY/8juBnB9xYNq iAGW6gZI9pWG1jZaHmSvpr8bOM6+jcvCzng8k87oDWcDN3flq0uzgG50RBrsr3Kwi/ut auZA== X-Gm-Message-State: ALoCoQm5Tey++KzWm28aoqWEBbipCdRXMKPUl/H5fllyde1mNoicKowNuhwczLreYbSf08SZnDXy X-Received: by 10.182.114.233 with SMTP id jj9mr20397820obb.22.1441202976114; Wed, 02 Sep 2015 07:09:36 -0700 (PDT) From: Bart Schaefer Message-Id: <150902070933.ZM16829@torch.brasslantern.com> Date: Wed, 2 Sep 2015 07:09:33 -0700 In-Reply-To: <87wpw9vuek.fsf@gmail.com> Comments: In reply to Christian Neukirchen "Re: Ctrl-c not working during correction with 5.1" (Sep 2, 3:10pm) References: <20150901141031.GB423@x4> <150901111502.ZM2072@torch.brasslantern.com> <87wpw9vuek.fsf@gmail.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Ctrl-c not working during correction with 5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Sep 2, 3:10pm, Christian Neukirchen wrote: } Subject: Re: Ctrl-c not working during correction with 5.1 } } Bart Schaefer writes: } } > Unintended side-effect of all the race-condition-prevention work that } > went on this summer. } } Could this also be related to this glitch? No, it couldn't, but that is an interesting one.