From: "Alex Griffin" <a@ajgrf.com>
To: "Alan Mackenzie" <acm@muc.de>
Cc: 33967@debbugs.gnu.org
Subject: bug#33967: [Feature Request] Use proportional fonts in Info-mode
Date: Thu, 03 Jan 2019 16:41:55 -0500 [thread overview]
Message-ID: <30093ea1-76f5-4c6f-a64a-4ded0a0e3f6e@www.fastmail.com> (raw)
In-Reply-To: <20190103212321.29223.qmail@mail.muc.de>
On Thu, Jan 3, 2019, at 9:23 PM, Alan Mackenzie wrote:
> I'm happy to do without such "improvements", taking advantage of the high
> readability of my terminal's fixed width font. I take it you really mean
> "have the option of using proportional fonts". I've nothing against
> that.
Just having the option would be a nice improvement, there's no need to agree on the relative readability of each. Using more varied faces would also make it possible for you to style more elements of info manuals even in the terminal.
> I'm wholly unconvinced that making Info "better match" HTML is at all
> worthwhile. Where's the advantage in such a match, even supposing it is
> possible?
I guess I don't care whether they match or not. I was just calling attention to the fact that texinfo already knows what needs to be formatted in fixed-width. (In contrast, most man pages don't track the semantic information that's necessary to render them in anything but fixed-width.)
--
Alex Griffin
next prev parent reply other threads:[~2019-01-03 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 20:35 bug#33967: [Feature Request] Use proportional fonts in Info-mode Alex Griffin
[not found] ` <mailman.6730.1546547831.1284.bug-gnu-emacs@gnu.org>
2019-01-03 21:23 ` Alan Mackenzie
2019-01-03 21:41 ` Alex Griffin [this message]
2019-01-04 5:58 ` Glenn Morris
2019-01-04 6:50 ` Eli Zaretskii
2019-01-05 21:51 ` Juri Linkov
2019-01-06 3:35 ` Eli Zaretskii
2019-01-07 0:00 ` Juri Linkov
2019-01-07 3:36 ` Eli Zaretskii
2019-01-07 21:49 ` Juri Linkov
2019-01-06 19:41 ` Richard Stallman
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=30093ea1-76f5-4c6f-a64a-4ded0a0e3f6e@www.fastmail.com \
--to=a@ajgrf.com \
--cc=33967@debbugs.gnu.org \
--cc=acm@muc.de \
/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).