From: Dave Goel <deego3@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Faces: How to clear an attribute while continuing to inherit other attributes?
Date: Thu, 10 Oct 2019 20:56:56 -0400 [thread overview]
Message-ID: <CAOCW0DjnTEiQMj2FaCEt7DAj3W+38+bV+KgfCW4FVisTVAgv=Q@mail.gmail.com> (raw)
In-Reply-To: <83k19cqvdi.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
> That's because you expect the attribute to magically change after you
set it.
Yes, I do :)
That's what face A would do if it did not inherit B (which specified the
attribute). It would magically follow whatever default does. for the
missing attribute.
On Thu, Oct 10, 2019 at 3:00 PM Eli Zaretskii <eliz@gnu.org> wrote:
> That's what 'unspecified' does, and it clearly isn't what Dave
> wanted. He wanted a value that says "clear that attribute", and
> there's no such value.
But, again, nothing stops us from providing one. For example, specifying
'clear would cause all inheritances to pause, so that the result of chasing
becomes 'unspecified, even if one of the ancestors specified the face.
.
What is DMARC?
>
>
[-- Attachment #2: Type: text/html, Size: 3136 bytes --]
next prev parent reply other threads:[~2019-10-11 0:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 2:42 Faces: How to clear an attribute while continuing to inherit other attributes? Dave Goel
2019-10-10 8:09 ` Eli Zaretskii
2019-10-10 15:56 ` Dave Goel
2019-10-10 15:59 ` Dave Goel
2019-10-10 17:37 ` Eli Zaretskii
2019-10-10 17:50 ` Dave Goel
2019-10-10 18:07 ` Eli Zaretskii
2019-10-10 18:26 ` Dave Goel
2019-10-10 18:39 ` Eli Zaretskii
[not found] ` <47578dbd-71ea-cb02-c337-96fb18af1915@lanl.gov>
[not found] ` <83k19cqvdi.fsf@gnu.org>
2019-10-11 0:56 ` Dave Goel [this message]
2019-10-11 1:13 ` Dave Goel
2019-10-11 8:37 ` Eli Zaretskii
2019-10-11 8:36 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOCW0DjnTEiQMj2FaCEt7DAj3W+38+bV+KgfCW4FVisTVAgv=Q@mail.gmail.com' \
--to=deego3@gmail.com \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.