From: Fredrik Ljungdahl <fredde1994@gmail.com>
To: 25666@debbugs.gnu.org
Subject: bug#25666: Screen rendering bug
Date: Thu, 9 Feb 2017 09:23:48 +0100 [thread overview]
Message-ID: <CAPNDYOZ1a780+3GtLtjASBdZxDAAktxxefSyKhL232jUQSdN1A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
Hi.
I encountered a minor bug related to screen rendering in vertical split
screen (a | b) of the same file and some forms of page scrolling. The
problem seems to be related to linum-mode.
What I did to reproduce this bug under default settings:
* I used a 146x46 size terminal (potentially matters)
* Acquire this: http://sprunge.us/hVNi
* Invoke emacs with emacs -Q
* Go to this file (C-x C-f hVNi)
* Invoke line number mode (M-x linum-mode), lack of linum-mode doesn't seem
to reproduce this
* Split the window (C-x 3)
* Hold down C-n (C-v does not reproduce this)
* On the 2nd half-scroll, the 2nd split window should have its rendering
messed up in obvious ways
Emacs version: 25.1.1
System info (uname -a): Linux fiq-desktop 4.9.6-1-ARCH #1 SMP PREEMPT Thu
Jan 26 09:22:26 CET 2017 x86_64 GNU/Linux
I am using the terminal version of Emacs
Regards
FIQ
[-- Attachment #2: Type: text/html, Size: 1117 bytes --]
next reply other threads:[~2017-02-09 8:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 8:23 Fredrik Ljungdahl [this message]
2017-02-09 20:37 ` bug#25666: Screen rendering bug 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
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=CAPNDYOZ1a780+3GtLtjASBdZxDAAktxxefSyKhL232jUQSdN1A@mail.gmail.com \
--to=fredde1994@gmail.com \
--cc=25666@debbugs.gnu.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.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).