From: michael.cadilhac@lrde.org (Michaël Cadilhac)
Cc: emacs-devel@gnu.org
Subject: Re: The order input events are processed.
Date: Sun, 10 Sep 2006 11:08:53 +0200 [thread overview]
Message-ID: <87ejukt7fe.fsf@lrde.org> (raw)
In-Reply-To: <E1GM9hu-0003Ha-57@fencepost.gnu.org> (Richard Stallman's message of "Sat, 09 Sep 2006 16:45:42 -0400")
[-- Attachment #1.1: Type: text/plain, Size: 1563 bytes --]
Richard Stallman <rms@gnu.org> writes:
> The whole point of unread-post-input-method-events is to be processed
> first. Changing it to operate last will break it. When an input method
> runs and generates a sequence of several events, those events must
> be processed before whatever is in unread-command-events.
Ok, seems reasonable ;-)
> One way to fix it is for sit_for to test these variables directly
> so that it doesn't need to change them. Does anyone see a problem
> with that?
Does it mean that sit-for will have to do active wait [1] ? I think
it's not a good way to go, or have we an alternative?
In a first place, I thought that `read-char' could store the var from
which the char read has been taken, so that a function `putback-char'
could but it back in the good list. How about that ?
However, I've always dreamt about an unique entry point for
unread-events: unread-command-events would store direct events (u-c-e
= '(?a ?b)) or events as a cons, the cdr telling if input-method has
to be used (u-c-e = '(?a (?b . nil) ?c)). Does it seems crazy? [2]
Footnotes:
[1] (while (not (or unread-command-events unread-*))
)
[2] Of course, _after_ the release ;-)
--
| Michaël `Micha' Cadilhac | La culture c'est comme la confiture, |
| Epita/LRDE Promo 2007 | c'est meilleur avec du pain. |
| http://www.lrde.org/~cadilh_m | -- MOI59 |
`-- - JID: micha@amessage.be --' - --'
[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2006-09-10 9:08 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 [this message]
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
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
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=87ejukt7fe.fsf@lrde.org \
--to=michael.cadilhac@lrde.org \
--cc=emacs-devel@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).