GNU bug report logs -
#2940
[macOS] C-s in dired fails to find umlauts in filenames (due to wrong file-name-coding-system)
Previous Next
Full log
Message #15 received at 2940 <at> emacsbugs.donarmstrong.com (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
> What's your value of file-name-coding-system?
It is nil, and default-file-name-coding-system is 'utf-8.
> Does it help to say
>
> C-x RET c utf-8 RET C-x d
>
> instead of just "C-x d"?
No, unfortunately not. Also for C-s it does not seem to make a
difference. When I enter an "ö" in *scratch*, C-u C-x = on it says:
character: ö (246, #o366, #xf6)
preferred charset: unicode (Unicode (ISO10646))
code point: 0xF6
syntax: w which means: word
category: .:Base, j:Japanese, l:Latin
to input: type "oe" with german-postfix
buffer code: #xC3 #xB6
file code: #xC3 #xB6 (encoded by coding system utf-8-unix)
display: by this font (glyph code)
xft:-bitstream-Bitstream Vera Sans Mono-normal-normal-normal-*-20-*-*-*-m-0-iso10646-1 (#x7C)
Character code properties: customize what to show
name: LATIN SMALL LETTER O WITH DIAERESIS
old-name: LATIN SMALL LETTER O DIAERESIS
general-category: Ll (Letter, Lowercase)
decomposition: (111 776) ('o' '̈')
There are text properties here:
fontified t
This "ö" is thus also rendered with the expected font, in contrast to
the one in dired.
This bug report was last modified 4 years and 306 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.