From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: The `risky-local-variable' blacklist
Date: Wed, 01 Sep 2004 15:24:31 -0400 [thread overview]
Message-ID: <E1C2aid-0003sr-Ey@fencepost.gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0408311622260.31548-100000@x-mail.lanl.gov> (message from Davis Herring on Tue, 31 Aug 2004 17:07:02 -0600 (MDT))
In summary, in my Emacs (21.3.1) "emacs -q --no-site-file" yields only 498
non-risky user variables (as tested by `user-variable-p', `boundp', and
`risky-local-variable-p'),
Does this 498 include only variables that are preloaded or autoloaded?
I would guess so. The actual number of user-option variables defined
in Lisp files must be much larger.
To pick the first example I could find, does that 498 include
makefile-macro-assign? That variable is safe.
> Here's an idea that might do the job and be acceptable. Each time
> Emacs sees a variable/value combination that is new for the current
> user, it asks the user to confirm that combination. Any given
> combination only needs to be confirmed once by any given user. This
> could reduce the repetitive nuisance down to the point where people
> will (1) accept the burden and (2) not zone out when they see the
> questions.
>
> What do you think?
That sounds like it would work, but it also sounds like a lot of overhead
(and more user-data to keep up with in one dot-file or another); since
users could of course put `safe-local-variable' declarations into their
.emacs, it might not be necessary. Combined with the arbitrary filter
feature (where the `safe-local-variable' property stores a check-function
through which to run the file's value for the variable) and a simple
interface (like that provided for disabled commands), my original
suggestion would be almost entirely equivalent.
As regards the work we would have to do, they are not even similar.
One involves studying every variable. The other does not.
next prev parent reply other threads:[~2004-09-01 19:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 2:13 The `risky-local-variable' blacklist Davis Herring
2004-08-31 14:01 ` Stefan
2004-08-31 21:42 ` Davis Herring
2004-08-31 22:43 ` Stefan
2004-08-31 23:18 ` Davis Herring
2004-08-31 22:07 ` Richard Stallman
2004-08-31 23:07 ` Davis Herring
2004-09-01 19:24 ` Richard Stallman [this message]
2004-09-01 7:11 ` Kim F. Storm
2004-09-01 14:36 ` Stefan Monnier
2004-09-02 4:53 ` Richard 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=E1C2aid-0003sr-Ey@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.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.
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).