Subject: bug#63807: bug in compose-gstring-for-terminal?

From: Eli Zaretskii <[email-masked]>
Date: Wed, 31 May 2023 19:15:30 +0300

> From: Mattias Engdegård <[email-masked]>
> Date: Wed, 31 May 2023 17:08:58 +0200
> Cc: [email-masked]
> 
> I was unable to provoke that particular code to run for strings longer than 1 chars but that could just be my own ineptitude, and in any case it seems unsafe to rely on it. Maybe you could come up with an example?

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).

Anyway, if you feel safer to add to i, fine by me (on master, please).