[Python-Dev] PEP 263 -- Python Source Code Encoding
Tue, 26 Feb 2002 20:50:35 +0100
"Martin v. Loewis" wrote:
> firstname.lastname@example.org (Barry A. Warsaw) writes:
> > I don't think it works for XEmacs. I've got a MULE-aware XEmacs
> > 21.4.6 and while it asks if I want to set the local variables in the
> > -*- line, I still see "Raw" in the modeline, and I see the following
> > letters in print string (with funny little lines above the
> > characters): iAOOEI. See attached capture. That doesn't seem right,
> > does it?
> Indeed not: It interprets it as latin-1. I hope XEmacs will eventually
> follow the GNU Emacs conventions here, since I think they are useful.
After reading some of the Emacs docs, I think we should allow
a more flexible coding line:
-*- ... coding: (\w+) ... -*-
because you will sometimes want to add more variables to that
Emacs init line than just the encoding declaration.
Does anybody know where XEmacs is moving w/r to this ? (and
for that matter what about vi, vim, etc. ?)
CEO eGenix.com Software GmbH
Company & Consulting: http://www.egenix.com/
Python Software: http://www.egenix.com/files/python/