From: Jim Porter <jporterbugs@gmail.com>
To: Ashton Wiersdorf <ashton@wiersdorfmail.net>,
Eli Zaretskii <eliz@gnu.org>
Cc: 74430@debbugs.gnu.org
Subject: bug#74430: 30.0.92; pixel-scroll-precision-mode hiding Eshell prompt after some commands
Date: Sun, 15 Dec 2024 11:10:00 -0800 [thread overview]
Message-ID: <0c8c7aa4-a73d-c125-4770-f21f8aec9456@gmail.com> (raw)
In-Reply-To: <m2o71exg58.fsf@wiersdorfmail.net>
On 12/14/2024 10:40 AM, Ashton Wiersdorf wrote:
> Hey, sorry Eli. I haven't been able to get this to reproduce
> consistently—it happens most often when I run a (broken) test suite on
> an Elixir project I'm working on, and then only sometimes. I think
> running a complex Elixir application would be a suboptimal thing to run
> to try to reproduce the bug, no?
>
> I might have a little time today to try reproducing it with simpler
> commands; I'll let you know then. Sorry I haven't been able to get a MWE
> yet.
If you can't find a minimal example, a screenshot could also help, so
long as you wouldn't be leaking any private information.
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.
prev parent reply other threads:[~2024-12-15 19:10 UTC|newest]
Thread overview: 12+ 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-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 [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=0c8c7aa4-a73d-c125-4770-f21f8aec9456@gmail.com \
--to=jporterbugs@gmail.com \
--cc=74430@debbugs.gnu.org \
--cc=ashton@wiersdorfmail.net \
--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).