From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: arunisaac@systemreboot.net, 58070@debbugs.gnu.org
Subject: bug#58070: [PATCH] Add tamil99 input method
Date: Tue, 27 Sep 2022 13:04:48 +0530 [thread overview]
Message-ID: <87pmfhe0dj.fsf@gmail.com> (raw)
In-Reply-To: <83o7v1jpb0.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 27 Sep 2022 09:37:23 +0300")
[செவ்வாய் செப்டம்பர் 27, 2022] Eli Zaretskii wrote:
>> Emacs 29's delete-forward-char deletes by grapheme clusters now. It is
>> now a job of writing a backward version of the grapheme cluster
>> detection code. I poked around in the C code to see how
>> find-composition-internal was implemented, and it looked *relatively*
>> straightforward to get a backward searching function working. I might
>> be wrong here, so I hope Eli corrects my misunderstandings.
>
> I don't think I understand what you are after. Please elaborate on
> the "backward version of the grapheme cluster detection code", and its
> purpose in this context.
In delete-forward-char, we use find-composition to get the extend of the
current glyphs in terms of characters. AFAICT, find-composition does a
forward search for the 'composition' text property. My proposal was
that we write a find-composition variant that would do a backward search
for the 'composition' text property which we then can make of use in
delete-backward-char.
We cannot simply do backward-char then delete-forward-char and bind it
to a command since IIRC the grapheme cluster movement happens in the
display code? M-: (progn (backward-char 1) (delete-forward-char 1)) RET
deletes கு| to | (| being point) whereas if I define the above as a
command named test, and call it via M-x test RET it gives க| instead.
Which is why I said we need a "backward version of the grapheme cluster
detection code."
HTH.
next prev parent reply other threads:[~2022-09-27 7:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 10:00 bug#58070: [PATCH 0/1] Add tamil99 input method Arun Isaac
2022-09-25 10:02 ` bug#58070: [PATCH] " Arun Isaac
2022-09-25 11:38 ` Visuwesh
2022-09-25 13:59 ` Eli Zaretskii
2022-09-25 14:14 ` Visuwesh
2022-09-25 14:23 ` Eli Zaretskii
2022-09-25 14:38 ` Visuwesh
2022-09-25 15:55 ` Eli Zaretskii
2022-09-26 20:59 ` Arun Isaac
2022-09-27 6:25 ` Eli Zaretskii
2022-09-27 20:34 ` Arun Isaac
2022-09-26 20:55 ` Arun Isaac
2022-09-27 1:49 ` Visuwesh
2022-09-27 2:29 ` Visuwesh
2022-09-27 6:37 ` Eli Zaretskii
2022-09-27 7:34 ` Visuwesh [this message]
2022-09-27 7:53 ` Eli Zaretskii
2022-09-27 9:24 ` Robert Pluim
2022-09-27 9:40 ` Eli Zaretskii
2022-09-27 10:11 ` Visuwesh
2022-09-27 20:32 ` Arun Isaac
2022-09-27 6:23 ` Eli Zaretskii
2022-09-27 7:52 ` Visuwesh
2022-09-27 8:03 ` Eli Zaretskii
2022-09-27 10:15 ` Visuwesh
2022-10-12 8:40 ` Arun Isaac
2022-10-12 14:00 ` Eli Zaretskii
2022-10-15 8:23 ` Arun Isaac
2022-09-27 20:19 ` Arun Isaac
2022-09-27 20:26 ` Arun Isaac
2022-09-28 2:30 ` Eli Zaretskii
2022-09-25 10:13 ` bug#58070: [PATCH 0/1] " Eli Zaretskii
2022-09-25 11:16 ` Arun Isaac
2022-10-12 8:41 ` Arun Isaac
2022-10-12 13:55 ` Eli Zaretskii
2022-10-15 8:34 ` Arun Isaac
2022-10-15 9:16 ` bug#58070: [PATCH v2] " Arun Isaac
2022-10-15 14:42 ` bug#58070: [PATCH 0/1] " Visuwesh
2022-10-18 7:11 ` Arun Isaac
2022-10-18 18:00 ` bug#58070: [PATCH v3] " Arun Isaac
2022-10-19 11:41 ` 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=87pmfhe0dj.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=58070@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=eliz@gnu.org \
/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).