zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>,
	"Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: 'zle redisplay' bug in 5.3?
Date: Sat, 7 Jan 2017 20:46:40 -0800	[thread overview]
Message-ID: <170107204640.ZM12937@torch.brasslantern.com> (raw)
In-Reply-To: <20170107200455.656cec0c@ntlworld.com>

On Jan 7,  8:04pm, Peter Stephenson wrote:
} Subject: Re: 'zle redisplay' bug in 5.3?
}
} OK, how about this as an alternative to the previous change to the
} refresh code?  If I'm following properly, this was a problem when
} 
} TRAPINT () {
} 	zle reset-prompt
} 	return 127
} }
} 
} was in effect during interruption at a completion list.

That's correct.  However, this patch (checking errflag) does not fix
the issue with interrupts.

Here's how to reproduce:

    zsh -f
    autoload compinit
    compinit -u -D
    TRAPINT () {
      zle reset-prompt
      return 127
    }
    _delay() { sleep 10 }
    zstyle \* completer _complete _delay

Now complete after e.g. "ls " and press ^C within 10 seconds.  The
complist module does not need to be involved, so a change only there
does not help.


  reply	other threads:[~2017-01-08  4:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170105030137.v4tzweda6pxyqnrq@majutsushi.net>
     [not found] ` <CGME20170105091042epcas1p3ebc6c107d3121c8f6b980bbcbc59bc60@epcas1p3.samsung.com>
     [not found]   ` <170105010914.ZM1529@torch.brasslantern.com>
2017-01-05 15:01     ` Peter Stephenson
2017-01-05 17:08       ` Bart Schaefer
2017-01-07 18:05         ` Bart Schaefer
2017-01-07 18:53           ` Peter Stephenson
2017-01-07 20:04             ` Peter Stephenson
2017-01-08  4:46               ` Bart Schaefer [this message]
2017-01-08 17:59                 ` 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=170107204640.ZM12937@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@zsh.org \
    /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).