From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: Dired doesn't decode UTF-8 file names
Date: Mon, 28 Aug 2006 09:02:58 -0600 [thread overview]
Message-ID: <ecv0k7$9nn$1@sea.gmane.org> (raw)
In-Reply-To: <10737F7A-CC2F-4281-B611-CB3BBE791A07@Web.DE>
Peter Dyballa wrote:
>
> Am 24.08.2006 um 18:12 schrieb Kevin Rodgers:
>> Is there an entry in process-coding-system-alist for ls? Should there
>> be?
>
> Not directly ...
>
> (("\\*shell\\*\\'" utf-8 . utf-8)
> ("\\*.* output\\*\\'" iso-8859-15-unix . iso-8859-15-unix))
>
> The second line is meant for AUCTeX output buffers (although not really
> working, probably I have to find some hook). Is there really more needed?
That doesn't look right at all. According to its doc string, the car of
the alist elements should be a regexp that matches a program name,
whereas your patterns look like they match buffer names.
--
Kevin
next prev parent reply other threads:[~2006-08-28 15:02 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 ` Dired doesn't decode UTF-8 file names (was: Dired confused by filenames starting with date-like strings) Kevin Rodgers
2006-08-24 19:48 ` Peter Dyballa
2006-08-28 15:02 ` Kevin Rodgers [this message]
2006-08-28 15:44 ` Dired doesn't decode UTF-8 file names 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
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='ecv0k7$9nn$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.
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).