unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Akib Azmain Turja via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57728@debbugs.gnu.org
Subject: bug#57728: 29.0.50; Emacs writes wrong glyph at the bottom-right corner of text terminals
Date: Mon, 12 Sep 2022 18:59:09 +0600	[thread overview]
Message-ID: <87bkrkkaua.fsf@disroot.org> (raw)
In-Reply-To: <83a6749643.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Sep 2022 14:36:44 +0300")

[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Akib Azmain Turja <akib@disroot.org>
>> Cc: 57728@debbugs.gnu.org
>> Date: Mon, 12 Sep 2022 14:03:04 +0600
>> 
>> > Let me turn the table and ask you: why do you think that '\' is not
>> > the usual continuation glyph that Emacs always produces when the width
>> > of a screen line on a TTY frame is exceeded?
>> >
>> >
>> >
>> 
>> OK, OK.  This title is misleading.  Showing the continuation glyph is
>> not wrong, but it is unexpected, because Emacs doesn't write to the
>> bottom-right corner.
>
> I've seen these continuation glyphs on every TTY display where I ever
> used Emacs, so I'd consider it a surprise, if not a bug, that on some
> TTYs those continuation glyphs were absent.  They should be there to
> indicate to the user that the line is continued.
>
>> Perhaps I don't have the ability to express the problem in character, so
>> I'm trying to pixel.  Can you please spend some seven and half minutes
>> to watch the bug in the video I attached?
>
> Sorry, I cannot want videos of this format.

What format should I use?  AFAIK, ogv is a free format.  How about
asciicast (made with asciinema)?

-- 
Akib Azmain Turja

Find me on Mastodon at @akib@hostux.social.

This message is signed by me with my GnuPG key.  Its fingerprint is:

    7001 8CE5 819F 17A3 BBA6  66AF E74F 0EFA 922A E7F5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2022-09-12 12:59 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 [this message]
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
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=87bkrkkaua.fsf@disroot.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=57728@debbugs.gnu.org \
    --cc=akib@disroot.org \
    --cc=eliz@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).