unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Leonard Lausen <leonard@lausen.nl>
Cc: 27312@debbugs.gnu.org
Subject: bug#27312: 25.2; can't activate fcitx even though env is set up correctly
Date: Wed, 14 Jun 2017 20:10:56 -0400	[thread overview]
Message-ID: <87r2ymrtyn.fsf@users.sourceforge.net> (raw)
In-Reply-To: <7db29009-200d-4921-20b1-71e2df37e67f@lausen.nl> (Leonard Lausen's message of "Sat, 10 Jun 2017 16:37:09 +0900")

Leonard Lausen <leonard@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?





  reply	other threads:[~2017-06-15  0:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-10  7:37 bug#27312: 25.2; can't activate fcitx even though env is set up correctly Leonard Lausen
2017-06-15  0:10 ` npostavs [this message]
2017-06-15  1:55   ` Leonard Lausen
2017-06-15  3:22     ` npostavs
2017-06-15  3:55       ` Eli Zaretskii
2017-06-15  4:47         ` Leonard Lausen
2021-12-09  3:40 ` bug#27312: bug#21456: 24.5; Emacs does not respect fcitx as GTK input method Mingde (Matthew) Zeng
2021-12-10  0:42   ` bug#21456: " Lars Ingebrigtsen
2021-12-09  3:42 ` Mingde (Matthew) Zeng

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=87r2ymrtyn.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=27312@debbugs.gnu.org \
    --cc=leonard@lausen.nl \
    /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).