Re: files completions for german umlauts

2026-01-10 12:23:41 +0100, Klaus Ethgen:
> Am Sa den 10. Jan 2026 um  9:57 schrieb Jonas Gilbricht:
> > Did you start with a minimal config?
> 
> That hint helped.
> 
> Recently (1. Dec) I added `unsetopt multibyte` to my config as I do not
> use any multibyte charset, not in filesystem and not in shell.
> 
> Setting that option on solves the problem. But it is wrong in my
> oppinion to leave that to on!
> 
> So I believe that to be a bug of zsh doing multibyte the wrong way.
[...]

I can reproduce with 5.9 with a .zshrc of

autoload -Uz compinit
compinit
set +o multibyte

And

$ mkdir -p Stéphane/Chazelas
$ cd Stéphane/<Tab>

in multibyte and singlebyte locales alike.

But not in the current git head. So presumably that bug has been
fixed already.

There's one remaining related bug in that if a path component
contains non-displayable characters/bytes, completion transforms
them to their $'...' notation and completion fails again.

That's in singlebyte and multibyte locales alike with the
multibyte option enabled or not.

For instance:

$ mkdir -p $'St\x01phane/Chazelas'
$ cd St<Tab>

completes to "cd St$'\001'phane" but then won't complete
further.

If I do:

$ cd 'St<Tab>

Then it completes to "cd 'St^Aphane/" with the ^A in reverse
video, and it lets me complete further to 'St^Aphane/Chazelas/,
but with:

$ cd $'St<Tab>

It completes to "cd $'St\001phane" and doesn't let me complete
further.

-- 
Stephane