unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: cyd@stupidchicken.com, handa@m17n.org, emacs-devel@gnu.org
Subject: Re: subtle problem of font-lock in *compilation* buffer
Date: Fri, 15 Sep 2006 10:29:41 -0400	[thread overview]
Message-ID: <E1GOEhJ-000735-Ku@fencepost.gnu.org> (raw)
In-Reply-To: <jwv3bavmu2m.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 13 Sep 2006 15:45:23 -0400)

    Sadly, it seems to be becoming more and more common for people to use spaces
    in their file/directory names.

We can try to find clever ways to distinguish, as you've done here.
(Thanks for thinking of it.)

Despite the best we can do, there will still be some names that could
be confused with parts of compiler messages, such that we can't
distinguish.  When that happens, we have to parse the compiler
messages properly.  If someone actually uses a name that causes
confusion, we have to tell him "Don't use names like that."

  parent reply	other threads:[~2006-09-15 14:29 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
2006-09-13 19:45         ` Stefan Monnier
2006-09-13 20:17           ` Chong Yidong
2006-09-15 14:29           ` Richard Stallman [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=E1GOEhJ-000735-Ku@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).