[Openmcl-devel] Emacs: local variables list contains values that may not be safe
smishra at sfmishras.com
Thu Dec 13 02:25:37 UTC 2007
A value of nil means local variable values (those within -*- at the
start of a source file) will never be set. Is that really what you
want? You might want to check out the documentation for
enable-local-variables. Usually it makes no difference, but slime does
appear to pay attention to the value for Package.
On 12/12/07, Ron Garret <ron at awun.net> 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
> > automatically.)
> > * 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?
> > Thanks,
> > rg
> > _______________________________________________
> > Openmcl-devel mailing list
> > Openmcl-devel at clozure.com
> > http://clozure.com/mailman/listinfo/openmcl-devel
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel