From: phillip.lord@russet.org.uk (Phillip Lord)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Timing of input-method output
Date: Tue, 12 Feb 2019 12:21:51 +0000 [thread overview]
Message-ID: <87mun1w61s.fsf@russet.org.uk> (raw)
In-Reply-To: <jwvbm3inf56.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 11 Feb 2019 17:20:54 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Oh dear, that really does seem nasty to me.
>
> ;-)
>
>> I wonder if I am going about this in the wrong way. Given that this only
>> happens when quail is active, is it not quail that needs hooking?
>> "pre-quail-command-hook" or something. Quail knows that it's about to do
>> something weird that is not going to signal pre-command-hook because we
>> are still awaiting more information before the command happens.
>
> Yeah, it's probably better to try and hack Quail to better cooperate.
>
>> If it works, it would mean that input-event-functions is not really fit
>> for the purpose I intended and should, perhaps, be removed.
>
> When you added it, I thought you had already confirmed that it satisfies
> your needs. But if it doesn't, then maybe it's not a good hook.
Well, I had checked that it did do what I wanted, in terms of stopping
the buggy completion display. I hadn't checked that it didn't break
the completion in the first place. Oh dear.
I'll remove this and see if I can fix up quail instead with a hook
there. As you say, perhaps the ultimate fix is to change quail to enter
information in a different way, but one step at a time.
Phil
next prev parent reply other threads:[~2019-02-12 12:21 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
2019-02-11 22:10 ` Phillip Lord
2019-02-11 22:20 ` Stefan Monnier
2019-02-12 12:21 ` Phillip Lord [this message]
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=87mun1w61s.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).