From: Po Lu <luangruo@yahoo.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: GTK Emacs and input modules
Date: Sun, 04 Sep 2022 20:53:54 +0800 [thread overview]
Message-ID: <878rmzcnbx.fsf@yahoo.com> (raw)
In-Reply-To: <CAP_d_8VUrWtgJhenHop6OEDngcbSfz3BvbHG1LCi6gm8_zqx5A@mail.gmail.com> (Yuri Khan's message of "Sun, 4 Sep 2022 16:26:48 +0700")
Yuri Khan <yuri.v.khan@gmail.com> writes:
> Never encountered any, except for the C-S-u issue.
Select all of a large file, such as xdisp.c or xterm.c in the Emacs
source code, and try to insert it into another program.
Emacs will probably crash with a BadAlloc error.
> Just so that I’m prepared: do the C-S-u and C-; problems exist in PGTK
> Emacs on Wayland?
Yes, unless you also run (pgtk-use-im-context nil).
prev parent reply other threads:[~2022-09-04 12:53 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
2022-09-04 12:53 ` Po Lu [this message]
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=878rmzcnbx.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=help-gnu-emacs@gnu.org \
--cc=yuri.v.khan@gmail.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).