--- Begin Message ---
|
Subject: |
24.4.50; Info-quoted face should inherit default |
|
Date: |
Tue, 22 Jul 2014 10:15:38 +0200 |
Currently, the `Info-quoted' face is defined as follows in info.el:
(defface Info-quoted
'((t :family "courier"))
"Face used for quoted elements.")
I do no think that mode faces should *hard-code* specific font families,
and thus bypass any customization of the default face that the user
might have made to pick their preferred font.
Besides, courier is not a particularly friendly choice. There is no
specific font with that name. The actual font depends on the font
configuration and aliasing picked by the OS and the user, and depending
on the quality of this configuration the appearance of this font varies
greatly. If the configuration is particularly poor, or if a proper
substitute font is missing, Emacs might even fall back to X11 bitmap
fonts, which are particularly ugly on modern screens.
So just because it's pretty on your screen, it doesn't need to be pretty
on some else's screen.
Please remove the hard-coded font family and inherit from the default
face instead.
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#18077: 24.4.50; Info-quoted face should inherit default |
|
Date: |
Sun, 04 Apr 2021 10:33:30 +0300 |
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 3 Apr 2021 18:58:37 -0500
> Cc: 18077@debbugs.gnu.org, Sebastian Wiesner <swiesner@lunaryorn.com>
>
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> >> For `info-quoted' we could use the same font families as e.g.
> >> StackOverflow uses for code blocks:
> >
> > It's probably a good source of inspiration, but we have to take into
> > account that the font of the "normal text" is usually proportional in
> > stackoverflow, whereas it's usually monospaced in Emacs.
>
> Is this now fixed by this commit, or is there more to do here?
>
> Author: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri May 13 13:30:33 2016 -0700
>
> Improve display of tex-verbatim and Info quoted
I think that commit changed things sufficiently to consider the issue
closed, and any further issues with what we use nowadays should be
submitted as a new bug report with updated facts and complaints.
Closing.
--- End Message ---