From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: gregory@heytings.org, 57728@debbugs.gnu.org, akib@disroot.org
Subject: bug#57728: 29.0.50; Emacs writes wrong glyph at the bottom-right corner of text terminals
Date: Mon, 12 Sep 2022 15:06:23 +0300 [thread overview]
Message-ID: <8335cw94qo.fsf@gnu.org> (raw)
In-Reply-To: <m2y1uoyfau.fsf@Mini.fritz.box> (message from Gerd Möllmann on Mon, 12 Sep 2022 13:59:05 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: gregory@heytings.org, 57728@debbugs.gnu.org, akib@disroot.org
> Date: Mon, 12 Sep 2022 13:59:05 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> >> This is because 'write' deliberatly leaves the bottom-right corner alone
> >> if the terminal has "auto right margin" (autowrap).
> >
> > But AFAIU, the bug actually shows that we somehow _do_ write there,
> > although the display engine assumes we don't. Right?
>
> My theory is that no-one but tty_write_glyphs knows that it didn't write
> to the bottom-right corner.
You are saying that update_frame_line tells tty_write_glyphs to write
the '\', but tty_write_glyphs doesn't in this case?
But why would we need to write that character if we know it's already
there (because all lines end with it)? That should only happen if we
scroll the region instead of rewriting lines one by one. Is that what
happens in this case?
next prev parent reply other threads:[~2022-09-12 12:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 10:34 bug#57728: 29.0.50; Emacs writes wrong glyph at the bottom-right corner of text terminals Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-11 10:54 ` Andreas Schwab
2022-09-11 10:54 ` Lars Ingebrigtsen
2022-09-11 11:39 ` Eli Zaretskii
2022-09-11 13:38 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-11 14:33 ` Eli Zaretskii
2022-09-11 15:44 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-11 17:23 ` Eli Zaretskii
2022-09-11 18:02 ` Lars Ingebrigtsen
2022-09-11 18:12 ` Eli Zaretskii
2022-09-11 18:18 ` Lars Ingebrigtsen
2022-09-11 18:30 ` Eli Zaretskii
2022-09-12 7:56 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 9:19 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87pmg1xbnr.fsf@disroot.org>
2022-09-12 8:21 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 9:05 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 11:36 ` Eli Zaretskii
2022-09-12 12:59 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 13:01 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 13:12 ` Eli Zaretskii
2022-09-12 18:48 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 11:31 ` Eli Zaretskii
2022-09-11 20:35 ` Gregory Heytings
2022-09-12 6:38 ` Gerd Möllmann
2022-09-12 8:03 ` Gregory Heytings
2022-09-12 8:59 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 11:30 ` Eli Zaretskii
2022-09-12 11:42 ` Gregory Heytings
2022-09-12 12:03 ` Gerd Möllmann
2022-09-12 11:59 ` Gerd Möllmann
2022-09-12 12:06 ` Eli Zaretskii [this message]
2022-09-12 12:29 ` Gerd Möllmann
2022-09-12 12:54 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 12:20 ` Andreas Schwab
2022-09-12 12:29 ` Gerd Möllmann
2022-09-12 8:10 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 11:58 ` Eli Zaretskii
2022-09-12 12:07 ` Gregory Heytings
2022-09-12 12:11 ` Eli Zaretskii
2022-09-12 12:22 ` Gregory Heytings
2022-09-12 12:07 ` Eli Zaretskii
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=8335cw94qo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57728@debbugs.gnu.org \
--cc=akib@disroot.org \
--cc=gerd.moellmann@gmail.com \
--cc=gregory@heytings.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).