From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Dired doesn't decode UTF-8 file names (was: Dired confused by filenames starting with date-like strings)
Date: Thu, 24 Aug 2006 10:12:00 -0600 [thread overview]
Message-ID: <eckj5i$te2$1@sea.gmane.org> (raw)
In-Reply-To: <55FE760B-5409-4876-9E4D-0B15A0F5AEAF@Web.DE>
Peter Dyballa wrote:
>
> Am 24.08.2006 um 16:27 schrieb Kevin Rodgers:
>
>> There is no reason to set dired-use-ls-dired to anything but t or nil.
>> In particular, it does not determine which ls program is run. Try:
>>
>> (setq insert-directory-program "/sw/bin/ls"
>> dired-use-ls-dired t)
>
> Am 24.08.2006 um 16:35 schrieb Miles Bader:
>
>> So I guess the following should work:
>>
>> (setq dired-use-ls-dired t)
>> (setq insert-directory-program "/sw/bin/gls")
>
>
> Oh, yes, these work! Thank you! There isn't much difference compared to
> using Apple's ls; in GNU Emacs 22.0.50 UTF-8 characters are still
> displayed as a series of UTF-8 octets, and in GNU Emacs 23.0.0 I still
> cannot search for file names with German umlauts etc.
That is the first mention of UTF-8 in this thread. Mile suggested using
GNU ls --dired to solve the OP's problem with date-like filenames.
Is file-name-coding-system (or default-file-name-coding-system) set
to utf-8? Should it be?
Is there an entry in process-coding-system-alist for ls? Should there
be?
--
Kevin
next prev parent reply other threads:[~2006-08-24 16:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 18:15 Dired confused by filenames starting with date-like strings kg6mar
2006-08-23 22:17 ` Miles Bader
2006-08-24 11:56 ` Peter Dyballa
2006-08-24 14:27 ` Kevin Rodgers
[not found] ` <mailman.5544.1156420601.9609.help-gnu-emacs@gnu.org>
2006-08-24 14:35 ` Miles Bader
2006-08-24 15:05 ` Peter Dyballa
2006-08-24 16:12 ` Kevin Rodgers [this message]
2006-08-24 19:48 ` Dired doesn't decode UTF-8 file names (was: Dired confused by filenames starting with date-like strings) Peter Dyballa
2006-08-28 15:02 ` Dired doesn't decode UTF-8 file names Kevin Rodgers
2006-08-28 15:44 ` Peter Dyballa
2006-08-28 20:52 ` Kevin Rodgers
2006-08-28 21:29 ` Peter Dyballa
[not found] ` <mailman.5855.1156800592.9609.help-gnu-emacs@gnu.org>
2006-08-28 21:36 ` David Kastrup
[not found] ` <mailman.5520.1156371436.9609.help-gnu-emacs@gnu.org>
2006-08-24 17:43 ` Dired confused by filenames starting with date-like strings kg6mar
2006-08-24 23:35 ` Eli Zaretskii
2006-08-25 0:41 ` Miles Bader
[not found] ` <mailman.5588.1156462534.9609.help-gnu-emacs@gnu.org>
2006-08-25 23:28 ` B. T. Raven
2006-08-26 12:09 ` Eli Zaretskii
[not found] ` <mailman.5676.1156594178.9609.help-gnu-emacs@gnu.org>
2006-08-27 0:58 ` B. T. Raven
2006-08-27 1:41 ` Miles Bader
[not found] ` <mailman.5698.1156642923.9609.help-gnu-emacs@gnu.org>
2006-09-07 3:08 ` kg6mar
2006-09-07 13:44 ` Miles Bader
2006-11-02 17:59 ` John Olson
2006-08-24 21:48 ` Jesse Alama
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='eckj5i$te2$1@sea.gmane.org' \
--to=ihs_4664@yahoo.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.