From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3513 invoked by alias); 3 Sep 2015 03:17:27 -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: 36408 Received: (qmail 14965 invoked from network); 3 Sep 2015 03:17:26 -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=a0EsYPIJejUMCpz2JW9GPv9HJ3oSoGi/dYiZ2wofXl8=; b=dpvaFg21AlgnmmbAE8RvL78/jOy5FjMRodyTmvweuyzjXSlv8Ve7js/DhrEz7ovL1G 6DEfflKjoOOfECettua5AXPQ6wf/iuNuEyLE3VuPe1gWFzRyzvUDdy4nz6ziXCAJcpya pVeeTsOfc6JUzyI/hcLhGLoaLmZnbFFB2fCnhtC2anRXE7WDe7UFXM+iX6yRyP8iM6wJ 6hKS9l+oG7czRsUUjGiuhwXgEVIGP/K0c3Va81Nk9BdBZVx+3DHEJ/TJmehy58rwKafP /Bdq0YABq1N/6QpTGs3KkLZxX+UPTBZsoOvl96OVIYlsqEt8Z2U8huPZE8YpurZMDAre qQbw== X-Gm-Message-State: ALoCoQmdqwWvFQrRckMI1ffG7phA6xkF7PIQnOxxwyvkjrc8CtyGj/f1DoqjNp8FKiwYb/0dvheD X-Received: by 10.202.80.67 with SMTP id e64mr11612079oib.100.1441250243410; Wed, 02 Sep 2015 20:17:23 -0700 (PDT) From: Bart Schaefer Message-Id: <150902201715.ZM18001@torch.brasslantern.com> Date: Wed, 2 Sep 2015 20:17:15 -0700 In-Reply-To: <150902193229.ZM17927@torch.brasslantern.com> Comments: In reply to Bart Schaefer "Re: Ctrl-c not working during correction with 5.1" (Sep 2, 7:32pm) References: <20150901141031.GB423@x4> <150901111502.ZM2072@torch.brasslantern.com> <87wpw9vuek.fsf@gmail.com> <150902193229.ZM17927@torch.brasslantern.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, 7:32pm, Bart Schaefer wrote: } } In any event, it is reproducible. And happens in 5.0.8 too, so it's at least not related to *recent* signal handling changes.