From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: emacs-devel@gnu.org
Subject: Re: Default Info face
Date: Wed, 18 Dec 2024 16:05:35 +0200 [thread overview]
Message-ID: <86frmlm6hc.fsf@gnu.org> (raw)
In-Reply-To: <87wmfxgvjd.fsf@ledu-giraud.fr> (emacs-devel@gnu.org)
> Date: Wed, 18 Dec 2024 11:00:54 +0100
> From: Manuel Giraud via "Emacs development discussions." <emacs-devel@gnu.org>
> 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?
Info manuals don't look nice with variable-pitch fonts because
'makeinfo' fills and justifies lines assuming a fixed-pitch font, then
inserts hard newlines between lines. Try making your default face use
a variable-pitch font, and you will see that Info manuals look ugly:
some lines are too long, others too short.
Variable-pitch fonts could make sense if our documentation was
refilled, like we do in shr.el for HTML content. But that will not
work with Info, I think, at least not in the near future.
If variable-pitch face is out, what other advantages could we have by
using a specialized face in Info?
next prev parent reply other threads:[~2024-12-18 14:05 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
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 [this message]
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=86frmlm6hc.fsf@gnu.org \
--to=eliz@gnu.org \
--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).