zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: zsh exits after delete-char-or-list and two ^Cs
Date: Thu, 26 Aug 2004 17:22:24 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0408261705190.28624@toltec.zanshin.com> (raw)
In-Reply-To: <20040825170456.GA7526@la-z-boy.comfychair.org>

On Wed, 25 Aug 2004, Danek Duvall wrote:

> This happens with 4.0.6, 4.2.0 and 4.2.1, the first two on Linux, the 
> latter on Solaris.  If I use delete-char-or-list, then hit control-C 
> twice, the first time cancels the command-line where I hit ^D, and the 
> second one exits the shell.

Looks like the interrupt handler isn't getting reset after the first 
ctrl-C.  I don't yet know why not, but this means that the default SIGINT
handler is called on the second ^C, which of course ends the process.

There also appears to be a bug in 4.2.x with "zle -I" and "zle -R".  This 
should work:

	TRAPINT() { zle -I && zle send-break }

because "zle -I" is supposed to return zero only when zle is active. 
However, I get:

	TRAPINT:zle: widgets can only be called when ZLE is active

In any case there are numerous workarounds involving trapping ^C or using 
"stty" to disable interrupt ... but they all have drawbacks.


  reply	other threads:[~2004-08-27  0:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25 17:04 Danek Duvall
2004-08-27  0:22 ` Bart Schaefer [this message]
2004-09-01 18:10   ` Peter Stephenson
2004-09-01 19:44     ` Bart Schaefer
2004-09-02  9:19       ` Peter Stephenson
2004-09-02 15:15         ` Bart Schaefer
2004-09-03  9:37           ` Peter Stephenson
2004-09-03 18:59             ` Bart Schaefer
2004-09-07 14:08               ` Peter Stephenson
2004-09-08 14:23               ` Peter Stephenson
2004-09-01 17:36 ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.61.0408261705190.28624@toltec.zanshin.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).