From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: 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:11:19 +0300 [thread overview]
Message-ID: <83zgf47py0.fsf@gnu.org> (raw)
In-Reply-To: <ee1bff0b2c99d4bdcf21@heytings.org> (message from Gregory Heytings on Mon, 12 Sep 2022 12:07:12 +0000)
> Date: Mon, 12 Sep 2022 12:07:12 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: akib@disroot.org, 57728@debbugs.gnu.org
>
> >> 5. Now hit C-p a few times, until you see the "\" continuation
> >> character appear on the last character (the one at the bottom right).
> >> This should not happen.
> >
> > It does happen. Why do you think it shouldn't? Those are all continued
> > lines, so they should all end with a '\'.
>
> Because Emacs should never write on the last character at the bottom
> right.
That's immaterial: the user doesn't care what are Emacs's problems.
The user expects to see a continuation glyph at the end of every
continued line. How does Emacs accomplish that is our problem.
> > However, if I now C-n enough times to have the mini-window scroll, I see
> > that lines scrolled into the view don't have the '\' continuation glyph.
> > _That_ shouldn't happen. So I finally have something to work with,
> > thanks.
>
> That shouldn't happen either, indeed. But that wasn't what the bug report
> originally said.
I think it's exactly the same bug.
next prev parent reply other threads:[~2022-09-12 12:11 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
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 [this message]
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=83zgf47py0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57728@debbugs.gnu.org \
--cc=akib@disroot.org \
--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).