[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dired doesn't decode UTF-8 file names
From: |
David Kastrup |
Subject: |
Re: Dired doesn't decode UTF-8 file names |
Date: |
Mon, 28 Aug 2006 23:36:05 +0200 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
Peter Dyballa <Peter_Dyballa@Web.DE> writes:
> Am 28.08.2006 um 22:52 schrieb Kevin Rodgers:
>
>> Peter Dyballa wrote:
>>> Am 28.08.2006 um 17:02 schrieb Kevin Rodgers:
>>>> > (("\\*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.
>>> OK. So I'll try to use
>>> (("[bt][ac]sh\\'" utf-8 . utf-8)
>>> (".*tex\\'" iso-8859-15-unix . iso-8859-15-unix))
>>
>> That should fix your *shell* buffers, and Dired buffers for wildcard
>> file names. But non-wildcard Dired buffers invoke ls directly (not
>> via a shell).
>
> I was thinking of the *shell* buffer and the *output whatsoever*
> buffer from AUCTeX, which did not always work correctly, the latter
> kept using incorrect and inappropriate ISO 8859-1 encoding.
You are confused. Multibyte buffers in Emacs are always in Emacs
encoding, never anything else. There are various encodings for I/O
however: process I/O, file I/O, X cutbuffer and so on. Those are
independent.
> The *shell* buffer does not show in mode-line any encoding – I have
> no idea whether this is good or bad, I would like to know which
> 'mood' it is in and how to interpret the buffer's contents.
Emacs buffer contents are characters in Emacs' encoding (MULE for
Emacs 22, an UTF-8 variant for Emacs 23).
> Do I really need to set encodings for each UNIX and GNU UNIX
> command? Can't GNU Emacs learn from the LC_CTYPE environment
> variable?
Emacs uses the LC_CTYPE information unless you explicitly override it.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
- Re: Dired confused by filenames starting with date-like strings, (continued)
- Re: Dired confused by filenames starting with date-like strings, Peter Dyballa, 2006/08/24
- Message not available
- Re: Dired confused by filenames starting with date-like strings, Miles Bader, 2006/08/24
- Re: Dired confused by filenames starting with date-like strings, Peter Dyballa, 2006/08/24
- Dired doesn't decode UTF-8 file names (was: Dired confused by filenames starting with date-like strings), Kevin Rodgers, 2006/08/24
- Re: Dired doesn't decode UTF-8 file names (was: Dired confused by filenames starting with date-like strings), Peter Dyballa, 2006/08/24
- Re: Dired doesn't decode UTF-8 file names, Kevin Rodgers, 2006/08/28
- Re: Dired doesn't decode UTF-8 file names, Peter Dyballa, 2006/08/28
- Re: Dired doesn't decode UTF-8 file names, Kevin Rodgers, 2006/08/28
- Re: Dired doesn't decode UTF-8 file names, Peter Dyballa, 2006/08/28
- Message not available
- Re: Dired doesn't decode UTF-8 file names,
David Kastrup <=
Message not available
- Re: Dired confused by filenames starting with date-like strings, kg6mar, 2006/08/24
- Re: Dired confused by filenames starting with date-like strings, Eli Zaretskii, 2006/08/24
- Re: Dired confused by filenames starting with date-like strings, Miles Bader, 2006/08/24
- Message not available
- Re: Dired confused by filenames starting with date-like strings, B. T. Raven, 2006/08/25
- Re: Dired confused by filenames starting with date-like strings, Eli Zaretskii, 2006/08/26
- Message not available
- Re: Dired confused by filenames starting with date-like strings, B. T. Raven, 2006/08/26
- Re: Dired confused by filenames starting with date-like strings, Miles Bader, 2006/08/26
Message not available