GNU bug report logs - #58070
[PATCH 0/1] Add tamil99 input method

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Arun Isaac <arunisaac <at> systemreboot.net>
Cc: 58070 <at> debbugs.gnu.org, visuweshm <at> gmail.com
Subject: bug#58070: [PATCH] Add tamil99 input method
Date: Wed, 28 Sep 2022 05:30:33 +0300

> From: Arun Isaac <arunisaac <at> systemreboot.net>
> Cc: visuweshm <at> gmail.com, 58070 <at> debbugs.gnu.org
> Date: Wed, 28 Sep 2022 01:56:21 +0530
> 
> > There's a problem with the above: in some situations you want deletion
> > by codepoints, in others you want deletion by grapheme clusters.  (It
> > is possible that with Tamil the former is rarely the case, but it is
> > definitely a frequent case with other scripts, in particular with
> > those that have diacriticals.)  Emacs 29 solves this by having
> > delete-forward-char, which is usually bound to the <Delete> key,
> > delete by grapheme clusters, while DEL (which deletes backward) and
> > C-d delete individual codepoints.  The primary motivation for DEL to
> > delete by codepoints is that it allows you to make sub-grapheme
> > corrections to stuff you just typed, for example if you typed an
> > incorrect accent.
> >
> > Emacs 29 also has the composition-break-at-point variable, which you
> > could set non-nil, in which case <Delete> will also work by
> > codepoints.
> 
> I see. You're saying that the deletion by grapheme clusters or by
> codepoints may be a matter of preference.

Not preference, but the specific use case.

> In that case, it would be nice to have a variable similar to
> composition-break-at-point that would enable deletion by grapheme
> clusters.

We already do have that: <Delete> does that in Emacs 29.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.