From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net
Cc: 25666@debbugs.gnu.org, fredde1994@gmail.com
Subject: bug#25666: Screen rendering bug
Date: Sun, 12 Feb 2017 21:49:02 +0200 [thread overview]
Message-ID: <83y3xb1975.fsf@gnu.org> (raw)
In-Reply-To: <87d1enkzfm.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)
> From: npostavs@users.sourceforge.net
> Cc: 25666@debbugs.gnu.org, fredde1994@gmail.com
> Date: Sun, 12 Feb 2017 13:59:41 -0500
>
> >> > I see this with nlinum-mode as well. My terminal is PuTTY (which
> >> > emulates xterm).
> >>
> >> Ah, this depends on how high the terminal is. With an 80x32 terminal I
> >> see it with nlinum-mode as well. I think it's just a question of
> >> whether the first scroll reaches high enough line numbers to trigger a
> >> margin width adjustment.
> >
> > Not sure what you mean by that. In my experiments, the margin starts
> > at 3 columns, and stays at 3 columns. There's no adjustment.
>
> With nlinum-mode it starts at 2 columns for me. With a terminal 80x49
> or higher, it widens before the bug happens.
Most of my experiments were with 80x38 terminal, where the margin
never widens during the first 2 scrolls. And I see the problem with
nlinum-mode with that configuration.
I don't think margin widening has anything to do with the problem.
It's enough to have a post-command-hook that changes overlays, I
think. But that's a guess, although it's based on the fact that the
problematic window doesn't need to be redrawn at all and doesn't need
any margin width adjustment. The selected window, which is where the
margin width might change, is updated correctly.
next prev parent reply other threads:[~2017-02-12 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 8:23 bug#25666: Screen rendering bug Fredrik Ljungdahl
2017-02-09 20:37 ` Eli Zaretskii
2017-02-09 21:37 ` Fredrik Ljungdahl
2017-02-10 8:29 ` Eli Zaretskii
2017-02-10 9:12 ` Fredrik Ljungdahl
2017-02-10 9:43 ` Fredrik Ljungdahl
2017-02-10 10:22 ` Eli Zaretskii
2017-02-10 10:44 ` Fredrik Ljungdahl
2017-02-12 15:56 ` npostavs
2017-02-12 16:47 ` Eli Zaretskii
2017-02-12 17:15 ` npostavs
2017-02-12 18:24 ` Eli Zaretskii
2017-02-12 18:59 ` npostavs
2017-02-12 19:49 ` Eli Zaretskii [this message]
2022-02-21 15:40 ` bug#25666: split-screen + linum-mode in tall TTY fails to fully render other window after scrolling Lars Ingebrigtsen
2022-03-21 18:30 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y3xb1975.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25666@debbugs.gnu.org \
--cc=fredde1994@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).