From: Farblos 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: 60817@debbugs.gnu.org
Subject: bug#60817: 28.2; `x-focus-frame' causes spurious input events causes edebug not showing intermediate results
Date: Sat, 21 Jan 2023 22:36:16 +0100 [thread overview]
Message-ID: <25376940-6fb8-bca1-962a-1df3424a2554@vodafonemail.de> (raw)
In-Reply-To: <4c47a431-4661-4a94-9cd7-267df5430946@vodafonemail.de>
On 2023-01-21 21:03, Farblos wrote:
> I used printf debugging and, admittedly, even back in Emacs 27 for now,
> since I have the Debian toolchain ready for that. I reduced the test
> case to this:
Bit the bullet and cloned master, compiled it, and: Bug *does not*
reproduce.
Only after seeing that HELP_EVENT in Emacs 27 I understood that hovering
over the modeline is a necessary precondition to reliably reproduce this
issue. So without debugging in Emacs 27 I wouldn't have been able to
ensure that the bug is gone in master ...
Feel free to close this issue. Optionally: If you happen to have an
explanation why this bug is gone, I'd really appreciate that.
Thanks for developing Emacs!
next prev parent reply other threads:[~2023-01-21 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 21:55 bug#60817: 28.2; `x-focus-frame' causes spurious input events causes edebug not showing intermediate results Farblos via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-15 6:23 ` Eli Zaretskii
2023-01-21 20:03 ` Farblos via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-21 21:36 ` Farblos via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-01-26 7:47 ` 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=25376940-6fb8-bca1-962a-1df3424a2554@vodafonemail.de \
--to=bug-gnu-emacs@gnu.org \
--cc=60817@debbugs.gnu.org \
--cc=akfkqu.9df7rp@vodafonemail.de \
--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).