all messages for Emacs-related lists mirrored at yhetil.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: Sun, 11 Sep 2022 19:38:45 +0600	[thread overview]
Message-ID: <87k06ayqsa.fsf@disroot.org> (raw)
In-Reply-To: <835yhu9m3e.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 11 Sep 2022 14:39:17 +0300")

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

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Sun, 11 Sep 2022 16:34:38 +0600
>> From:  Akib Azmain Turja via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>> 
>> Emacs often writes to the last character possibly by mistake.  To
>> reproduce, run emacs -Q, hit M-: (eval-expression), write some garbage
>> until the minibuffer window scrolls (I used (+ (% (random) 26) ?a) to
>> generate the garbage), and hit C-p until you scroll down a line.  You
>> should now see that the last character cell contains a continuation
>> ('\') glyph.  I think this is probably due to the use of any of 'il' or
>> 'il1' or 'rin' terminal capabilities.
>
> Thanks, but please provide more info:
>
>   . the exact recipe to try (I tried to follow the above, but
>     couldn't, I guess I misunderstand what you mean)
>   . on which terminal emulators this is known to happen, at least in
>     your case (and if you happen to know, also others)

I don't why my first message confused everyone, but I'll try to give a
clearer explanation:

Emacs often writes to the last character cell (i.e. the character cell
on the bottom-left corner)  possibly by mistake.  To
reproduce:

  1. Run emacs -Q.
  2. M-: (or any other command that asks for a string).
  3. Write some garbage until the minibuffer window scrolls.  (I used
     (dotimes (i 10000) (+ (% (random) 26) ?a)) to generate the garbage
     in *scratch* buffer and copied to the minibuffer, but you can write
     anything you want.)
  4. Scroll down a line.
  5. You should now see that the last character cell (i.e. the character
     cell on the bottom-left corner) contains a continuation ('\')
     glyph.  But Emacs doesn't dare to write to that character cell when
     'am' capability is defined, and my terminal have that capability
     defined.  I think this is probably due to the use of any of 'il' or
     'il1' or 'rin' capabilities.  Tested on Linux console, St, Xterm
     and Kitty.
  6. Scroll up two lines.
  7. The continuation glyph on the line before the last one doesn't
     appear.  Tested on Linux console, St, Xterm and Kitty.
  8. Scroll down more than two lines.
  9. Exit minibuffer.  The continuation glyph will still stay there on
     some terminals.  Tested on St, Kitty.

I hope this is clearer.

-- 
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-11 13:38 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k06ayqsa.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.