emacs-pretest-bug
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: add info about safe-local-variable to describe-variable


From: Reiner Steib
Subject: Re: add info about safe-local-variable to describe-variable
Date: Tue, 09 May 2006 10:16:01 +0200
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.50 (gnu/linux)

On Tue, May 09 2006, Richard Stallman wrote:

>       > | This variable is safe to use as a file local variable only if its 
> value
>       > | satisfies the predicate `#[(x) [BYTE-CODE stripped] [x (t nil 
> shared dwim)] 2]'.
>
> Why is the predicate a bytecode, instead of a symbol whose
> function definition is a bytecode?

The predicate is a lambda expression which was bytecomplied [I'm not
sure if this is what you asked for].  I gave a recipe to reproduce in
my first mail.  FWIW, if I quote[1] the lambda expression in my
recipe, I get the expected result:

,----[ <f1> v rs-foo RET ]
| This variable is safe to use as a file local variable only if its value
| satisfies the predicate `(lambda (x) (or (stringp x) (member x (quote (t nil 
shared dwim)))))'.
`----

On Mon, May 08 2006, Dan Nicolaescu wrote:

> I am not sure what to do in this situation. Should we print the
> bytecode? A disassembly of the bytecode (not very useful)? 
> Or nothing?
>
> Opinions?

Printing the bytecode looks like a bug from the user's POV; and it
isn't useful.

Bye, Reiner.

[1]
(defvar rs-foo nil)
(put 'rs-foo 'safe-local-variable
     ;; Quoted lambda expression:
     '(lambda (x)
        (or (stringp x)
            (member x (quote (t nil shared dwim))))))
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]