From: Eli Zaretskii <eliz@gnu.org>
To: Fredrik Ljungdahl <fredde1994@gmail.com>
Cc: 25666@debbugs.gnu.org
Subject: bug#25666: Screen rendering bug
Date: Fri, 10 Feb 2017 10:29:23 +0200 [thread overview]
Message-ID: <83inoi4ffg.fsf@gnu.org> (raw)
In-Reply-To: <CAPNDYOYyn9za-TAeUVfoQnk4dWeZNPOPejVFOY1bxaTk8h3xBw@mail.gmail.com> (message from Fredrik Ljungdahl on Thu, 9 Feb 2017 22:37:47 +0100)
> From: Fredrik Ljungdahl <fredde1994@gmail.com>
> Date: Thu, 9 Feb 2017 22:37:47 +0100
> Cc: 25666@debbugs.gnu.org
>
> I attempted to reproduce this in a different terminal, in case that was the issue (I originally used Konsole), in
> this case xterm. I was not able to reproduce under the standard resolution of 80x24. However, by increasing
> the resolution by fullscreening it (resulting in a terminal size of 212x78), I was able to once again reproducue
> the bug. Further testing shows that, with that particular file, I am able to reproduce the issue in 116x24 but not
> 80x24. I am guessing that text wrapping is involved in some way, but I can't consistently figure out where the
> bug reproduces and when it doesn't (aside from it always or never reproducing under the same terminal
> size).
Please show a screenshot of the messup you see.
Thanks.
next prev parent reply other threads:[~2017-02-10 8:29 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 [this message]
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=83inoi4ffg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25666@debbugs.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).