Bug#99933: second attempt at more comprehensive unicode policy
On Jan 04, Robert Bihlmeyer <firstname.lastname@example.org> wrote:
>Considering old standards broken because a newer one exists is just
>> I've noticed that UTF-8 sometimes makes zsh unhappy, [...]
>That's quite an understatement. The commandline editor can't deal with
>multibyte characters in any way. So for example entering an o umlaut
>and then deleting it gets you in trouble, because zsh does not handle
>the two byte sequence as one character.
The same applies to bash. There has been patch in the BTS for a very
long time but it has never been applied.