From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.devel Subject: Re: Problems setting byte-compile-warnings to t Date: Thu, 25 Oct 2007 19:50:59 -0400 Message-ID: <9p8x5qiwik.fsf@fencepost.gnu.org> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1193356275 32046 80.91.229.12 (25 Oct 2007 23:51:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Oct 2007 23:51:15 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 26 01:51:16 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IlCTr-0007tW-RO for ged-emacs-devel@m.gmane.org; Fri, 26 Oct 2007 01:51:16 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IlCTj-0005nZ-Eo for ged-emacs-devel@m.gmane.org; Thu, 25 Oct 2007 19:51:07 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IlCTe-0005m2-Kv for emacs-devel@gnu.org; Thu, 25 Oct 2007 19:51:02 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IlCTc-0005kt-8D for emacs-devel@gnu.org; Thu, 25 Oct 2007 19:51:01 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IlCTb-0005kq-Vn for emacs-devel@gnu.org; Thu, 25 Oct 2007 19:51:00 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IlCTb-0001Fv-M3 for emacs-devel@gnu.org; Thu, 25 Oct 2007 19:50:59 -0400 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1IlCTb-0007gT-CV; Thu, 25 Oct 2007 19:50:59 -0400 X-Spook: munitions MD2 InfoSec Medco FBI BROMURE Echelon Khaddafi X-Ran: HZlV@LA;EkV{gKm(o=`*j#A71:hjlF8o2d!qFu4M1,|J.D?MBB#.+/2bB=e*X9bGxH~DZH X-Hue: blue X-Attribution: GM In-Reply-To: (Glenn Morris's message of "Thu, 25 Oct 2007 18:42:26 -0400") User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:81729 Archived-At: 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