From: Markus Triska <markus.triska@gmx.at>
To: Glenn Morris <rgm@gnu.org>
Cc: 2940@debbugs.gnu.org
Subject: bug#2940: 23.0.92; C-s in dired fails to find files with umlauts
Date: Mon, 11 Jul 2011 18:21:30 +0200 [thread overview]
Message-ID: <m21uxwokj9.fsf@gmx.at> (raw)
In-Reply-To: <qfy605zibb.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sun, 10 Jul 2011 22:01:44 -0400")
Glenn Morris <rgm@gnu.org> writes:
>> (require 'ucs-normalize)
>> (setq file-name-coding-system 'utf-8-hfs)
>
> I know nothing about this area: Is this an acceptable solution (in
> which case I will close this report); or should it work out-of-the-box
> with no configuration?
In my personal use, I expected it to work out of the box. It was also
initially unclear to me that you need to explicitly require
ucs-normalize in order to use utf8-8-hfs. When you do, in "emacs -Q":
(setq file-name-coding-system 'utf-8-hfs)
you cannot do much anymore with that Emacs instance, since you get
"Invalid coding system: utf-8-hfs" on almost all key presses. This is a
general issue though that also happens when you mistype a coding system.
next prev parent reply other threads:[~2011-07-11 16:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4984.1239295440.31690.bug-gnu-emacs@gnu.org>
2009-04-10 2:08 ` bug#2940: 23.0.92; C-s in dired fails to find files with umlauts Miles Bader
2009-04-10 5:53 ` Stefan Monnier
[not found] ` <mailman.5035.1239343440.31690.bug-gnu-emacs@gnu.org>
2009-04-10 10:48 ` Markus Triska
2009-04-10 11:34 ` Kenichi Handa
2009-08-13 12:25 ` Kenichi Handa
2011-07-10 18:26 ` Glenn Morris
2011-07-10 21:11 ` Markus Triska
2011-07-11 2:01 ` Glenn Morris
2011-07-11 2:56 ` Eli Zaretskii
2011-07-11 16:21 ` Markus Triska [this message]
2009-04-09 16:28 Markus Triska
2009-04-09 17:22 ` Eli Zaretskii
2009-04-09 17:33 ` Markus Triska
2011-07-11 22:02 ` Alp Aker
2011-07-15 20:38 ` Glenn Morris
2011-07-16 17:38 ` Alp Aker
2019-11-02 6:12 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m21uxwokj9.fsf@gmx.at \
--to=markus.triska@gmx.at \
--cc=2940@debbugs.gnu.org \
--cc=rgm@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).