From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: compile.el underlining
Date: Fri, 17 Jun 2005 22:20:59 -0400 [thread overview]
Message-ID: <E1DjSx9-0003U3-EW@fencepost.gnu.org> (raw)
In-Reply-To: <jwvbr65j8k1.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 17 Jun 2005 11:41:26 -0400)
Is there a reason you use
'((default :inherit font-lock-warning-face)
(((supports :underline t)) :underline t))
rather than
'((default :inherit font-lock-warning-face)
(t :underline t))
after all, if it's not supported the setting is harmless.
'((t :inherit font-lock-warning-face :underline t))
I was thinking of the changes I recently made to the underline face.
If you know that those two would work equivalently, please change it.
prev parent reply other threads:[~2005-06-18 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 14:58 compile.el underlining Richard Stallman
2005-06-17 15:41 ` Stefan Monnier
2005-06-17 15:42 ` Stefan Monnier
2005-06-18 2:20 ` Richard Stallman [this message]
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=E1DjSx9-0003U3-EW@fencepost.gnu.org \
--to=rms@gnu.org \
--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).