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 23:22:33 -0400 [thread overview]
Message-ID: <87mv9arl3a.fsf@users.sourceforge.net> (raw)
In-Reply-To: <482d503a-4e11-3824-ae3e-c924bee8aca2@lausen.nl> (Leonard Lausen's message of "Thu, 15 Jun 2017 10:55:55 +0900")
Leonard Lausen <leonard@lausen.nl> writes:
>> If you evaluate (getenv "XMODIFIERS") do you get the expected value?
>> Does evaluating (setenv "XMODIFIERS" "@im=fcitx") help?
>
> (getenv "XMODIFIERS") returns in "@im=fcitx" for both modes ("emacs -Q"
> and "emacs -Q -nw"). Running a further (setenv "XMODIFIERS" "@im=fcitx")
> does not make any difference.
Ok, I see that according to Bug#10867, it should work with your setup.
Have you ever got it working with older Emacs versions?
I guess you've also verified that 'locale -a' shows 'zh_CN.UTF-8'? I'm
afraid I don't know how to troubleshoot this any further.
> Note that if I press the Ctrl-Space key (which should change the fcitx
> input method) "emacs -Q" reports "Mark set" and "Mark deactivated",
> while for "emacs -Q -nw" the input method is changed correctly (i.e. I
> can input Chinese characters thereafter).
Yeah, I guess for 'emacs -nw' it's really the terminal program that
handles the input method, Emacs doesn't know anything about it.
next prev parent reply other threads:[~2017-06-15 3:22 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
2017-06-15 1:55 ` Leonard Lausen
2017-06-15 3:22 ` npostavs [this message]
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=87mv9arl3a.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).