unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: emacs-devel@gnu.org
Subject: Re: Default Info face
Date: Wed, 18 Dec 2024 11:22:17 +0100	[thread overview]
Message-ID: <Z2KiWUO1BKPyaVv/@tuxteam.de> (raw)
In-Reply-To: <87wmfxgvjd.fsf@ledu-giraud.fr>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

On Wed, Dec 18, 2024 at 11:00:54AM +0100, Manuel Giraud via Emacs development discussions. wrote:
> Hi,
> 
> If I'm not mistaken, currently, the face used for the text body of Info
> nodes is `default'.  I was wondering if there would be any interest in
> having an `info' face defined for this usage.  I imagine that it could
> inherit for `variable-pitch-text' as "shr.el" is doing.  I also guess
> that it would have an impact on some sub-faces (like `info-title*' for
> example).  WDYT?

As long as I can define variable-pitch to be a fixed-pitch font ;-P

More seriously: I explicitly set as much as I can to be a fixed pitch
font. It works best with my combo of screen and sight. I think it's
a bad idea to encode a font property into a base font's name. It feels
like forcing others to swallow one's own esthetic preferences.

Thanks & cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2024-12-18 10:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 10:00 Default Info face Manuel Giraud via Emacs development discussions.
2024-12-18 10:22 ` tomas [this message]
2024-12-18 12:18   ` Eric S Fraga
2024-12-18 13:34     ` tomas
2024-12-18 12:46   ` Manuel Giraud via Emacs development discussions.
2024-12-18 12:54     ` tomas
2024-12-18 14:42       ` Manuel Giraud via Emacs development discussions.
2024-12-18 14:05 ` Eli Zaretskii
2024-12-18 14:50   ` Manuel Giraud via Emacs development discussions.
2024-12-18 15:28     ` Eli Zaretskii
2024-12-18 16:50       ` Manuel Giraud via Emacs development discussions.
2024-12-18 17:06         ` Eli Zaretskii
2024-12-18 17:17 ` Juri Linkov

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=Z2KiWUO1BKPyaVv/@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-devel@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    /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).