From: npostavs@users.sourceforge.net
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25666@debbugs.gnu.org, fredde1994@gmail.com
Subject: bug#25666: Screen rendering bug
Date: Sun, 12 Feb 2017 12:15:06 -0500 [thread overview]
Message-ID: <87fujjl49x.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83d1en2w6b.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 12 Feb 2017 18:47:24 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> I see the same here. The frame dimensions are not relevant, btw: I
> can see this with any dimensions I tried.
Hmm, like the OP, I can't reproduce with an 80x24 terminal.
>> It doesn't happen with nlinum-mode, probably because with nlinum-mode
>> when the left window scrolls, the margin in the right window is widened
>> too.
>
> 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.
> You can also trigger a slightly different messup by "M-<" after the
> first scroll (which by itself looks OK).
Yes, in this case the top half of the other window gets lost.
next prev parent reply other threads:[~2017-02-12 17:15 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 [this message]
2017-02-12 18:24 ` Eli Zaretskii
2017-02-12 18:59 ` npostavs
2017-02-12 19:49 ` Eli Zaretskii
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=87fujjl49x.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=25666@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=fredde1994@gmail.com \
/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).