[Openmcl-devel] Emacs: local variables list contains values that may not be safe
gb at clozure.com
Wed Dec 12 21:40:26 EST 2007
A lot of OpenMCL source files try to specify the file's/buffer's package
(for the benefit of Emacs ...) via an attribute line:
;;;-*-Mode: LISP; Package: CCL -*-
In parsing this, some versions of Emacs apparently don't know that
setting a buffer-local Package variable is harmless. (Setting some
other buffer-local variables - especially those related to Emacs
search paths - might enable security exploits and apparently has
in the past.)
On Wed, 12 Dec 2007, Ron Garret wrote:
> Turns out the magic incantation is:
> (setq enable-local-variables nil)
> Still a mystery why this started all of a sudden.
> On Dec 12, 2007, at 6:05 PM, Ron Garret wrote:
>> From the if-it's-not-one-thing-it's-another department...
>> Just now (at least it seems like it started just now -- I don't
>> remember ever encountering this before, and I've been using emacs for
>> a long, long time) whenever I try to edit a Lisp file in emacs I get a
>> message like this:
>> The local variables list in l1-application.lisp
>> contains values that may not be safe (*).
>> Do you want to apply it? You can type
>> y -- to apply the local variables list.
>> n -- to ignore the local variables list.
>> ! -- to apply the local variables list, and permanently mark these
>> values (*) as safe (in the future, they will be set
>> * Package : CCL
>> This persists even if I get rid of my .emacs file, so it's not a
>> result of any of my customizations (which were pretty minimal anyway).
>> Does anyone know how to get emacs to stop doing this?
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel