Re: system-wide input methods and unmodified keys

Re: system-wide input methods and unmodified keys

[Stefan Monnier]

> Ideally, the IM would only ever handle keypresses that would eventually
> call `self-insert-command' in emacs. I have no idea how this works,
> however -- I don't know which application "comes first" in receiving
> keypresses, and whether emacs could conceivably intercept these
> unmodified keys and prevent the IM from reading them. I imagine if the
> IM comes first, then there's no hope.

The IM comes first, indeed, hence the problems.  Maybe there's a way for
Emacs to temporarily suspend the external IM processing.  IF so, someone
will have to implement support for it :-(

But if/when such support is installed, we could maybe automatically
disable IM processing after C-x or in windows displaying
special-mode buffers.  That would be really welcome.


        Stefan

Re: system-wide input methods and unmodified keys

[Eric Abrahamsen]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Ideally, the IM would only ever handle keypresses that would eventually
>> call `self-insert-command' in emacs. I have no idea how this works,
>> however -- I don't know which application "comes first" in receiving
>> keypresses, and whether emacs could conceivably intercept these
>> unmodified keys and prevent the IM from reading them. I imagine if the
>> IM comes first, then there's no hope.
>
> The IM comes first, indeed, hence the problems.  Maybe there's a way for
> Emacs to temporarily suspend the external IM processing.  IF so, someone
> will have to implement support for it :-(
>
> But if/when such support is installed, we could maybe automatically
> disable IM processing after C-x or in windows displaying
> special-mode buffers.  That would be really welcome.

Bad news, but not a surprise. I would have no idea how to start
implementing that. Something tells me we'll all be using Wayland before
anyone gets to it :)

Re: system-wide input methods and unmodified keys

[Stefan Monnier]

> implementing that. Something tells me we'll all be using Wayland before
> anyone gets to it :)

Probably won't make much of a difference in this respect (this guess is
based on the fact that AFAIK the same problem plagues OSX and W32 users).


        Stefan

system-wide input methods and unmodified keys

[Eric Abrahamsen]

I'm using the FCITX system-wide input method (for Chinese) as I like
having the same input method in all applications. I'm using Emacs trunk,
and this IM works well with the usual env variables set:

export GTK_IM_MODULE=fcitx
export XMODIFIERS="@im=fcitx"
export QT_IM_MODULE=fcitx

and emacs started as "LC_CTYPE=zh_CN.UTF-8 /usr/local/bin/emacs"

I'm using StumpWM on plain X, no window manager.

The only problem when using emacs is that any unmodified key stroke goes
to the IM, not to emacs. Fine when you're typing, but highly annoying in
special modes like Dired where unmodified keys call commands other than
`self-insert-command', or in key-prefix combos like "C-x o", where emacs
gets the "C-x" and the IM gets the "o".

Ideally, the IM would only ever handle keypresses that would eventually
call `self-insert-command' in emacs. I have no idea how this works,
however -- I don't know which application "comes first" in receiving
keypresses, and whether emacs could conceivably intercept these
unmodified keys and prevent the IM from reading them. I imagine if the
IM comes first, then there's no hope.

Does anyone know more about the interaction between emacs and system
IMs? Is there any chance of getting what I want?

Thanks!
Eric