From: Eli Zaretskii <eliz@gnu.org>
To: SUKBEOM KIM <sukbeom.kim@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Kenichi Handa <handa@gnu.org>
Cc: 66970@debbugs.gnu.org
Subject: bug#66970: 29.1; Overwrite-mode is not working with Korean characters
Date: Wed, 08 Nov 2023 15:18:59 +0200 [thread overview]
Message-ID: <83leb81iyk.fsf@gnu.org> (raw)
In-Reply-To: <559fe1a8-a18e-4d8c-81c3-78fd3bbddbcc@gmail.com> (message from SUKBEOM KIM on Tue, 7 Nov 2023 08:19:53 +0900)
> Date: Tue, 7 Nov 2023 08:19:53 +0900
> From: SUKBEOM KIM <sukbeom.kim@gmail.com>
>
> Yes, it is the problem only with typing via an input method.
> I checked that there is no issue if I type Korean characters with iBus
> (I guess this is the 'LEIM' what you mentioned).
It looks like the Korean input methods in Leim don't support Overwrite
mode: they use 'insert' (see 'hangul-insert-character'), whereas
Overwrite mode is supported only by self-insert-command, which
requires to push the characters on the unread-command-events instead
of explicitly inserting them.
Stefan, Kenichi: any ideas or suggestions for how to fix this?
next prev parent reply other threads:[~2023-11-08 13:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 16:07 bug#66970: 29.1; Overwrite-mode is not working with Korean characters SUKBEOM KIM
2023-11-06 16:37 ` bug#66970: (no subject) SUKBEOM KIM
2023-11-06 17:03 ` Eli Zaretskii
2023-11-06 23:19 ` bug#66970: 29.1; Overwrite-mode is not working with Korean characters SUKBEOM KIM
2023-11-08 13:18 ` Eli Zaretskii [this message]
2023-11-08 0:48 ` bug#66970: (no subject) Sukbeom Kim
2023-11-06 16:41 ` bug#66970: 29.1; Overwrite-mode is not working with Korean characters Eli Zaretskii
2023-11-09 16:37 ` João Távora
2023-11-09 16:50 ` Eli Zaretskii
2023-11-10 0:34 ` Sukbeom Kim
2023-11-10 7:13 ` Eli Zaretskii
2023-11-10 22:32 ` Sukbeom Kim
2023-11-13 12:41 ` João Távora
2023-11-13 14:31 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83leb81iyk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66970@debbugs.gnu.org \
--cc=handa@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=sukbeom.kim@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.