Right, that’s one workaround; you can emacs-specific input methods in a pinch. But it’s not so nice since you have to duplicate your configuration, keyboard settings, user dictionaries etc. And IMEs are self-learning systems, so it’s a bit of a shame to split their training.
--- I was wrong in thinking this was a regression. Rather, what triggered it was the uim-xim daemon not running (seems like some upgrade broke my X init scripts—is it just me or gnome is making it harder and harder to just run a command at startup?). I would still consider this a bug (Multi_key should work regardless) but it’s an edge case, since usually IME users will need the daemon running anyway. Here are some steps to reproduce: 1. Assign a key to Multi_key using xmodmap (if you're on Xorg; if on Wayland, do whatever they do to assign a Compose key). On my keyboard, "xmodmap -e 'keycode 135' = Multi_key" will assign the "menu" key to it. (xev(1) can tell the keycode number of a key.) 2. Test it elsewhere; e.g. <Multi_key s s> should output 'ß'. 3. env XMODIFIERS= emacs -q; test Multi_key (in my system it works). 4. Without the IME daemon running, env XMODIFIERS=@im=uim emacs -q (here this breaks Multi_key support.) 5. uim-xim &; retry last command (now Multi_key works again). Experimentally, I note that setting XMODIFIERS=@im=asdfg (or any other garbage) will also trigger the bug, but not XMODIFIERS=asdfg or XMODIFIERS=@foo=bar. So it seems like it's specifically the @im= modifier that may cause problems. Warm regards, -- Melissa 2020年4月25日(土) 14:03 era <[email protected]>: > On Sat, Apr 25, 2020, at 12:09, Melissa Boiko wrote: > > I would appreciate any current workarounds, because this bug renders > Emacs > > unusable for my case (I’m a linguist writing my thesis in Latex using > > Japanese, IPA and other writing systems). > > The documentation in the Debian wiki suggests using alternative means for > Japanese input specifically with Emacs. > > https://wiki.debian.org/JapaneseEnvironmentE currently says > > > emacs has its own unique Japanese input infrastructure (egg etc.) > > which does not rely on external programs such as X nor FEP. > > > > If you wish to input without going through XIM, set XMODIFIERS value > > to "none" while starting emacs. From shell, execute as: > > $ XMODIFIERS=none emacs > > I'm not familiar enough with these things to tell whether the information > there is current and accurate, but it came up as I was figuring out these > things. > > (I don't think I can solve your problem; I was just figuring out what it > would take for someone who - like myself - is unfamiliar with IME etc to > repro. Perhaps it would be useful to summarize how your system is > configured and what keystrokes and perhaps mouse clicks it requires to > correctly input an IPA symbol like ʃ (U+0283) when this bug is fixed.) > > -- > If this were a real .signature, it would suck less. Well, maybe not. >
