From: Chong Yidong <cyd@stupidchicken.com>
Subject: Re: Instead of `risky-local-variable'
Date: Tue, 31 Jan 2006 21:46:52 -0500 [thread overview]
Message-ID: <87d5i7x0bn.fsf@stupidchicken.com> (raw)
In-Reply-To: <200602010027.k110RHJ14939@raven.dms.auburn.edu> (Luc Teirlinck's message of "Tue, 31 Jan 2006 18:27:17 -0600 (CST)")
> I'm considering a more reliable replacement for the
> `risky-local-variable' mechanism. My idea is that only defcustom'ed
> variables could be specified in a local variables list, and that the
> :type together with the specified value would determine whether a
> variable is safe.
This won't work for defcustoms that haven't been loaded yet.
next prev parent reply other threads:[~2006-02-01 2:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 16:47 Instead of `risky-local-variable' Richard M. Stallman
2006-02-01 0:27 ` Luc Teirlinck
2006-02-01 2:46 ` Chong Yidong [this message]
2006-02-02 4:14 ` Richard M. Stallman
2006-02-02 4:47 ` Chong Yidong
2006-02-01 11:03 ` Kim F. Storm
2006-02-02 4:16 ` Richard M. Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d5i7x0bn.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).