🚀 go-pugleaf

In article <9006211721.AA04340@noname>, eric%yamada-sun writes:
|		   What might be nice as a safeguard is a variable,
| called something like `visit-file-paranoid', which if not nil, would
| refuse to eval anything in the local variables section without
| confirmation from the user.  So if I had this variable set, and
| visited a file as described above, I'd see a little buffer created
| with the Lisp code in it, and a message in the minibuffer saying `Okay
| to execute this code??'

You can start by
	(setq inhibit-local-variables t)
in your .emacs.  But, yes, I've wanted more of a "check this puppy
out" intermediate solution, as you suggest.

Maybe a hook in "hack-local-variables", that if present, *had* to
return a "t" for the variables to be evalled.  That way, I could say
"anything below $HOME is safe", or whatever.

Just another Emacs hacker,
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Welcome to Portland, Oregon, home of the California Raisins!"=/