unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bojohan+mail@dd.chalmers.xn--se, 675@debbugs.gnu.org
Subject: bug#675: 23.0.60; Edebugging track-mouse
Date: Sun, 20 Oct 2019 13:21:08 +0200	[thread overview]
Message-ID: <87k18zfysb.fsf@gnus.org> (raw)
In-Reply-To: <83o8yb65rz.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Oct 2019 14:00:16 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> But back to the original problem:  (input-pending-p) is non-nil here,
>> but it's because of a mouse movement, which edebug doesn't care about.
>> 
>> I guess edebug really cares about unread-command-events here?  So
>> changing the call to just examine that instead might be the fix?
>
> Can Edebug bind while-no-input-ignore-events to something appropriate
> to rectify this?

Hm...  I'm completely unfamiliar with that variable.

@defvar while-no-input-ignore-events
This variable allow setting which special events @code{while-no-input}
should ignore.  It is a list of symbols.

Perhaps the manual should mention what kind of symbols?

Anyway, I can't see that edebug calls while-no-input?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-10-20 11:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <yoijk5er1je7.fsf@remote5.student.chalmers.se>
2011-09-11 17:17 ` bug#675: 23.0.60; Edebugging track-mouse Lars Magne Ingebrigtsen
2014-02-26  9:16   ` Xue Fuqiao
2016-07-10 21:04     ` npostavs
2019-10-20  7:36 ` Lars Ingebrigtsen
2019-10-20 11:00   ` Eli Zaretskii
2019-10-20 11:21     ` Lars Ingebrigtsen [this message]
2019-10-20 11:38       ` Eli Zaretskii
2019-10-20 11:49         ` Lars Ingebrigtsen
2022-02-12  7:41 ` Lars Ingebrigtsen

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=87k18zfysb.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=675@debbugs.gnu.org \
    --cc=bojohan+mail@dd.chalmers.xn--se \
    --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).