From: Alex <agrambot@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28033@debbugs.gnu.org
Subject: bug#28033: [PATCH] Add new face 'header-line-highlight'
Date: Wed, 09 Aug 2017 23:36:19 -0600 [thread overview]
Message-ID: <874ltg6l2k.fsf@lylat> (raw)
In-Reply-To: <83k22crrfg.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 10 Aug 2017 07:13:23 +0300")
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Alex <agrambot@gmail.com>
>> Date: Wed, 09 Aug 2017 17:29:19 -0600
>>
>> Some header-line configurations don't interact nicely with the
>> 'highlight' face, particularly when they use the :box attribute.
>
> Can you elaborate about the problem and why introducing a new face is
> the solution for it?
>
> Thanks.
The problem is that the highlight face, which is used for highlighting
links and other mouse-sensitive buffer text frequently, may not always
look nice with the header-line face. I've attached a picture
demonstrating one possible issue. In it, the header-line face has a :box
attribute with line-width 4, but the highlight face does not. This
results in the characters at the ends being clipped.
A new face allows for users to customize it to match the customization
of the header-line face while not affecting all other uses of the
highlight face.
I believe the use case of this face is very similar to
'mode-line-highlight', which was added quite a while ago.
[-- Attachment #2: Screenshot_2017-08-09_23-20-30.png --]
[-- Type: image/png, Size: 10388 bytes --]
next prev parent reply other threads:[~2017-08-10 5:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 23:29 bug#28033: [PATCH] Add new face 'header-line-highlight' Alex
2017-08-10 4:13 ` Eli Zaretskii
2017-08-10 5:36 ` Alex [this message]
2017-08-11 16:15 ` Eli Zaretskii
2017-08-11 22:10 ` Alex
2017-08-12 7:20 ` Eli Zaretskii
2017-08-13 3:05 ` Alex
2017-08-13 14:27 ` Eli Zaretskii
2017-08-13 14:59 ` 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
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=874ltg6l2k.fsf@lylat \
--to=agrambot@gmail.com \
--cc=28033@debbugs.gnu.org \
--cc=eliz@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).