From: storm@cua.dk (Kim F. Storm)
Cc: Chong Yidong <cyd@stupidchicken.com>,
emacs-devel@gnu.org, Ken Manheimer <ken.manheimer@gmail.com>,
rms@gnu.org
Subject: Re: two related edebug problems
Date: Sat, 12 Aug 2006 02:19:36 +0200 [thread overview]
Message-ID: <m3r6zmztyf.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <jwv3bc2x5r7.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 11 Aug 2006 18:34:29 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> This is a workaround rather than a fix. A real fix would be to change
> sit-for so it doesn't use unread-command-events but an internal variable
> instead with which other code can't mess.
We currently have the following "unread event" variables (in order of usage):
unread-post-input-method-events
unread-command-char (obsolete)
unread-command-events
unread-input-method-events
<keyboard macros>
unread_switch_frame (C internal)
At which step should unread-sit-for-event be placed?
I.e. if some timer function actually places something on
unread-command-events, should that be interpreted before or after
unread-sit-for-event ??
BTW, unread-post-input-method-events and unread-input-method-events
have the _same_ doc string:
List of events to be processed as input by input methods.
These events are processed after `unread-command-events', but
before actual keyboard input. */);
According to the sequence in the code, "after" should be "before"
for unread-post-input-method-events.
But the name of these vars puzzles me... since the -post- thing
is actually run _before_ the other vars...??
Maybe the doc strings need some clarification...
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-08-12 0:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 18:30 two related edebug problems Ken Manheimer
2006-08-08 18:02 ` Richard Stallman
2006-08-08 19:26 ` Ken Manheimer
2006-08-09 14:42 ` Chong Yidong
2006-08-09 19:42 ` Ken Manheimer
2006-08-10 1:13 ` Richard Stallman
2006-08-10 16:08 ` Chong Yidong
2006-08-11 22:34 ` Stefan Monnier
2006-08-12 0:19 ` Kim F. Storm [this message]
2006-08-12 21:50 ` Richard Stallman
2006-08-12 4:02 ` Chong Yidong
2006-08-12 21:50 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r6zmztyf.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=ken.manheimer@gmail.com \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.