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 17:28:46 +0200 [thread overview]
Message-ID: <86bjx9m2mp.fsf@gnu.org> (raw)
In-Reply-To: <877c7xdp0h.fsf@ledu-giraud.fr> (message from Manuel Giraud on Wed, 18 Dec 2024 15:50:06 +0100)
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: emacs-devel@gnu.org
> Date: Wed, 18 Dec 2024 15:50:06 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > 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.
>
> I've just tried and I don't see more ugliness when using a
> variable-pitch font in Info-mode. The lines "too long" and "too short"
> are already there when using a fixed-pitch font anyway.
That's specific to the font your system uses when you say
"variable-pitch". The results are not very predictable, and depend on
the OS and the fonts actually installed.
> > If variable-pitch face is out, what other advantages could we have by
> > using a specialized face in Info?
>
> Yes, if you rule out variable-pitch, there is not much left to this case
> then.
So why is it so important to use variable-pitch face for Info? What
are the advantages of that?
next prev parent reply other threads:[~2024-12-18 15:28 UTC|newest]
Thread overview: 17+ 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
2024-12-18 14:50 ` Manuel Giraud via Emacs development discussions.
2024-12-18 15:28 ` Eli Zaretskii [this message]
2024-12-18 16:50 ` Manuel Giraud via Emacs development discussions.
2024-12-18 17:06 ` Eli Zaretskii
2024-12-19 9:02 ` Manuel Giraud via Emacs development discussions.
2024-12-19 11:06 ` Stefan Kangas
2024-12-19 16:28 ` Manuel Giraud via Emacs development discussions.
2024-12-18 17:17 ` Juri Linkov
2024-12-19 9:32 ` Manuel Giraud via Emacs development discussions.
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=86bjx9m2mp.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).