unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Zachary Acreman <zakk@acreman.net>
Cc: 21456@debbugs.gnu.org
Subject: bug#21456: 24.5; Emacs does not respect fcitx as GTK input method
Date: Thu, 03 Dec 2020 12:04:37 +0100	[thread overview]
Message-ID: <87k0tztaka.fsf@gnus.org> (raw)
In-Reply-To: <55F2493F.5070007@acreman.net> (Zachary Acreman's message of "Thu, 10 Sep 2015 22:23:43 -0500")

Zachary Acreman <zakk@acreman.net> writes:

> Emacs compiled with GTK does not respect fcitx as the system-wide GTK
> input method.
>
> When I use a keyboard configuration with right-alt mapped to Compose, I
> get "<Multi-key> is undefined" messages in Emacs instead of the expected
> behavior.
>
> When I use a keyboard configuration with dead keys for accented
> characters, I get messages like "<dead-acute> is undefined" instead of
> the expected behavior.
>
> Chinese Pinyin input methods are ignored.
>
> XMODIFIERS=@im=fcitx
> GTK_IM_MODULE=fcitx
>
> fcitx input works correctly in every other application on this system
> that I have tested.

(This bug report unfortunately got no response at the time.)

Do you have a recipe, starting from "emacs -Q", to reproduce this issue?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-12-03 11:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11  3:23 bug#21456: 24.5; Emacs does not respect fcitx as GTK input method Zachary Acreman
2020-12-03 11:04 ` Lars Ingebrigtsen [this message]
2020-12-03 18:06   ` Eric Abrahamsen
2020-12-04  9:53     ` Lars Ingebrigtsen
2020-12-04 18:13       ` Eric Abrahamsen
2020-12-06 13:11         ` Lars Ingebrigtsen
2020-12-06 17:56           ` Eric Abrahamsen
2020-12-07 13:48             ` Lars Ingebrigtsen

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=87k0tztaka.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=21456@debbugs.gnu.org \
    --cc=zakk@acreman.net \
    /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).