From: Eli Zaretskii <eliz@gnu.org>
To: Ingo Lohmar <ingo.lohmar@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: :extend t inheritance
Date: Thu, 24 Oct 2019 16:46:08 +0300 [thread overview]
Message-ID: <83o8y6xnmn.fsf@gnu.org> (raw)
In-Reply-To: <87zhhrmcaq.fsf@kenko.localhost.com> (message from Ingo Lohmar on Wed, 23 Oct 2019 22:34:05 +0200)
> From: Ingo Lohmar <ingo.lohmar@posteo.net>
> Date: Wed, 23 Oct 2019 22:34:05 +0200
>
> I am messing around with the face :extend attribute and I am wondering
> about sth. The elisp manual says
>
> The value should be ‘t’ to display the empty space between end of
> line and edge of the window using this face, or ‘nil’ to not use
> this face for the space between the end of the line and the edge of
> the window. When Emacs merges several faces for displaying the
> empty space beyond end of line, only those faces with ‘:extend’
> non-‘nil’ will be merged.
>
> I briefly read the original discussion of this feature, but did not find
> a reason for this peculiar behavior when it comes to inheritance; if
> there was a reason given, could someone point me to it?
I don't think I understand what you are saying or asking. The text
that you cite doesn't mention inheritance at all. Could you clarify
the issue?
> Background: I manage all faces without themes on my own, and I rely
> heavily on inheritance. As it stands now, IIUC (and according to some
> tests), I have to specify :extend t on ~30 faces (mostly diff, ediff,
> smerge, magit-ediff and -blame etc) that all derive from 3 or 4 base
> faces. It seems to me that this renders the whole point of inheritance
> moot.
>
> My natural reaction would have been to specify :extend t on some base
> faces, and for faces that inherit from them, explicitly say :extend nil
> only for those faces for which I do not want that extension. Isn't that
> at least as flexible, and more in the spirit of inheriting attributes?
Are you saying that the :extend attribute isn't inherited via
:inherit? Or are you saying something else? In any case, could you
please show a recipe or an example of what you tried and how the
results didn't match your expectations?
Thanks.
next prev parent reply other threads:[~2019-10-24 13:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 20:34 :extend t inheritance Ingo Lohmar
2019-10-24 13:46 ` Eli Zaretskii [this message]
2019-10-24 15:38 ` Kévin Le Gouguec
2019-10-24 17:39 ` Ingo Lohmar
2019-10-24 22:22 ` Ergus
2019-10-26 1:49 ` Ergus
2019-10-26 7:28 ` Eli Zaretskii
2019-10-26 19:21 ` Ergus
2019-10-26 19:45 ` Eli Zaretskii
2019-10-26 23:13 ` Ergus
2019-10-27 5:51 ` Eli Zaretskii
2019-10-27 11:01 ` Ergus
2019-10-29 14:27 ` Eli Zaretskii
2019-10-28 21:24 ` Ergus
2019-10-29 3:28 ` Eli Zaretskii
2019-10-26 8:55 ` Ingo Lohmar
2019-10-26 11:41 ` Ergus
2019-10-26 11:49 ` Ingo Lohmar
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=83o8y6xnmn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ingo.lohmar@posteo.net \
/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).