[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: unibyte buffers won't display latin-1 characters
From: |
David Kuehling |
Subject: |
Re: unibyte buffers won't display latin-1 characters |
Date: |
29 Aug 2002 19:47:39 +0200 |
>>>>> "Karl" == Karl Berry <karl@freefriends.org> writes:
> Unfortunately I do not. Since compressed (or encrypted files) are
> arbitrary binary data, I don't know any way to read them except with
> 'no-conversion, which I assume is what stops the translation into a
> multibyte buffer.
`auto-compression-mode' seems to know a way around that. It loads the
compressed file with coding `no-conversion' (default value of
`auto-coding-alist' makes it do that), and decodes the uncompressed data
into multibyte representation, determining the coding system by calling
`auto-coding-alist-lookup' on the filename with the extension .gz etc
stripped.
Well, that's what I think after a short look at `jka-compr.el', I'm far
from understanding what actually goes on there...
> Anyway, at this point, I suggest that crypt++ not be loaded by default
> and probably not be used at all. The builtin (un)compression and
> line-ending support in emacs should suffice.
Someone would have to implement a way to let `auto-compression-mode'
query for passwords when required.
David
--
GnuPG public key: http://user.cs.tu-berlin.de/~dvdkhlng/dk.gpg
Fingerprint: B17A DC95 D293 657B 4205 D016 7DEF 5323 C174 7D40