all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
Cc: handa@m17n.org, emacs-devel@gnu.org
Subject: Re: subtle problem of font-lock in *compilation* buffer
Date: Tue, 12 Sep 2006 23:42:50 -0400	[thread overview]
Message-ID: <87vensh1ol.fsf@furball.mit.edu> (raw)
In-Reply-To: <87fyewpun5.fsf@stupidchicken.com> (Chong Yidong's message of "Tue\, 12 Sep 2006 18\:50\:06 -0400")

>> I don't know whqether it's uncommon or not, but if a packages uses
>> libtool with "-version-info M:N:L" argument, the above line
>> appears.  It may be too ad hoc but we can tell font-lock
>> that a line matching with the regexp "-version-info [0-9]"
>> is not an error message (if font-lock accepts such a
>> request).
>
> I don't see a straightforward way of doing this, but I guess it's
> worth a shot.

On further consideration, it's impossible to handle this perfectly:
consider compiling a file named "foo -version-info 1", which gives
rise to the error message

foo -version-info 1:0: blah blah
^^^^^^^^^^^^^^^^^^^

  reply	other threads:[~2006-09-13  3:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06  8:16 subtle problem of font-lock in *compilation* buffer Kenichi Handa
2006-09-11  2:59 ` Chong Yidong
2006-09-11  3:56   ` Kenichi Handa
2006-09-11 19:57   ` Richard Stallman
2006-09-12 22:50     ` Chong Yidong
2006-09-13  3:42       ` Chong Yidong [this message]
2006-09-13  4:07         ` Kenichi Handa
2006-09-13 19:24         ` Richard Stallman
2006-09-13 19:24       ` Richard Stallman
2006-09-13 19:45         ` Stefan Monnier
2006-09-13 20:17           ` Chong Yidong
2006-09-15 14:29           ` Richard Stallman
2006-09-15 16:27             ` Stefan Monnier
2006-09-16 19:04               ` Richard Stallman
2006-09-17 19:17             ` Juri Linkov
2006-09-18 18:50               ` Richard Stallman

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=87vensh1ol.fsf@furball.mit.edu \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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.