From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5184 invoked by alias); 3 Sep 2015 02:32:38 -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: 36406 Received: (qmail 28808 invoked from network); 3 Sep 2015 02:32:36 -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=pbnR9Vv2USvXtDmUdMjbOVjNKRu8sVvirpEIjOLJ9x8=; b=KLH8y1HVPhTbtc9kI13m68f2iI/BeFjY7rvgbESelgLe60YJysVU03j8v8/H8ytZkm 1lOoMibyeiDkJzNqcHr4jRGmNtg26XSh5XmM6vAvRZrmYYrCZZu6Ui8PV0cAgGby9dC/ q2r/A1leGYfjTCjwZrAbdoDL//HKyoEoQ/U2AuYNAXEVgLUaA/UvvPgGrxGgCVdnH2dv 5RRp4I9CkqpjL9uFn74h5GErvQv5rdPtGQOyqylhbg+IYRqob0afKzgOlURzZwByScy6 m2wC+Fq+RafhIyDOVo7n3iGiYHVQCrJOPleJw8KtAW8OTBPZJnNP4aUDwrrsLelzHQro QS9A== X-Gm-Message-State: ALoCoQnfILZAkVtcxIySoCuF3Scrg6+n6w+c34PJt1WwGS91scz25NZjSe929cNNOlKnVEOUndO8 X-Received: by 10.202.85.20 with SMTP id j20mr11695797oib.101.1441247552675; Wed, 02 Sep 2015 19:32:32 -0700 (PDT) From: Bart Schaefer Message-Id: <150902193229.ZM17927@torch.brasslantern.com> Date: Wed, 2 Sep 2015 19:32:29 -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 An additional comment ... On Sep 2, 3:10pm, Christian Neukirchen wrote: } } zsh 5.1 (x86_64-unknown-linux-gnu) } zsh-5.1-0-g11189c6 } % zsh -f } juno% setopt NOALWAYSLASTPROMPT PROMPT_SUBST } juno% PS1='$(echo foo)%# ' } foo% ls /usr/share/man/man1/ } zsh: do you wish to see all 2528 possibilities (1264 lines)? n } $(echo ls /usr/share/man/man1/ } foo% } } Somehow the unevaluated PS1 is printed. While attempting to reproduce this, I somehow managed to cause this to kill the *parent* shell from which I started up "zsh -f". I have no good ideas how that could happen; no core files were produced. But I thought I would mention it, in case it indicates this is a more serious problem than it appears. In any event, it is reproducible.