Peter Daum <[EMAIL PROTECTED]> writes:
>> Not really related to the problem, but why do you use unibyte mode?
>> It is very much deprecated, you will not be able to edit or view utf-8
>> encoded text.
>
> Fortunately, I don't usually need UTF-8 (Even in multibyte mode and with
> a suitable font, I
Sven Joachim <[EMAIL PROTECTED]> writes:
> One important reason to prefer emacs-snapshot over emacs22 is that the
> latter was not part of Debian before the Etch release and the various
> add-on Elisp packages in Etch do not support it well. Contrastingly,
> the emacs-snapshot had been in Debian
Peter Daum writes:
> Fortunately, I don't usually need UTF-8 (Even in multibyte mode and with
> a suitable font, I never managed persuading emacs to correctly display
> an utf-8-encoded file)
Unless you live on an island, sooner or later you will retrieve UTF-8
encoded files, as this is standard i
Sven Joachim wrote:
> Not really related to the problem, but why do you use unibyte mode?
> It is very much deprecated, you will not be able to edit or view utf-8
> encoded text.
Fortunately, I don't usually need UTF-8 (Even in multibyte mode and with
a suitable font, I never managed persuading
Peter Daum writes:
> Now after migrating my systems from Suse to Debian (Etch), my key
> bindings don't work anymore and I can't figure out, what changed.
>
> Here a minimal code snippet to illustrate the problem:
>
> (defun latin1-to-emacs-char (char-code)
> (make-char 'latin-iso8859-1 (- char
5 matches
Mail list logo
