GNU bug report logs - #27312
25.2; can't activate fcitx even though env is set up correctly

Previous Next

Package: emacs;

Reported by: Leonard Lausen <leonard <at> lausen.nl>

Date: Sat, 10 Jun 2017 16:42:01 UTC

Severity: normal

Merged with 21456

Found in versions 24.5, 25.2

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

Message #8 received at 27312 <at> debbugs.gnu.org (full text, mbox):

From: npostavs <at> users.sourceforge.net
To: Leonard Lausen <leonard <at> lausen.nl>
Cc: 27312 <at> debbugs.gnu.org
Subject: Re: bug#27312: 25.2;
 can't activate fcitx even though env is set up correctly
Date: Wed, 14 Jun 2017 20:10:56 -0400

Leonard Lausen <leonard <at> lausen.nl> writes:

> Even though all environment variables are (afaik) set up correctly, and
> fcitx is working in all other programs, it does not work in emacs GUI
> mode. It works fine if I start emacs in the terminal.

By the "GUI mode" do you mean 'emacs' vs 'emacs -nw'?  Or do you mean
that the you use a different kind of launcher?

> I compiled emacs myself using the Gentoo ebuild.
>
> I would be very thankful for any suggestions. Currently I believe it is
> a bug in emacs (?).
>
> Specifically:
> ➜  ~ cat .xprofile
> export XMODIFIERS=@im=fcitx
> export QT_IM_MODULE=fcitx
> export GTK_IM_MODULE=fcitx
> export LC_CTYPE=zh_CN.UTF-8

If you evaluate (getenv "XMODIFIERS") do you get the expected value?
Does evaluating (setenv "XMODIFIERS" "@im=fcitx") help?
This bug report was last modified 3 years and 167 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.