From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: 'zle redisplay' bug in 5.3?
Date: Sat, 7 Jan 2017 10:05:05 -0800 [thread overview]
Message-ID: <170107100505.ZM11210@torch.brasslantern.com> (raw)
In-Reply-To: <170105090803.ZM3653@torch.brasslantern.com>
} On Jan 5, 3:01pm, Peter Stephenson wrote:
} }
} } The documentation says
} }
} } /* Most lines of the buffer we've shown at once with the current list *
} } * showing. == 0 if there is no list. == -1 if a new list has just *
} } * been put on the screen. == -2 if zrefresh() needs to put up a new *
} } * list. */
} }
} } Is it a case of the two requiring different handling?
That comment is incomplete. showinglist may also have a positive value
which is tied to the value of "nlnct" -- which appears to be the number
of newlines in the prompt string.
Something is repeating the "move up nlnct lines" action twice. This is
similar to the description in the thread from 38048.
Not sure what to do with this information yet, and out of time to look
at it this morning, but maybe it's a clue for someone else.
next prev parent reply other threads:[~2017-01-07 18:11 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 [this message]
2017-01-07 18:53 ` Peter Stephenson
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=170107100505.ZM11210@torch.brasslantern.com \
--to=schaefer@brasslantern.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).