From: storm@cua.dk (Kim F. Storm)
Cc: michael.cadilhac@lrde.org, emacs-devel@gnu.org
Subject: Re: The order input events are processed.
Date: Mon, 11 Sep 2006 16:17:37 +0200 [thread overview]
Message-ID: <m3lkoqh4hq.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1GMmW1-0001zC-8H@fencepost.gnu.org> (Richard Stallman's message of "Mon\, 11 Sep 2006 10\:12\:01 -0400")
Richard Stallman <rms@gnu.org> writes:
> It used unread-post-input-method-events instead of unread-command-events
> to ensure that the event is pushed back on the first list of events
> processed by read-event.
>
> That change is not right, I think. Using
> unread-post-input-method-events instead of unread-command-events
> alters the way the events are processed: it does goto reread_first
> instead of goto reread_for_input_method.
But since the event was returned by read-event, hasn't it been through
the "for_input_method" code already? So passing through once more
seems like a bug to me.
But I don't quite understand this input method stuff, so I suppose
you are right.
> With your change (or my change), we know that these lists are
> empty when read-event is called. That being so, I think it is fine
> to put the event back in unread-command-events.
Ok.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-09-11 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 11:21 The order input events are processed Michaël Cadilhac
2006-09-09 20:45 ` Richard Stallman
2006-09-10 9:08 ` Michaël Cadilhac
2006-09-10 13:05 ` Richard Stallman
2006-09-10 13:14 ` Michaël Cadilhac
2006-09-10 21:28 ` Kim F. Storm
2006-09-11 14:12 ` Richard Stallman
2006-09-11 14:17 ` Kim F. Storm [this message]
2006-09-11 14:11 ` Richard Stallman
2006-09-11 14:19 ` Kim F. Storm
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=m3lkoqh4hq.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=michael.cadilhac@lrde.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.