zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: 'zle redisplay' bug in 5.3?
Date: Sat, 7 Jan 2017 18:53:25 +0000	[thread overview]
Message-ID: <20170107185325.061a57cf@ntlworld.com> (raw)
In-Reply-To: <170107100505.ZM11210@torch.brasslantern.com>

On Sat, 7 Jan 2017 10:05:05 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> Something is repeating the "move up nlnct lines" action twice.  This is
> similar to the description in the thread from 38048.

I can see two bits in zrefresh() that look like they have to
do with this

One is to do with listshown, rather than showinglist, that triggers what
I take to be the key bit of the refresh code, together with clearlist.
The interaction between showinglist and listshown appears to be utterly
opaque.

The other uses showinglist and then calls listmatches().  Furthermore,
it then calls zrefresh() recursively.  I modified that in 36416, commit
32f5d3d8, only to get called if there was no error, but the recursive
call has always been there.  This might have something to do with
it, particularly now errflag signals both error and interrupt.  Could
propagation of ERRFLAG_INT or the lack of it or the fact that it affects
the code that calls zrefresh() recursively have something to do with
the interrupt problem that caused the changed to redisplaying?

pws


  reply	other threads:[~2017-01-07 19:00 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 [this message]
2017-01-07 20:04             ` Peter Stephenson
2017-01-08  4:46               ` Bart Schaefer
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=20170107185325.061a57cf@ntlworld.com \
    --to=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).