unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 21456@debbugs.gnu.org, Zachary Acreman <zakk@acreman.net>
Subject: bug#21456: 24.5; Emacs does not respect fcitx as GTK input method
Date: Fri, 04 Dec 2020 10:13:13 -0800	[thread overview]
Message-ID: <877dpxo2x2.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87pn3pnbib.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 04 Dec 2020 10:53:00 +0100")


On 12/04/20 10:53 AM, Lars Ingebrigtsen wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Reproduction would likely require installing and configuring fcitx, if
>> you're willing to do that.
>
> Sure.
>
>> It's 100% reproducible, and I've started
>> Emacs like this for many years in order to make it work:
>>
>> env LC_CTYPE=zh_CN.UTF-8 /home/eric/dev/emacs/src/emacs
>>
>> I thought that might cause other weirdness in Emacs, but it never did,
>> not that I noticed.
>
> But how do you reproduce the error?

Start fcitx, configure it to toggle between English and Chinese, note
the "trigger key" (I've set mine to F7). Start Emacs, hit the trigger
key, and Emacs tells me "<f7> is undefined". In all other applications,
F7 toggles the input method.

It's been a while since I messed with this, so I did some
experimentation. I've had such hit-or-miss luck with using Emacs and the
system-wide input method that I think I've been using Emacs' own input
for a while. I'm using an Arch Linux machine running the sway Wayland
tiling window manager, and it turns out that under this setup fcitx
doesn't work in Emacs even with the LC_TYPE incantation that used to
work. I wasn't able to get the compose key to work either ("<print> is
undefined").

It's possible that the LC_TYPE thing will still work under X11.

I've been running the pgtk branch as a daily driver since it was added
to the repo, and under that branch both fcitx and the compose key work
as expected with no special configuration.

The package repos have a "fcitx" package, which I've never used, which
might solve this problem a different way.

HTH,
Eric





  reply	other threads:[~2020-12-04 18:13 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
2020-12-03 18:06   ` Eric Abrahamsen
2020-12-04  9:53     ` Lars Ingebrigtsen
2020-12-04 18:13       ` Eric Abrahamsen [this message]
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=877dpxo2x2.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=21456@debbugs.gnu.org \
    --cc=larsi@gnus.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).