From: Eli Zaretskii <eliz@gnu.org>
To: Richard Wordingham <richard.wordingham@ntlworld.com>
Cc: 20140@debbugs.gnu.org, handa@gnu.org, larsi@gnus.org
Subject: bug#20140: 24.4; M17n shaper output rejected
Date: Sat, 12 Feb 2022 20:54:20 +0200 [thread overview]
Message-ID: <83zgmvrk4j.fsf@gnu.org> (raw)
In-Reply-To: <20220208221310.734f8d75@JRWUBU2> (message from Richard Wordingham on Tue, 8 Feb 2022 22:13:10 +0000)
> Date: Tue, 8 Feb 2022 22:13:10 +0000
> From: Richard Wordingham <richard.wordingham@ntlworld.com>
> Cc: larsi@gnus.org, 20140@debbugs.gnu.org, Kenichi Handa <handa@gnu.org>
>
> On Sun, 06 Feb 2022 10:11:08 +0200
> Eli Zaretskii <eliz@gnu.org> wrote:
>
> > I don't see the commands forward-char-intrusive and
> > backward-char-intrusive anywhere in Emacs, so I guess they are your
> > local changes, based on the code posted by Handa-san in this
> > discussion?
>
> That's a shame; they are indeed local, sitting in my initialisation
> file (.emacs). (I future-proofed myself too well.) They are well worth
> adding to the general store of emacs commands, and mentioning in
> documentation next to forward-char and backward-char.
I've now added a similar feature to what will become Emacs 29 at some
future point. The code is based on that old post by Handa-san, but I
decided to change its user-facing aspects: instead of new commands, I
added a new user option, which, if set non-nil, disables
auto-composition at point, and thus allows point to "enter" the
composed sequence. I think this is better for 2 reasons:
. no need to introduce new cursor motion commands, for which it will
be hard to find a convenient key binding (using C-S-f/C-S-b will
conflict with the shift-selection feature, for example);
. the user option affects cursor motion by any means, so it's more
general thus I hope will be more convenient.
next prev parent reply other threads:[~2022-02-12 18:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 22:20 bug#20140: 24.4; M17n shaper output rejected Richard Wordingham
2015-03-19 3:43 ` Eli Zaretskii
2015-03-21 8:33 ` K. Handa
2015-03-21 17:20 ` Wolfgang Jenkner
2015-03-21 17:58 ` Richard Wordingham
2015-03-21 18:26 ` Eli Zaretskii
2015-03-25 14:25 ` K. Handa
2015-03-25 21:45 ` Richard Wordingham
2015-04-05 19:48 ` Richard Wordingham
2022-02-03 21:21 ` Lars Ingebrigtsen
2022-02-04 7:37 ` Eli Zaretskii
2022-02-05 22:52 ` Richard Wordingham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-06 8:11 ` Eli Zaretskii
2022-02-06 22:09 ` Richard Wordingham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-07 14:04 ` Eli Zaretskii
2022-02-07 23:38 ` Richard Wordingham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-08 22:13 ` Richard Wordingham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-12 18:54 ` Eli Zaretskii [this message]
2022-02-13 16:04 ` Eli Zaretskii
2022-02-13 20:53 ` Richard Wordingham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-14 13:19 ` Eli Zaretskii
2022-02-14 22:14 ` Richard Wordingham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-15 1:27 ` Richard Wordingham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-16 15:13 ` Eli Zaretskii
2022-02-16 15:12 ` Eli Zaretskii
2022-02-16 15:11 ` Eli Zaretskii
2022-02-13 19:49 ` Eli Zaretskii
2022-02-13 21:11 ` Richard Wordingham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-14 13:26 ` Eli Zaretskii
2022-02-14 23:26 ` Richard Wordingham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-15 14:40 ` Eli Zaretskii
2022-02-15 21:06 ` Richard Wordingham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-16 13:15 ` Eli Zaretskii
2022-02-16 19:01 ` Richard Wordingham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-16 19:20 ` 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=83zgmvrk4j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20140@debbugs.gnu.org \
--cc=handa@gnu.org \
--cc=larsi@gnus.org \
--cc=richard.wordingham@ntlworld.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.