bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#22169: 25.0.50; File name compiletion doesn't work with non-ASCII ch


From: Anders Lindgren
Subject: bug#22169: 25.0.50; File name compiletion doesn't work with non-ASCII characters on OS X
Date: Thu, 17 Dec 2015 23:01:01 +0100

Hi!

I think I have solved this.

The current coding system defined in ns-win.el didn't work because it only provided a decode but no encode functions.

After revisiting the "hfs" encoder, I managed to get it to work, this time.

Below is a patch where I have dropped the old encoder and use the new instead. The only thing noteworthy is that `ucs-normalize' is loaded by loadup (when ns is used) and thus included in the dumped Emacs (if I understand correctly). Unless anybody objects, I'll push it in a couple of days.

    -- Anders

On Tue, Dec 15, 2015 at 9:05 PM, Anders Lindgren <andlind@gmail.com> wrote:
Hi,
 
Can you write a patch to that effect, for emacs-25 branch?

We have the find the cause of the problem first. But once we do that, this should be straight forward.


>     What does this return:
>
>     M-: (file-name-all-completion "åäö" "/that/empty/directory/") RET
>
> It returns nil.

So this is the heart of the problem.  I assume that if you do the same
with an ASCII first argument, the result is non-nil, yes?

Yes. 

 
Then the next step is to step with a debugger through
file_name_completion, and see why this returns nil instead of a list
of files that begin.

Auhm, I'll see what I can do. I'm a family father and have very, very, limited time, but I can see in I can find a time slot for it.

    -- Anders


Attachment: coding.diff
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]