all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: DJV5@Austin.RR.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: byte-compile making erroneous *Compile Log*
Date: Sun, 31 May 2009 13:40:06 +0200	[thread overview]
Message-ID: <4A226C96.6040903@gmx.at> (raw)

 > I just downloaded emacs-snapshot for Emacs 23 and the problem still exists.
 > Rather than try to figure out what was causing it, I have implemented a simple
 > program that goes into the *Compile-Log* buffer and fixes the problem by
 > inserting the missing newlines before the file name.  I had not realized it
 > initially, but some of the "In <defun-name>" log entries do appear correctly on
 > their own lines.

So IMHO the only possible culprit is the call to `fill-region' in
`display-warning' which goes as:

	  (when (and warning-fill-prefix (not (string-match "\n" message)))
	    (let ((fill-prefix warning-fill-prefix)
		  (fill-column 78))
	      (fill-region start (point))))

Please try to edebug `fill-region' (with the *Compile-Log* buffer
displayed in some window to see what's going on).  I suppose one of
your .emacs settings wrt to filling cause the behavior you observe.

martin




             reply	other threads:[~2009-05-31 11:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-31 11:40 martin rudalics [this message]
2009-06-02  0:36 ` byte-compile making erroneous *Compile Log* David Vanderschel
  -- strict thread matches above, loose matches on Subject: below --
2009-06-02  6:23 martin rudalics
     [not found] ` <000401c9e4da$2e106680$650aa8c0@austin.rr.com>
     [not found]   ` <4A2773E2.9030001@gmx.at>
2009-06-05  8:16     ` David Vanderschel
2009-06-05  9:26       ` martin rudalics
2009-06-06  0:02         ` David Vanderschel
2009-06-06  8:21           ` martin rudalics
2009-05-30  9:52 martin rudalics
2009-05-31  5:17 ` David Vanderschel
2009-05-29 20:43 David Vanderschel
2009-05-29 21:09 ` Drew Adams
2009-05-29 22:50   ` David Vanderschel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A226C96.6040903@gmx.at \
    --to=rudalics@gmx.at \
    --cc=DJV5@Austin.RR.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.