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
