From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Ingo Lohmar <ingo.lohmar@posteo.net>
Subject: Re: :extend t inheritance
Date: Thu, 24 Oct 2019 17:38:35 +0200 [thread overview]
Message-ID: <87v9serw5g.fsf@gmail.com> (raw)
In-Reply-To: <83o8y6xnmn.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 24 Oct 2019 16:46:08 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> 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?
From emacs -Q:
Add and remove a bunch of lines in a version-controlled file, and open a
*vc-diff* buffer with C-x v =. Both diff-added and diff-removed faces
extend beyond EOL since by default their :extend attribute is set to t.
Then evaluate:
(set-face-extend 'diff-added 'unspecified)
(set-face-extend 'diff-removed 'unspecified)
(set-face-extend 'diff-changed t)
Intended effect: none, since diff-added and diff-removed inherit
diff-changed.
Actual effect: diff-added and diff-removed no longer extend beyond EOL.
Like Ingo, I'm not sure whether this (:extend not being inheritable) is
intentional or not; like Ingo, I would like to be able to set :extend t
on a few base faces.
next prev parent reply other threads:[~2019-10-24 15:38 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
2019-10-24 15:38 ` Kévin Le Gouguec [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9serw5g.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=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 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.