From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56237@debbugs.gnu.org, 56237-done@debbugs.gnu.org
Subject: bug#56237: 29.0.50; delete-forward-char fails to delete character
Date: Sat, 16 Jul 2022 18:20:46 +0530 [thread overview]
Message-ID: <87edylfcgp.fsf@gmail.com> (raw)
In-Reply-To: <87h740j8rs.fsf@gmail.com> (Visuwesh's message of "Sat, 02 Jul 2022 12:33:51 +0530")
reopen 56237
thanks
[சனி ஜூலை 02, 2022] Visuwesh wrote:
> [திங்கள் ஜூன் 27, 2022] Eli Zaretskii wrote:
>
>>> Thanks, it is much better now! It doesn't fail on the cases that I had
>>> problems with so far.
>>
>> Thanks for testing, and feel free to close whenever you feel satisfied ;-)
>
> Closing issue since I haven't noticed anything funny. Thanks again for
> the quick fixes!
This command somehow to have been regressed. With the HEAD at
0190dff96a, the command works perfectly fine but with current master, it
fails to delete by entire clusters: it behaves identical to delete-char.
With the point being |,
|ரு
after <Delete>, becomes
|ு
instead of |.
Can you please take a look, Eli?
next prev parent reply other threads:[~2022-07-16 12:50 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
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 [this message]
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=87edylfcgp.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=56237-done@debbugs.gnu.org \
--cc=56237@debbugs.gnu.org \
--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).