From: Ashton Wiersdorf <ashton@wiersdorfmail.net>
To: Jim Porter <jporterbugs@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 74430@debbugs.gnu.org
Subject: bug#74430: 30.0.92; pixel-scroll-precision-mode hiding Eshell prompt after some commands
Date: Fri, 27 Dec 2024 13:09:00 -0700 [thread overview]
Message-ID: <m2v7v4x50j.fsf@wiersdorfmail.net> (raw)
In-Reply-To: <0c8c7aa4-a73d-c125-4770-f21f8aec9456@gmail.com> (Jim Porter's message of "Sun, 15 Dec 2024 11:10:00 -0800")
[-- Attachment #1: Type: text/plain, Size: 178 bytes --]
> If you can't find a minimal example, a screenshot could also
> help, so
> long as you wouldn't be leaking any private information.
Here's a screenshot of the bug in action:
[-- Attachment #2: Screenshot showing scroll bug in Emacs --]
[-- Type: image/png, Size: 282829 bytes --]
[-- Attachment #3: Type: text/plain, Size: 1008 bytes --]
> Also, are there any "unique" properties of the output that
> causes this
> bug? For example, does it use "\r" carriage returns to overwrite
> the
> last line, or does it use emojis, or anything like that? If
> there's
> something different from the norm, that could help narrow things
> down.
I've seen this most often after running Elixir scripts—that might
just be availability bias because that's what I'm doing for work
right now! There *is* some colored text in the output. AFAIK
Elixir doesn't send "\r" to do anything tricky with the last line.
I think I've seen this happen with other commands.
I've noticed that the easiest way to rid myself of this behavior
is to just it Ctrl-l when it arises. That resets something and it
will work again for a while.
Note: I just upgraded to 30.0.93, and I'll keep my eyes peeled to
see if it resurfaces.
Thanks for your help, attention, and patience. Happy holidays!
--
Ashton Wiersdorf
https://lambdaland.org/
prev parent reply other threads:[~2024-12-27 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 17:52 bug#74430: 30.0.92; pixel-scroll-precision-mode hiding Eshell prompt after some commands Ashton Wiersdorf
2024-11-21 10:53 ` Eli Zaretskii
2024-11-21 18:37 ` Jim Porter
2024-11-21 23:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-22 6:58 ` Eli Zaretskii
2024-11-30 10:07 ` Eli Zaretskii
2024-12-14 9:38 ` Eli Zaretskii
2024-12-28 11:13 ` Eli Zaretskii
2024-11-25 5:13 ` Jim Porter
2024-11-30 10:07 ` Eli Zaretskii
2024-12-14 9:38 ` Eli Zaretskii
2024-12-14 18:40 ` Ashton Wiersdorf
2024-12-15 19:10 ` Jim Porter
2024-12-27 20:09 ` Ashton Wiersdorf [this message]
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=m2v7v4x50j.fsf@wiersdorfmail.net \
--to=ashton@wiersdorfmail.net \
--cc=74430@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jporterbugs@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).