unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: info@protesilaos.com, 64799@debbugs.gnu.org, philipk@posteo.net
Subject: bug#64799: [PATCH] Add 'project-prompt-key' face
Date: Thu, 27 Jul 2023 08:28:58 +0300	[thread overview]
Message-ID: <83tttpncrp.fsf@gnu.org> (raw)
In-Reply-To: <11d47a2d-c068-b40f-ad86-6025201e8484@gutov.dev> (message from Dmitry Gutov on Thu, 27 Jul 2023 04:01:17 +0300)

> Date: Thu, 27 Jul 2023 04:01:17 +0300
> Cc: philipk@posteo.net, 64799@debbugs.gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
> 
> On 26/07/2023 14:10, Eli Zaretskii wrote:
> > Beware: the 'bold' face changes the metrics of the font glyphs (wrt
> > the 'medium' variant), and at least with some fonts could cause a
> > small 1- or 2-pixel vertical resize of the mini-window, which is
> > generally distracting and even annoying.
> 
> Only non-monospaced font, though, right? Or ones without a 'bold' variant.

No, not only those.  I'm talking about the _vertical_ metrics, so
whether the font is monospaced is not relevant.  Try marking files for
deletion in Dired, and you will see that, at least with some fonts and
some sizes.  Here on MS-Windows the default face's font (Courier New)
does that, for some sizes of the font.  I have customized
eldoc-highlight-function-argument to use 'underline' instead of 'bold'
for that very reason.

> Anyway, we're talking about switching from 'bold' to 'help-key-binding', 
> which uses the default weight.

That's fine.  I was under the impression that 'bold' is also being
considered, and wanted to warn about this.





  reply	other threads:[~2023-07-27  5:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-23  8:19 bug#64799: [PATCH] Add 'project-prompt-key' face Protesilaos Stavrou
2023-07-23 13:41 ` Philip Kaludercic
2023-07-23 13:49   ` Protesilaos Stavrou
2023-07-23 13:59     ` Philip Kaludercic
2023-07-24  5:53       ` Protesilaos Stavrou
2023-07-25  1:56         ` Dmitry Gutov
2023-07-25  6:39           ` Philip Kaludercic
2023-07-25 13:05             ` Dmitry Gutov
2023-07-26  4:50               ` Protesilaos Stavrou
2023-07-26 11:10                 ` Eli Zaretskii
2023-07-27  1:01                   ` Dmitry Gutov
2023-07-27  5:28                     ` Eli Zaretskii [this message]
2023-07-28  0:56                       ` Dmitry Gutov
2023-07-28  5:51                         ` Eli Zaretskii
2023-07-27  1:28                 ` Dmitry Gutov
2023-07-28  3:33                   ` Protesilaos Stavrou
2023-08-12  0:35                     ` Dmitry Gutov
2023-07-28  6:35                   ` Philip Kaludercic
2023-08-23 10:35                   ` Visuwesh
2023-08-23 12:18                     ` Philip Kaludercic
2023-08-23 12:44                       ` Dmitry Gutov
2023-08-23 14:13                         ` Visuwesh
2023-08-23 15:24                           ` Dmitry Gutov
2023-08-23 15:35                             ` Visuwesh
2023-08-23 15:37                               ` Dmitry Gutov
2023-08-23 15:45                                 ` Visuwesh
2023-08-23 16:40                                   ` Dmitry Gutov
2023-08-23 17:36                                     ` Visuwesh
2023-08-24 11:59                                     ` Mauro Aranda
2023-08-24 12:34                                       ` Dmitry Gutov

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=83tttpncrp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64799@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=info@protesilaos.com \
    --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).