From: Juri Linkov <juri@jurta.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: use faces on the mode-line for compile.el
Date: Sun, 24 Feb 2008 19:40:21 +0200 [thread overview]
Message-ID: <87hcfy45iv.fsf@jurta.org> (raw)
In-Reply-To: <200802232359.m1NNxFpa025055@sallyv1.ics.uci.edu> (Dan Nicolaescu's message of "Sat, 23 Feb 2008 15:59:14 -0800")
> 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.
> It can be seen with just the peripheral vision, or from farther away
> from the screen.
I think it would be more useful if the result message displayed
in the minibuffer was the same as at the end of the compilation
buffer, i.e.
Compilation exited abnormally with code 1 at Sun Feb 24 19:36:34
The date part at the end of this message may be not necessary
when displayed in the minibuffer.
> A simple patch can accomplish the above. It uses
> font-lock-warning-face which is designed to be highly visible.
What do you think about using a special compilation face
`compilation-error' that inherits from `font-lock-warning-face'?
This face is already used to highlight the exit code at the end of the
compilation buffer.
But maybe we should add a new face?
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2008-02-24 17:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 23:59 use faces on the mode-line for compile.el Dan Nicolaescu
2008-02-24 13:42 ` Stefan Monnier
2008-02-24 20:48 ` Dan Nicolaescu
2008-02-24 17:40 ` Juri Linkov [this message]
2008-02-24 20:53 ` Dan Nicolaescu
2008-02-24 23:23 ` Juri Linkov
2008-02-26 2:00 ` Xavier Maillard
-- strict thread matches above, loose matches on Subject: below --
2006-04-20 6:20 Dan Nicolaescu
2006-04-20 7:34 ` Nick Roberts
2006-04-20 18:27 ` Dan Nicolaescu
2006-04-21 13:07 ` 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=87hcfy45iv.fsf@jurta.org \
--to=juri@jurta.org \
--cc=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).