From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: non-ascii chars in the Lisp source files
Date: Thu, 04 Sep 2003 20:09:08 +0900 [thread overview]
Message-ID: <b9yoey07quj.fsf@jpl.org> (raw)
In-Reply-To: <87k78oyi89.fsf@jautero.no-ip.org>
>>>>> In <87k78oyi89.fsf@jautero.no-ip.org>
>>>>> Juha Autero <Juha.Autero@iki.fi> wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> Thanks. I've confirmed both the latest XEmacs 21.4 and 21.5
>> don't handle the coding cookie at the end of a file yet.
> What is the value of enable-local-variables?
t. Other local-eval related variables, enable-local-eval,
ignored-local-variables, and hack-local-variables-hook are
unchanged from the default.
> Local variables are sort of security hole so maybe XEmacs nowadays
> disable them by default.
Eh? It is defined in files.el with the default value t. Both
the latest XEmacs 21.4 and 21.5 do the same.
When I traced it using edebug, processing the `Local Variables:'
block was performed by the hack-one-local-variable function by
way of the hack-local-variables-last-page function as follows:
>>>>> In <b9y65ka9h7w.fsf@jpl.org> Katsumi Yamaoka wrote:
> (make-local-variable 'coding)
> (set 'coding 'iso-8859-1)
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2003-09-04 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 6:22 Katsumi Yamaoka
2003-09-03 7:01 ` Daniel Pittman
2003-09-03 9:06 ` Robert Epprecht
2003-09-03 7:38 ` Katsumi Yamaoka
2003-09-03 10:43 ` Reiner Steib
2003-09-03 11:20 ` Katsumi Yamaoka
2003-09-03 12:41 ` Katsumi Yamaoka
2003-09-03 15:10 ` Reiner Steib
2003-09-04 0:58 ` Katsumi Yamaoka
2003-09-04 10:13 ` Juha Autero
2003-09-04 11:09 ` Katsumi Yamaoka [this message]
2003-09-05 12:26 ` Katsumi Yamaoka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9yoey07quj.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).