From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Oleksandr Gavenko <gavenko@bifit.com.ua>
Cc: help-gnu-emacs@gnu.org
Subject: Re: When and why Emacs developer change 'faces'?
Date: Thu, 27 Oct 2011 13:12:32 +0200 [thread overview]
Message-ID: <CAMXnza2p-M=MbWShM40B2+PBoaLnFP_DSOdcNNT5JewwvJoMEQ@mail.gmail.com> (raw)
In-Reply-To: <j8bb6m$qau$1@dough.gmane.org>
On Thu, Oct 27, 2011 at 12:19, Oleksandr Gavenko <gavenko@bifit.com.ua> wrote:
> But in pretest Emacs 24 (from alpha.gnu.org):
>
> 'compilation-info' inherited from 'success', which is:
In this particular case the rational might be more consistent UI
through the inheritance.
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-10-27 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 10:19 When and why Emacs developer change 'faces'? Oleksandr Gavenko
2011-10-27 11:12 ` suvayu ali [this message]
2011-10-27 19:15 ` Andreas Röhler
2011-10-28 7:29 ` Oleksandr Gavenko
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='CAMXnza2p-M=MbWShM40B2+PBoaLnFP_DSOdcNNT5JewwvJoMEQ@mail.gmail.com' \
--to=fatkasuvayu+linux@gmail.com \
--cc=gavenko@bifit.com.ua \
--cc=help-gnu-emacs@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.
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).