From: Yuri Khan <yuri.v.khan@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: GTK Emacs and input modules
Date: Sun, 4 Sep 2022 16:26:48 +0700 [thread overview]
Message-ID: <CAP_d_8VUrWtgJhenHop6OEDngcbSfz3BvbHG1LCi6gm8_zqx5A@mail.gmail.com> (raw)
In-Reply-To: <87k06jcz86.fsf@yahoo.com>
On Sun, 4 Sept 2022 at 15:37, Po Lu <luangruo@yahoo.com> wrote:
> > On the plus side, I won’t need to look for it when I migrate to
> > Wayland. On the minus side, I’m currently on X and I know your
> > warnings about PGTK Emacs on X not being a recommended configuration.
>
> It's not only recommended, it comes with severe defects up to and
> including crashes.
Never encountered any, except for the C-S-u issue.
> > I do not want any input module, not even the default one that seems to
> > grab Ctrl+Shift+U.
>
> Try GTK_IM_CONTEXT=simple.
No, with this build, Ctrl+Shift+U still pops up an underlined ‘u’ and
ignores keypresses up to the next entered hexadecimal digit.
> But your best option is simply to not use the PGTK build, and to put
> this in your ~/.Xresources:
>
> Emacs.useXIM: false
>
> Thanks.
I’ll try that, thank you.
Just so that I’m prepared: do the C-S-u and C-; problems exist in PGTK
Emacs on Wayland?
next prev parent reply other threads:[~2022-09-04 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 15:59 GTK Emacs and input modules Yuri Khan
2022-09-03 16:03 ` Yuri Khan
2022-09-04 0:39 ` Po Lu
2022-09-04 0:38 ` Po Lu
2022-09-04 8:00 ` Yuri Khan
2022-09-04 8:36 ` Po Lu
2022-09-04 9:26 ` Yuri Khan [this message]
2022-09-04 12:53 ` Po Lu
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=CAP_d_8VUrWtgJhenHop6OEDngcbSfz3BvbHG1LCi6gm8_zqx5A@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--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.
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).