bug#63807: closed (bug in compose-gstring-for-terminal?)

[GNU bug Tracking System]

Your message dated Wed, 31 May 2023 19:23:46 +0200
with message-id <48CD3569-59E9-46E8-9072-A8573D248692@gmail.com>
and subject line Re: bug#63807: bug in compose-gstring-for-terminal?
has caused the debbugs.gnu.org bug report #63807,
regarding bug in compose-gstring-for-terminal?
to be marked as done.

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


-- 
63807: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63807
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> bug in compose-gstring-for-terminal?
>
>
>
>
> Date: 
>
> Tue, 30 May 2023 22:36:18 +0200
>
>
>
>
> There is what appears to be a little code accident in 
> compose-gstring-for-terminal, at composite.el:821:
>
>               (setq i (+ 2)))
>
> but someone who knows the character composition code better should have a look. 
> The remedy seems obvious, though.
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#63807: bug in compose-gstring-for-terminal?
>
>
>
>
> Date: 
>
> Wed, 31 May 2023 19:23:46 +0200
>
>
>
>
> 31 maj 2023 kl. 18.15 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > I don't think such examples exist, because then we wouldn't need to
> > prepend a space (the character would compose with the preceding one).
>
> Yes, that could very well be the case, but it would take more time and effort 
> to prove it.
>
> > Anyway, if you feel safer to add to i, fine by me (on master, please).
>
> I'll do that, on master naturally. Thank you.
>
>
>
>
> --- End Message ---