From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.help Subject: Re: byte-compile making erroneous *Compile Log* Date: Tue, 02 Jun 2009 08:23:36 +0200 Message-ID: <4A24C568.6090609@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1243923853 18202 80.91.229.12 (2 Jun 2009 06:24:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 2 Jun 2009 06:24:13 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: DJV5@Austin.RR.com Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jun 02 08:24:09 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MBNPs-0007Iv-Lw for geh-help-gnu-emacs@m.gmane.org; Tue, 02 Jun 2009 08:24:08 +0200 Original-Received: from localhost ([127.0.0.1]:50859 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MBNPs-0007eV-2b for geh-help-gnu-emacs@m.gmane.org; Tue, 02 Jun 2009 02:24:08 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MBNPX-0007eI-3q for help-gnu-emacs@gnu.org; Tue, 02 Jun 2009 02:23:47 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MBNPS-0007dq-DJ for help-gnu-emacs@gnu.org; Tue, 02 Jun 2009 02:23:46 -0400 Original-Received: from [199.232.76.173] (port=41343 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MBNPS-0007dn-7M for help-gnu-emacs@gnu.org; Tue, 02 Jun 2009 02:23:42 -0400 Original-Received: from mail.gmx.net ([213.165.64.20]:38879) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MBNPR-0005kw-Ja for help-gnu-emacs@gnu.org; Tue, 02 Jun 2009 02:23:42 -0400 Original-Received: (qmail invoked by alias); 02 Jun 2009 06:23:38 -0000 Original-Received: from 62-47-63-63.adsl.highway.telekom.at (EHLO [62.47.63.63]) [62.47.63.63] by mail.gmx.net (mp034) with SMTP; 02 Jun 2009 08:23:38 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX1+/GKN80ZO/eMZ9UbRa6PU0Xs+vrMA5sL24gFd1dq uFrHsSiBAXzD5/ User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) Original-References: loom.20090602T003509-287@post.gmane.org X-Y-GMX-Trusted: 0 X-FuHaFi: 0.63 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:64892 Archived-At: > I did (edebug-on-entry (quote fill-region) nil) and the debugger did not start, > so I must be missing something. (E.g., do I have to recompile fill-region with > debugging enabled, or something like that?) Sorry, I should have told you. Try M-x find-function RET fill-region RET followed by C-u C-M-x which calls `edebug-defun` and is also on the Emacs-Lisp menu. > Looking for "fill" in my initialization I found that > fill-individual-varying-indent and paragraph-ignore-fill-prefix were set to t. > However, setting both to nil did not help. I did not see anything else that > looks like suspicious. Let's see what happens when you debug this with and without your .emacs (obviously the bug may be caused by something else than filling). > I am satisfied with my workaround, which took remarkably little code. However, > Martin, if you are trying to debug this, I'll continue to pursue it for you - > just give me another clue. I hope `edebug-defun' works for you. You can use the following function (defun make-empty-compile-log () (interactive) (let ((inhibit-read-only t)) (with-current-buffer (get-buffer-create "*Compile-Log*") (delete-region (point-min) (point-max)) (display-buffer (current-buffer))))) to create, empty and display the *Compile-Log* buffer. Here I can't do anything because I have no recipe to reproduce your bug. > (Incidentally, I had poked around in the byte compiler code trying to find where > it was inserting the warnings - and I could not find it. At least Martin has > pointed me to where it happens now.) It's a bit tricky indeed. `display-warning' which is in the file warnings.el has the call (if warning-prefix-function (setq level-info (funcall warning-prefix-function level level-info))) where `warning-prefix-function' is set by `byte-compile-log-warning' to `byte-compile-warning-prefix'. If you edebug-defun both `display-warning' and `byte-compile-warning-prefix' you can observe how these functions and the "funcall" interact when compiling a file. martin