From: "Eric Twietmeyer" <zimbus26@yahoo.com>
Subject: enable-local-variables
Date: 1 Jan 2007 12:04:08 -0800 [thread overview]
Message-ID: <1167681848.399172.255500@h40g2000cwb.googlegroups.com> (raw)
Hi,
I just upgraded to emacs 22.0.92.1. I write C++ code and there is a
local variable "typedefs" that is used for syntax highlighting. Now
that I have upgraded I find that every buffer I open that has this
local variable "typedefs" in it I am presented with a dialog asking
that I confirm that the local variable is "safe".
I have read through the docs that I can find on this, and I realized
that I can set the "enable-local-variables" value to ":all", and now it
won't ask me any more about these typedefs. The docs say "don't do
this" (i.e. use the ":all" value) because it is globally unsafe.
However, there doesn't appear to be any way to specify that the local
variable "typedefs" should always be accepted as safe, regardless of
its values. Each C++ file I visit will have a different value of
"typedefs", so I can't in any reasonable way create a var, val cons
list of safe values. It would be thousands of entries long.
So is there another way to work around this? I never have any other
local variables defined in my files, I use emacs purely for writing
code. I guess I'm just wondering what the expected usage would be in
this case.
Thanks,
-Eric Twietmeyer
next reply other threads:[~2007-01-01 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-01 20:04 Eric Twietmeyer [this message]
2007-01-01 20:43 ` enable-local-variables Leo
2007-01-01 21:45 ` enable-local-variables Ralf Angeli
2007-01-01 22:27 ` enable-local-variables Eric Twietmeyer
2007-01-01 22:50 ` enable-local-variables Ralf Angeli
2007-01-02 0:21 ` enable-local-variables Eric Twietmeyer
2007-01-02 2:21 ` enable-local-variables Eric Twietmeyer
2007-01-02 6:56 ` enable-local-variables Ralf Angeli
2007-01-02 14:55 ` enable-local-variables Eric Twietmeyer
[not found] ` <mailman.2620.1167684196.2155.help-gnu-emacs@gnu.org>
2007-01-01 22:21 ` enable-local-variables Eric Twietmeyer
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=1167681848.399172.255500@h40g2000cwb.googlegroups.com \
--to=zimbus26@yahoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).