From: Lennart Borgman <lennart.borgman@gmail.com>
To: Sam Steingold <sds@gnu.org>
Cc: 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 00:39:37 +0200 [thread overview]
Message-ID: <g2ve01d8a51004271539vafd456eehb0df9382c0856de3@mail.gmail.com> (raw)
In-Reply-To: <g2w1f77704b1004271509k21dcf2a9ucd68bcf5d8e9af9d@mail.gmail.com>
On Wed, Apr 28, 2010 at 12:09 AM, Sam Steingold <sds@gnu.org> wrote:
> On 4/27/10, Glenn Morris <rgm@gnu.org> wrote:
>> Sam Steingold wrote:
>>
>> > +2010-04-27 Sam Steingold <sds@gnu.org>
>> > +
>> > + * progmodes/bug-reference.el (bug-reference-url-format): Mark as
>> > + `safe-local-variable' if the value is a string or a function,
>>
>> I'm probably being thick, but I don't see how an arbitrary function
>> can be assumed to be safe
>
> You are right.
> this means that I cannot really set bug-reference-url-format in the
> "Local Variables:"
> section together with "mode: bug-reference" if I also set
> enable-local-variables to :safe.
...
> the bottom line is that there _must_ be a way to use something
> reasonably flexible here and still not be asked "local variable"
> question for each C-x v =
Maybe a safe value could be a (symbol) key to an association lists
with entries like '(my-key my-bug-reference-url-function)?
next prev parent reply other threads:[~2010-04-27 22:39 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 [this message]
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
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=g2ve01d8a51004271539vafd456eehb0df9382c0856de3@mail.gmail.com \
--to=lennart.borgman@gmail.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).