bug#63837: closed (29.0.91; delete-forward-char error with composed text)

[GNU bug Tracking System]

Your message dated Fri, 02 Jun 2023 17:30:47 +0300
with message-id <83v8g69bs8.fsf@gnu.org>
and subject line Re: bug#63837: 29.0.91; delete-forward-char error with 
composed text
has caused the debbugs.gnu.org bug report #63837,
regarding 29.0.91; delete-forward-char error with composed text
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
63837: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63837
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 29.0.91; delete-forward-char error with composed text
>
>
>
>
> Date: 
>
> Fri, 2 Jun 2023 10:42:29 +0000
>
>
>
>
> * How to reproduce:
>
> 0. Start emacs with `emacs -Q'
> 1. Create some text composition, e.g. eval: `(insert (compose-chars ?+))'
> 2. Move cursor to before composed character
> 3. `M-x delete-forward-char' or press <delete> key
>
> * Backtrace:
>
> Debugger entered--Lisp error: (wrong-type-argument sequencep t)
>   lgstring-glyph-boundary(t 1 2)
>   delete-forward-char(1 nil)
>   funcall-interactively(delete-forward-char 1 nil)
>   call-interactively(delete-forward-char nil nil)
>   command-execute(delete-forward-char)
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#63837: 29.0.91; delete-forward-char error with composed text
>
>
>
>
> Date: 
>
> Fri, 02 Jun 2023 17:30:47 +0300
>
>
>
>
> > From: Thiago Melo <tmdmelo@gmail.com>
> > Date: Fri, 2 Jun 2023 13:42:19 +0000
> > Cc: Robert Pluim <rpluim@gmail.com>, 63837@debbugs.gnu.org
> > 
> > On Fri, Jun 2, 2023 at 12:48 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > > I fixed that on emacs-29.
> > 
> > Thanks, Eli.  It also works for me.
>
> Thanks, closing the bug.
>
> > I also saw the related Bug#56237.  From what I could test, it seems
> > your fix doesn't cause a regression in their use case.  Right? (eg,
> > when deleting the text "ரு போ").
>
> The current fix didn't touch that case, it only touched the case of
> static compositions, not automatic compositions.
>
>
> --- End Message ---