all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: amscott1@sedona.ch.intel.com, cyd@stupidchicken.com,
	storm@cua.dk, emacs-devel@gnu.org
Subject: Re: Clarification on using safe-local-variable-values
Date: Sat, 11 Mar 2006 10:46:27 -0500	[thread overview]
Message-ID: <E1FI6IV-0001k8-S7@fencepost.gnu.org> (raw)
In-Reply-To: <200603102357.k2ANvtW07688@raven.dms.auburn.edu> (message from Luc Teirlinck on Fri, 10 Mar 2006 17:57:55 -0600 (CST))

    I believe that Richard decided that _every_ variable should be
    considered risky, except when explicitly marked safe.

I decided that every variable should be considered _somewhat_ risky,
if not explicitly marked safe.  This does not _necessarily_ mean
there is no such thing as degrees of risk, so it does not _necessarily_ mean
we should eliminate the concept of marking a variable as risky.

I am not sure that the current way of handling variables marked
risky is really best.  But it might be useful.  So let's leave it
alone, for now.  There is no need to change it.

  reply	other threads:[~2006-03-11 15:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 19:55 Clarification on using safe-local-variable-values Andrew M. Scott
2006-03-08 20:24 ` Chong Yidong
2006-03-08 20:43   ` Andrew M. Scott
2006-03-08 21:52     ` Chong Yidong
2006-03-08 23:50       ` Andrew M. Scott
2006-03-09  0:03         ` Chong Yidong
2006-03-09  8:39           ` Kim F. Storm
2006-03-09 14:50             ` Chong Yidong
2006-03-10 23:57               ` Luc Teirlinck
2006-03-11 15:46                 ` Richard Stallman [this message]
2006-03-11 23:47               ` Kim F. Storm
2006-03-09 17:14   ` Richard Stallman
2006-03-09 17:14 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1FI6IV-0001k8-S7@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=amscott1@sedona.ch.intel.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.