From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59141@debbugs.gnu.org, Ihor Radchenko <yantar92@posteo.net>
Subject: bug#59141: 28.1.90; Face :extend when all the line but trailing \n is invisible
Date: Wed, 09 Nov 2022 23:19:42 +0100 [thread overview]
Message-ID: <87o7tfkby9.fsf@gmail.com> (raw)
In-Reply-To: <83cz9wux9l.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 09 Nov 2022 14:29:10 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> I said many times that people shouldn't willy-nilly use the :extent
> attribute, just because it looks cooler in some situation. The intent
> was and still is for faces not to have this attribute set, with very
> few very special exceptions, like the 'region' face. But people don't
> listen...
FWIW, my motivation for setting :extend on outline headings doesn't stem
from aesthetics.
Clearly delineating "sections" with colored backgrounds that span the
whole window width is a neat visual aid, IME; that's just one more guide
for the eye to exploit when e.g. locating the next same-level heading
(for those who like to look before they leap), getting a sense of how
"long" a section is (in terms of lines if expanded, or subsections if
folded), etc.
(Other people's sensibilities will necessarily differ, e.g. they might
find a document's structure easier to scan visually without distracting
colored backgrounds. I certainly don't mean to imply that :extending
heading backgrounds would be "objectively" better, only that it would be
genuinely helpful for _some_ folks)
So this "visual aid" aspect is why I suspect reporters think being able
to :extend outline heading backgrounds is about as desirable as
:extending the hl-line or region faces, and it's a shame it breaks down
when folding.
It's not a critical feature to be missing, and that motivation does not
invalidate the implementation challenges you highlight. I just wanted
to spell this point out FTR, as I didn't feel "it looks cooler" conveyed
it quite as convincingly 🙂
next prev parent reply other threads:[~2022-11-09 22:19 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 2:24 bug#59141: 28.1.90; Face :extend when all the line but trailing \n is invisible Ihor Radchenko
2022-11-09 7:49 ` Kévin Le Gouguec
2022-11-09 12:36 ` Eli Zaretskii
2022-11-09 17:12 ` Juri Linkov
2022-11-10 1:36 ` Ihor Radchenko
2022-11-10 7:45 ` Juri Linkov
2022-11-11 1:58 ` Ihor Radchenko
2022-11-11 7:46 ` Eli Zaretskii
2022-11-12 12:44 ` Ihor Radchenko
2022-11-11 8:13 ` Juri Linkov
2022-11-13 4:31 ` Ihor Radchenko
2022-11-11 12:30 ` Al Haji-Ali
2022-11-11 12:42 ` Eli Zaretskii
2022-11-11 16:00 ` Al Haji-Ali
2022-11-11 17:34 ` Eli Zaretskii
2022-11-11 19:47 ` Abdul-Lateef Haji-Ali
2022-11-11 20:09 ` Eli Zaretskii
2022-11-11 20:17 ` Abdul-Lateef Haji-Ali
2022-11-11 20:25 ` Eli Zaretskii
2022-11-12 11:18 ` Kévin Le Gouguec
2022-11-12 17:46 ` Juri Linkov
2022-11-13 10:50 ` Kévin Le Gouguec
2022-11-13 17:53 ` Juri Linkov
2022-11-13 22:22 ` Kévin Le Gouguec
2022-11-14 7:43 ` Juri Linkov
2022-11-14 11:02 ` Kévin Le Gouguec
2022-11-14 17:32 ` Juri Linkov
2022-11-14 17:44 ` Eli Zaretskii
2022-11-15 8:02 ` Juri Linkov
2022-11-15 14:42 ` Eli Zaretskii
2022-11-15 15:01 ` Ihor Radchenko
2022-11-15 15:05 ` Eli Zaretskii
2022-11-16 1:38 ` Ihor Radchenko
2022-11-16 13:01 ` Eli Zaretskii
2022-11-20 18:42 ` Juri Linkov
2022-11-14 22:22 ` Kévin Le Gouguec
2022-11-20 18:38 ` Juri Linkov
2022-11-22 7:52 ` Juri Linkov
2022-11-22 15:02 ` Eli Zaretskii
2022-11-22 17:35 ` Juri Linkov
2022-11-22 18:42 ` Eli Zaretskii
2022-11-22 19:16 ` Juri Linkov
2022-11-22 19:36 ` Eli Zaretskii
2022-11-12 17:52 ` Juri Linkov
2022-11-12 18:31 ` Eli Zaretskii
2024-01-25 22:53 ` Ihor Radchenko
2024-01-26 7:08 ` Eli Zaretskii
2022-11-09 12:29 ` Eli Zaretskii
2022-11-09 22:19 ` Kévin Le Gouguec [this message]
2022-11-10 7:10 ` Eli Zaretskii
2022-11-10 23:41 ` Kévin Le Gouguec
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=87o7tfkby9.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=59141@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yantar92@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).