From: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: use faces on the mode-line for compile.el
Date: Thu, 20 Apr 2006 11:27:06 -0700 [thread overview]
Message-ID: <200604201827.k3KIR6Jn011259@scanner2.ics.uci.edu> (raw)
In-Reply-To: <17479.14739.797810.757480@farnswood.snap.net.nz> (Nick Roberts's message of "Thu, 20 Apr 2006 19:34:43 +1200")
Nick Roberts <nickrob@snap.net.nz> writes:
> > If the mode-line for the compilation buffer would be a bit more
> > visible it would be easier to see if a compilation is still running
> > (which is handy if you have compilations that take a long time and
> > don't want to spend too much time checking if it's done).
> > Also if the compilation fails it's nice to be able to see it faster.
> >
> > A simple patch can accomplish the above. It uses
> > font-lock-warning-face which is designed to be highly visible.
> >
> > IMO this is a very nice feature to have, and simple to implement...
> >
> > Thoughts?
> Font-lock-warning-face is normally used to report warnings or
> errors, not normal progress like "run".
I used font-lock-warning-face in 2 contexts, in this one you have a
point, maybe another face can be used.
> *Every* modeline already displays the keyword "Compiling" during
> compilation.
Right, and it would be nice for it to be in a different color so that
it can be seen if you are not exactly in front of the computer. I have
had this patch in my tree for a while and it does make a difference.
> It will only be seen if the compilation buffer is visible and this
> is already heavily fontified.
It is, but if the errors are not in the visible portion of the buffer
all that fontification does not help. Using font-lock-warning-face in
the modeline in case of an error gives a strong signal that you need
to look at the what is going on.
next prev parent reply other threads:[~2006-04-20 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 6:20 use faces on the mode-line for compile.el Dan Nicolaescu
2006-04-20 7:34 ` Nick Roberts
2006-04-20 18:27 ` Dan Nicolaescu [this message]
2006-04-21 13:07 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2008-02-23 23:59 Dan Nicolaescu
2008-02-24 13:42 ` Stefan Monnier
2008-02-24 20:48 ` Dan Nicolaescu
2008-02-24 17:40 ` Juri Linkov
2008-02-24 20:53 ` Dan Nicolaescu
2008-02-24 23:23 ` Juri Linkov
2008-02-26 2:00 ` Xavier Maillard
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=200604201827.k3KIR6Jn011259@scanner2.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@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 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).