all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, handa@m17n.org
Subject: Re: subtle problem of font-lock in *compilation* buffer
Date: Wed, 13 Sep 2006 15:24:16 -0400	[thread overview]
Message-ID: <E1GNaLI-0007wC-9r@fencepost.gnu.org> (raw)
In-Reply-To: <87fyewpun5.fsf@stupidchicken.com> (message from Chong Yidong on Tue, 12 Sep 2006 18:50:06 -0400)

    > How about by the spaces in the "file name"?

    It would wrongly reject compilation messages for file names containing
    spaces.

I'd rather have that problem than the problem we have now.
People shouldn't use such names for their source files.

    >  Or, more generally, we may be able tell that a line matching with
    > "^/bin/sh " is not an error message.

    This would be wrong if you are compiling the file /bin/sh (unlikely as
    that may seem).

I'd rather have that problem than the problem we have now.  For
/bin/sh to be a source file is not just absurd, but impossible as well
on GNU-like systems.

  parent reply	other threads:[~2006-09-13 19:24 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
2006-09-13  4:07         ` Kenichi Handa
2006-09-13 19:24         ` Richard Stallman
2006-09-13 19:24       ` Richard Stallman [this message]
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=E1GNaLI-0007wC-9r@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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.