unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 王会斌 <fighter90@163.com>
Cc: 53172@debbugs.gnu.org
Subject: bug#53172: 29.0.50; cannot use fcitx5 after upgrading emacs
Date: Tue, 11 Jan 2022 16:17:51 +0800	[thread overview]
Message-ID: <87lezmn0sw.fsf@yahoo.com> (raw)
In-Reply-To: <76292c7e.6c6.17e46bd9f5b.Coremail.fighter90@163.com> ("王会斌"'s message of "Tue, 11 Jan 2022 09:25:39 +0800 (CST)")

王会斌 <fighter90@163.com> writes:

> From: wanghb@arch.mail-host-address-is-not-set
>
> To: bug-gnu-emacs@gnu.org
>
> Subject: 29.0.50; cannot use fcitx5 after upgrading emacs
>
> Date: Tue, 11 Jan 2022 09:22:01 +0800
>
> Message-ID: <87pmoz9idi.fsf@arch.mail-host-address-is-not-set>
>
> --text follows this line--
>
> After upgrading emacs to the latest version, I cannot enable fcitx5 in
>
> emacs.
>
> When I try to enable it, the frame of fcitx just appears and disappears
>
> quickly.
>
> The version that does not has this issue I know is
>
> emacs-git-29.0.50.153249-1-x86_64.pkg.tar.zst. And the version I am
>
> using, which has this issue, is 29.0.50.153486-1.

I tend to suspect this is an fcitx bug caused by some of the recent
changes to XIM support on master (Emacs is essentially the last
remaining XIM client that is actually used, along with WPS Office, so it
doesn't get very good support from modern input method frameworks.)

Please try launching Emacs with like below in turn, and tell with which
options fcitx remains broken:

  emacs -q -xrm 'Emacs.inputStyle: none'
  emacs -q -xrm 'Emacs.inputStyle: offthespot'
  emacs -q -xrm 'Emacs.inputStyle: overthespot'
  emacs -q -xrm 'Emacs.inputStyle: root'
  emacs -q -xrm 'Emacs.inputStyle: callback'

Thanks.





  reply	other threads:[~2022-01-11  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  1:25 bug#53172: 29.0.50; cannot use fcitx5 after upgrading emacs 王会斌
2022-01-11  8:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-10 11:43   ` 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=87lezmn0sw.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53172@debbugs.gnu.org \
    --cc=fighter90@163.com \
    --cc=luangruo@yahoo.com \
    /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).