From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: RFC: add .dir-locals.el
Date: Thu, 12 Apr 2012 20:15:00 -0000 [thread overview]
Message-ID: <87k41kzp1k.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83bomw4vob.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Apr 2012 22:06:12 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Thu, 12 Apr 2012 07:32:56 +0800
>> From: Yao Qi <yao@codesourcery.com>
>> CC: <gdb-patches@sourceware.org>
>>
>> With this change, when emacs opens gdb files for the first time, it
>> prompts to ask apply risky local variables. Not sure GDB contributors
>> using emacs are comfortable with this or not.
Eli> Can't you make them not risky conditioned on specific types of values,
Eli> like strings etc.?
I don't see how that applies here.
You can set a property on a symbol to make it safe in some situations.
This would normally be done via a patch to Emacs, but one can also do it
temporarily in .emacs or whatever.
In this case though, what symbol would you use?
AFAIK you have to call font-lock-add-keywords to change font-locking.
There is no local variable you can set.
Tom
next prev parent reply other threads:[~2012-04-12 20:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 18:52 Tom Tromey
2012-03-26 19:06 ` Joel Brobecker
2012-03-26 19:33 ` Tom Tromey
2012-03-28 17:35 ` Tom Tromey
2012-04-11 23:59 ` Yao Qi
2012-04-12 0:44 ` Joel Brobecker
2012-04-12 16:01 ` Tom Tromey
2012-04-12 16:25 ` Tom Tromey
2012-04-12 19:21 ` Eli Zaretskii
2012-04-12 20:15 ` Tom Tromey [this message]
2012-04-13 9:08 ` Eli Zaretskii
2012-04-13 14:05 ` Tom Tromey
2012-04-13 15:22 ` Eli Zaretskii
2012-04-13 15:37 ` Eli Zaretskii
2012-04-13 9:45 ` Yao Qi
2012-04-13 12:48 ` Eli Zaretskii
2012-04-13 13:51 ` Yao Qi
2012-04-13 14:45 ` Pedro Alves
2012-04-13 14:58 ` Tom Tromey
2012-04-13 15:20 ` Eli Zaretskii
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=87k41kzp1k.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox