From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: 56237@debbugs.gnu.org
Subject: bug#56237: 29.0.50; delete-forward-char fails to delete character
Date: Sun, 26 Jun 2022 19:57:46 +0300 [thread overview]
Message-ID: <83v8sn8ir9.fsf@gnu.org> (raw)
In-Reply-To: <87fsjr9xs6.fsf@gmail.com> (message from Visuwesh on Sun, 26 Jun 2022 22:17:53 +0530)
> From: Visuwesh <visuweshm@gmail.com>
> Cc: 56237@debbugs.gnu.org
> Date: Sun, 26 Jun 2022 22:17:53 +0530
>
> [ஞாயிறு ஜூன் 26, 2022] Eli Zaretskii wrote:
>
> > Sorry, I misunderstood the report.
> >
> > I tried to fix this now on master.
>
> Thanks for the quick fix! Unfortunately, delete-forward-char still
> deletes two clusters instead of one in "ப்போ". :(
They aren't two clusters, they are two graphemes that are part of a
single grapheme cluster.
Invoke find-composition, and you will see that it returns a single
composition there.
> I.e.,
>
> |ப்போ becomes |
>
> where | denotes the point.
This is the intended behavior.
next prev parent reply other threads:[~2022-06-26 16:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 16:07 bug#56237: 29.0.50; delete-forward-char fails to delete character visuweshm
2022-06-26 16:13 ` Visuwesh
2022-06-26 16:18 ` Eli Zaretskii
2022-06-26 16:24 ` Lars Ingebrigtsen
2022-06-26 16:25 ` Visuwesh
2022-06-26 16:36 ` Eli Zaretskii
2022-06-26 16:47 ` Visuwesh
2022-06-26 16:57 ` Eli Zaretskii [this message]
2022-06-26 17:06 ` Visuwesh
2022-06-26 17:26 ` Eli Zaretskii
2022-06-26 18:01 ` Eli Zaretskii
2022-06-27 5:31 ` Visuwesh
2022-06-27 5:47 ` Visuwesh
2022-06-27 12:39 ` Eli Zaretskii
2022-06-27 14:24 ` Visuwesh
2022-06-27 15:53 ` Eli Zaretskii
2022-07-02 7:03 ` Visuwesh
2022-07-16 12:50 ` Visuwesh
2022-07-16 13:31 ` Eli Zaretskii
2022-07-16 13:43 ` Visuwesh
2022-06-26 16:38 ` 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
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=83v8sn8ir9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56237@debbugs.gnu.org \
--cc=visuweshm@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).