unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: The `risky-local-variable' blacklist
Date: Thu, 02 Sep 2004 00:53:20 -0400	[thread overview]
Message-ID: <E1C2jb6-0002EV-L0@fencepost.gnu.org> (raw)
In-Reply-To: <m3u0ui8nvp.fsf@kfs-l.imdomain.dk> (storm@cua.dk)

    Quoting from NEWS, we already added the foundation for this:

    ** The variable `safe-local-eval-forms' specifies a list of forms that
    are ok to evaluate when they appear in an `eval' local variables
    specification.  Normally Emacs asks for confirmation before evaluating
    such a form, but if the form appears in this list, no confirmation is
    needed.

I think I wouldn't use the same variable, simply because setting a
variable isn't an "eval form".  Yes, we could look for (setq VAR VAL)
in that list, but it seems unclean as a user interface.

    IIRC, we discussed back then whether to give the user a choice to
    automatically add an eval form to that list when prompted to confirm.
    But it was rejected/postponed due to lack of interest.

Eval forms are used only rarely; for them, such a feature isn't
needed.  But if we make every file variable setting check such a list,
that is much more common, so I believe such an interface is needed.

    BTW, shouldn't safe-local-eval-forms be marked risky ???

Not necessary, its name automatically implies "risky".

      parent reply	other threads:[~2004-09-02  4:53 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
2004-09-01  7:11   ` Kim F. Storm
2004-09-01 14:36     ` Stefan Monnier
2004-09-02  4:53     ` Richard Stallman [this message]

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=E1C2jb6-0002EV-L0@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).