From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: emacs-devel@gnu.org
Subject: Re: Timing of input-method output
Date: Wed, 06 Feb 2019 17:55:39 -0500 [thread overview]
Message-ID: <jwvpns47cs1.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <878syssgr6.fsf@russet.org.uk> (Phillip Lord's message of "Wed, 06 Feb 2019 22:18:21 +0000")
> I'm guessing this is because of the location of the input-event-function
> call. It's happening too soon, before quail has done anything to respond
> to the keypress that will result in complex input happening.
Oh, here's another random idea:
in input-event-functions, start a timer to run "right away" (i.e. at
the next occasion, which will be when we finish processing the
current key and start waiting for the next).
-- Stefan
next prev parent reply other threads:[~2019-02-06 22:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190122214637.25164.20429@vcs0.savannah.gnu.org>
[not found] ` <20190122214639.B2E13203DD@vcs0.savannah.gnu.org>
2019-01-22 23:17 ` master 7b31de4: Add hook for all events Michael Albinus
2019-01-23 22:56 ` Phillip Lord
2019-01-24 3:36 ` Eli Zaretskii
2019-01-23 1:30 ` [Emacs-diffs] " Daniel Colascione
2019-01-23 23:10 ` Phillip Lord
2019-01-24 2:06 ` Stefan Monnier
2019-01-24 10:41 ` Phillip Lord
2019-01-25 13:56 ` Stefan Monnier
2019-01-28 9:42 ` Phillip Lord
2019-01-26 0:50 ` Stefan Monnier
2019-01-28 9:54 ` Phillip Lord
2019-02-02 16:13 ` Timing of input-method output (was: [Emacs-diffs] master 7b31de4: Add hook for all events) Stefan Monnier
2019-02-03 22:06 ` Timing of input-method output Phillip Lord
2019-02-05 14:49 ` Stefan Monnier
2019-02-06 22:18 ` Phillip Lord
2019-02-06 22:55 ` Stefan Monnier [this message]
2019-02-11 22:10 ` Phillip Lord
2019-02-11 22:20 ` Stefan Monnier
2019-02-12 12:21 ` Phillip Lord
2019-03-25 21:48 ` Phillip Lord
2019-03-26 15:12 ` Stefan Monnier
2019-03-28 13:54 ` Phillip Lord
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=jwvpns47cs1.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/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).