all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: jidanni@jidanni.org
To: emacs-devel@gnu.org
Subject: mention risky local variables "!" choice
Date: Fri, 31 Aug 2007 01:17:55 +0800	[thread overview]
Message-ID: <87odgphrgc.fsf@jidanni.org> (raw)

Info says:
   Otherwise, you can tell Emacs to record all the variable/value pairs in
   this file as safe, by typing `!' at the confirmation prompt.  When
   Emacs encounters these variable/value pairs subsequently, in the same
   file or others, it will assume they are safe.

OK, then the message

   The local variables list in .procmailrc
   contains variables that are risky (**).

   Do you want to apply it?  You can type
   y  -- to apply the local variables list.
   n  -- to ignore the local variables list.

    ** compile-command : (concat "proclint " buffer-file-name)

should mention "!", else one is sure there is no way to stop day in
and day out interrogation.

But wait. Info also says:
       Some variables, such as `load-path', are considered particularly
    "risky": there is seldom any reason to specify them as local variables,
    and changing them can be dangerous.  Even if you enter `!' at the
    confirmation prompt, Emacs will not record any values as safe for these
    variables.  If you really want to record safe values for these
    variables...

So maybe the message should instead just have a "link" to the Info page for
more details.

Also say if "**" means "particularly risky" vs. "*" if any.

Anyway, no fair not telling them about the existence of "!".

By the way, here is a patch about something else, different than the
above problem. I hope I got the link syntax correct.

*** /tmp/emacs-5	2007-07-07 11:55:03.000000000 +0800
--- /tmp/emacs-5.jidanni	2007-08-31 01:09:15.714237156 +0800
***************
*** 4458,4463 ****
--- 4458,4469 ----
       #   -Dmumble=blaah"
       # End:
  
+ You can even mix elisp expressions in:
+ 
+      # compile-command: (concat "proclint " buffer-file-name)
+ 
+ (which will trigger alarms. See *Note Safety of File Variables::.)
+ 
     Some "variable names" have special meanings in a local variables
  list.  Specifying the "variable" `mode' really sets the major mode,
  while any value specified for the "variable" `eval' is simply evaluated

             reply	other threads:[~2007-08-30 17:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 17:17 jidanni [this message]
2007-08-31  7:35 ` mention risky local variables "!" choice Richard Stallman
2007-08-31  8:21   ` Glenn Morris
2007-08-31 22:57     ` jidanni
2007-08-31 23:47       ` Glenn Morris
2007-09-04 22:35         ` Davis Herring
2007-09-01  4:06     ` 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=87odgphrgc.fsf@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=emacs-devel@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 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.