Re: Problems setting byte-compile-warnings to t

[Glenn Morris <rgm@gnu.org>]

Glenn Morris wrote:

> Perhaps one of the `(memq foo byte-compile-warnings)' in bytecomp.el
> is being run outside byte-compile-close-variables?

Looking at it some more, the value of byte-compile-warnings set by
byte-compile-close-variables gets clobbered when
byte-compile-insert-header is called. It changes the buffer to
" *Compiler Input", where the buffer local value shadows the value in
the let-binding.

A possible fix might be to alter the value in the " *Compiler Input" buffer:

***************
*** 1682,1687 ****
--- 1687,1697 ----
    ;; Arg of t means don't alter enable-local-variables.
          (normal-mode t)
          (setq filename buffer-file-name))
+       ;; Respect any file local variables.
+       (set (make-local-variable 'byte-compile-warnings)
+            (if (eq byte-compile-warnings t)
+                byte-compile-warning-types
+              byte-compile-warnings))
        ;; Set the default directory, in case an eval-when-compile uses it.
        (setq default-directory (file-name-directory filename)))
      ;; Check if the file's local variables explicitly specify not to