Re: Strange behaviour with dired and UTF8

[Kai Großjohann]

"Jan D." <address@hidden> writes:

> But when trying to operate on a file, say opening it, I get
> "File no longer exists; type `g' to update Dired buffer"
> It seems that dired does not keep the original file name around, but
> tries to open with the display name representation of the file name.

Yeah, it seems that's how dired operates: it inserts the output from
"ls -l" into the buffer and then does operations on that buffer to
find the file name and suchlike.

Hm.  And the "ls -l" output contains not only the file names, it also
contains the dates.

I was going to suggest to have dired-find-file bind
file-name-coding-system to the value used for reading the "ls -l"
output, but that will break when the date and the file names use
different encodings.

-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)