From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: jb@jeremybryant.net, justin@burkett.cc, emacs-devel@gnu.org
Subject: Re: URGENT - which-key FSF contributor status
Date: Tue, 18 Jun 2024 20:37:41 +0300 [thread overview]
Message-ID: <86sexap2xm.fsf@gnu.org> (raw)
In-Reply-To: <87plsews7o.fsf@posteo.net> (message from Philip Kaludercic on Tue, 18 Jun 2024 08:49:47 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: jb@jeremybryant.net, justin@burkett.cc, emacs-devel@gnu.org
> Date: Tue, 18 Jun 2024 08:49:47 +0000
>
> >> The :version tags of the defcustoms and deffaces will need to change.
> >
> > I can change the current tags to :package-version and also add :version
> > "30.1" tags.
>
> This has been done.
>
> >> Some faces use attributes such as underline or bold without testing
> >> for their availability first and without offering any fallbacks if
> >> they aren't. Is it okay to have those displayed using the default
> >> face?
> >
> > My guess is that this is just decoration, but someone who actually uses
> > which-key should comment on that. Specifically it appears to involve
> > the
> >
> > - which-key-special-key-face
> > - which-key-highlighted-command-face
>
> I think that it should be OK for 'which-key-special-key-face' to use
> :bold, because it is accompanied by :inverse-video that carries most of
> the visual effect.
>
> As for 'which-key-highlighted-command-face', I have removed the
> :underline and instead let it inherit from 'highlight'. I hope nobody
> objects to that. By default it doesn't make any difference, as it only
> affects people who have customised 'which-key-highlighted-command-list'.
>
> IMO we could merge the branch into master.
Thanks, I think it's okay to land this on master.
next prev parent reply other threads:[~2024-06-18 17:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87le4r98m9.fsf@jeremybryant.net>
[not found] ` <86le4rjv9p.fsf@gnu.org>
[not found] ` <87a5l78kc0.fsf@posteo.net>
[not found] ` <87msp6o9o4.fsf@jeremybryant.net>
2024-06-15 9:05 ` URGENT - which-key FSF contributor status Philip Kaludercic
2024-06-15 12:30 ` Eli Zaretskii
2024-06-15 12:58 ` Philip Kaludercic
2024-06-15 14:36 ` Stefan Kangas
2024-06-18 19:06 ` Stefan Kangas
2024-06-18 19:23 ` Philip Kaludercic
2024-06-18 19:30 ` Stefan Kangas
2024-06-18 19:41 ` Philip Kaludercic
2024-06-18 19:42 ` Stefan Kangas
2024-06-18 21:41 ` Philip Kaludercic
2024-06-20 14:26 ` Justin Burkett
2024-06-20 18:25 ` Stefan Kangas
2024-06-20 19:22 ` Philip Kaludercic
2024-06-20 21:16 ` Justin Burkett
2024-06-20 21:45 ` Stefan Kangas
2024-07-17 22:17 ` Philip Kaludercic
2024-07-18 11:54 ` Justin Burkett
2024-07-19 8:42 ` Philip Kaludercic
2024-06-15 15:19 ` Eli Zaretskii
2024-06-15 17:09 ` Philip Kaludercic
2024-06-15 17:42 ` Justin Burkett
2024-06-15 17:50 ` Eli Zaretskii
2024-06-18 8:49 ` Philip Kaludercic
2024-06-18 17:37 ` Eli Zaretskii [this message]
2024-06-16 19:07 ` Jeremy Bryant
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=86sexap2xm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jb@jeremybryant.net \
--cc=justin@burkett.cc \
--cc=philipk@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).