Subject: Re: bug#22169: 25.0.50; File name compiletion doesn't work with non-ASCII characters on OS X

From: Eli Zaretskii <[email-masked]>
Date: Tue, 15 Dec 2015 18:11:45 +0200

> Date: Tue, 15 Dec 2015 11:21:17 +0100
> From: Anders Lindgren <[email-masked]>
> Cc: Eli Zaretskii <[email-masked]>, [email-masked]
> 
>     > I tried setting it to nil. This made completion work. However, the
>     letters
>     > are presented in decomposed form, so that pressing backspace first
>     converts
>     > "å" to "a", a second backspace deletes the "a" -- this is not how we
>     would
>     > like to present file names to users.
>     
>     That's how composed characters work in Emacs.
> 
> The OS X file system *stores* filenames in a decomposed manner, that is true.
> However, they should be presented to the user as normal (composed) characters.
> If `file-name-coding-system' has the original value, they are. However, the
> problem is that the completion mechanism fails to handle this case, which is a
> bug and it should be fixed.

Andreas just pointed out that when character composition happens at
display time, the behavior you observe is normal, that's all.

The issue of why completion doesn't work still exists.