[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Unicode Lisp reader escapes

From: Kenichi Handa
Subject: Re: [PATCH] Unicode Lisp reader escapes
Date: Tue, 23 May 2006 10:05:56 +0900
User-agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI)

In article <address@hidden>, Richard Stallman <address@hidden> writes:

>     So, disabling character translation on reading an iso-2022
>     *.el file effectively stabilize the byte-compiling of the
>     file without any actual problem.

> Ok, I am convinced that disabling character translation is a good
> solution _mechanism_.  The remaining question is what user interface
> to use.  That is, how should Emacs determine that it should set
> enable-character-translation to nil for these files?

> One obvious way is an explicit specification of the variable
> enable-character-translation.  But that would be cumbersome to use.

At least, this should work for people who don't mind the

> Another way is that specification of coding: together with mode:
> emacs-lisp could do this automatically.

I object to this because it's an incompatible change that
should be avoided at this stage.  In addition, we then have
to invent someway to "enable" normal character translation.

> Another way is that you could specify coding: in a special way,
> perhaps with ! at the end of the coding system name.

I don't know if that is aesthetically good, but at least
it's a quite handy way.

;; xxx.el -- Do XXX.   -*- coding: latin-1!; -*-

So, I'd like to implement both the 1st and 3rd method.  Ok?

Kenichi Handa

reply via email to

[Prev in Thread] Current Thread [Next in Thread]