From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: jidanni@jidanni.org Newsgroups: gmane.emacs.devel Subject: mention risky local variables "!" choice Date: Fri, 31 Aug 2007 01:17:55 +0800 Message-ID: <87odgphrgc.fsf@jidanni.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1188495865 19390 80.91.229.12 (30 Aug 2007 17:44:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 30 Aug 2007 17:44:25 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 30 19:44:23 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IQo42-000112-1H for ged-emacs-devel@m.gmane.org; Thu, 30 Aug 2007 19:44:18 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IQo41-0005Yz-Ot for ged-emacs-devel@m.gmane.org; Thu, 30 Aug 2007 13:44:17 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IQo3z-0005YW-0X for emacs-devel@gnu.org; Thu, 30 Aug 2007 13:44:15 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IQo3x-0005YK-GQ for emacs-devel@gnu.org; Thu, 30 Aug 2007 13:44:13 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IQo3x-0005YH-B2 for emacs-devel@gnu.org; Thu, 30 Aug 2007 13:44:13 -0400 Original-Received: from lax-green-bigip-5.dreamhost.com ([208.113.200.5] helo=looneymail-a2.g.dreamhost.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IQo3x-0000rS-19 for emacs-devel@gnu.org; Thu, 30 Aug 2007 13:44:13 -0400 Original-Received: from jidanni2 (122-127-35-99.dynamic.hinet.net [122.127.35.99]) by looneymail-a2.g.dreamhost.com (Postfix) with ESMTP id CEA9D16D468 for ; Thu, 30 Aug 2007 10:43:44 -0700 (PDT) X-Detected-Kernel: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:77425 Archived-At: 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