Re: no-byte-compile no longer considered safe?
Richard Stallman [EMAIL PROTECTED] writes: I guess a simper way to do it is to provide a var that says set all the safe vars and ignore the others. I hope I never simper, but I implemented your suggestion. Thanks, it appears to have fixed the problem. The files that shouldn't be byte-compiled are no longer byte-compiled. -- Bill Wohler [EMAIL PROTECTED] http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian! If you're passed on the right, you're in the wrong lane. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: no-byte-compile no longer considered safe?
Should no-byte-compile be marked as a safe variable, It already is, since a month ago. But the problem could still be related to that. Does Emacs currently ask any questions when you visit any of these files? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: no-byte-compile no longer considered safe?
Richard Stallman [EMAIL PROTECTED] writes: Should no-byte-compile be marked as a safe variable, It already is, since a month ago. But the problem could still be related to that. Does Emacs currently ask any questions when you visit any of these files? Ah, now I see what happened and I found the bug. I was actually being asked for another variable in the same Local Variables stanza. If you add the following to a file, make recompile will compile it: ;; Local Variables: ;; no-byte-compile: t ;; url-unreserved-chars: nil ;; End -- Bill Wohler [EMAIL PROTECTED] http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian! If you're passed on the right, you're in the wrong lane. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: no-byte-compile no longer considered safe?
Ah, now I see what happened and I found the bug. I was actually being asked for another variable in the same Local Variables stanza. If you add the following to a file, make recompile will compile it: ;; Local Variables: ;; no-byte-compile: t ;; url-unreserved-chars: nil ;; End I think the byte compiler needs a way to ignore all local variables except those specific few it is interested in--and thus avoid ever asking for confirmation. Does anyone see a way in which that will fail to do the job? I think other commands will want more or less the same facility (but with a different list of significant variables). So the implementation should be at least a little bit general. Perhaps involving a variable that specifies the list of variables to pay attention to. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
no-byte-compile no longer considered safe?
An MH-E user has reported that a few of the MH-E files which MUST NOT be compiled were compiled after a recent CVS Emacs update. I've noticed this behavior too after I updated. Unfortunately, the compilation of these files causes mysterious bugs in MH-E (which is why we set no-byte-compile to t in the local variables stanza). When I fired up Emacs recently, I noticed that I was prompted for several of my local variables. I imagine that the safe variable code that has been discussed here was implemented. Related? Should no-byte-compile be marked as a safe variable, or is there something the MH-E package should be doing differently now? -- Bill Wohler [EMAIL PROTECTED] http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian! If you're passed on the right, you're in the wrong lane. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
