unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 21:03:41 +0100	[thread overview]
Message-ID: <4c47a431-4661-4a94-9cd7-267df5430946@vodafonemail.de> (raw)
In-Reply-To: <837cxo71tt.fsf@gnu.org>

On 2023-01-15  07:23, Eli Zaretskii wrote:

> AFAIU, input-pending-p should filter out focus events, so I don't
> think I understand why you see this.  Can you try this in Emacs 29 or
> the master branch of the Emacs Git repository, so we make sure this
> problem was not fixed already?  If it still happens in those newer
> versions, maybe you can step with GDB through get_input_pending, when
> it's called from input-pending-p, and through readable_events called
> by get_input_pending, and see why focus events aren't filtered out?

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:

(defun testcase ()
   (interactive)
   (message "pre: %S" (input-pending-p))
   (x-focus-frame (selected-frame))
   (sleep-for 0.5)
   (message "pst: %S" (input-pending-p)))

The error ("pst: t") reproduces only after touching some part of the 
modeline that provides a tooltip.

And the offending event that causes `input-pending-p' to become t is 
*not* a focus event (I can see indeed these getting filtered in 
readable_events) but rather a HELP_EVENT.  So as soon as one has touched 
the modeline, the call to `x-focus-frame' produces these HELP_EVENTS.

Does that ring a bell?  Any new directions where I should look at?

I'll try setting up a build environment for a newer Emacs when I find 
the time to do so.





  reply	other threads:[~2023-01-21 20:03 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 [this message]
2023-01-21 21:36     ` Farblos via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=4c47a431-4661-4a94-9cd7-267df5430946@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).