From: "Davis Herring" <herring@lanl.gov>
To: "Chong Yidong" <cyd@stupidchicken.com>
Cc: Sam Steingold <sds@gnu.org>, emacs-devel@gnu.org
Subject: Re: /srv/bzr/emacs/trunk r100059: (bug-reference-url-format): Mark as `safe-local-variable' if the value
Date: Wed, 28 Apr 2010 09:25:50 -0700 (PDT) [thread overview]
Message-ID: <49873.130.55.132.217.1272471950.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <87aasn60du.fsf@stupidchicken.com>
> A `safe-local-variable' property must be a function of one argument
> (or nil).
Ah, sorry; I don't know why I thought t was allowed. But the code I was
commenting on would fail with nil too, as I said, so the point remains.
While reading further I also see that we already have
`safe-local-variable-values' for the case where particular values need to
be marked as safe, which certainly satisfies the stated desire to allow
one additional value for a variable without the `lambda' trickery.
Perhaps the `safe-file-function' property would nonetheless be useful to
avoid having to add many different things to s-l-v-v.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2010-04-28 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1O6mXN-0006ds-3k@internal.in.savannah.gnu.org>
2010-04-27 21:32 ` /srv/bzr/emacs/trunk r100059: (bug-reference-url-format): Mark as `safe-local-variable' if the value Glenn Morris
2010-04-27 21:46 ` Chong Yidong
2010-04-27 22:09 ` Sam Steingold
2010-04-27 22:39 ` Lennart Borgman
2010-04-27 22:42 ` Chong Yidong
2010-04-27 23:10 ` Sam Steingold
2010-04-28 15:32 ` Davis Herring
2010-04-28 15:51 ` Chong Yidong
2010-04-28 16:25 ` Davis Herring [this message]
2010-04-28 17:21 ` Chong Yidong
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=49873.130.55.132.217.1272471950.squirrel@webmail.lanl.gov \
--to=herring@lanl.gov \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=sds@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).