From: Juri Linkov <juri@linkov.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, Tassilo Horn <tsdh@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Variable pitch mode line
Date: Fri, 24 Dec 2021 10:21:59 +0200 [thread overview]
Message-ID: <86ee62o4bs.fsf@mail.linkov.net> (raw)
In-Reply-To: <jwv35mjgl6z.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 23 Dec 2021 14:50:26 -0500")
>> I don't believe that distro packagers might want to include Info manuals
>> in the HTML format when only Emacs will display them but not the standalone
>> Info reader.
>
> I'm not sure they include Info manuals mainly for the standalone info
> viewer either. But in any case, currently I don't think any doc viewer
> has a good story for "use HTML as replacement for Info", so it's clear
> that if we want it to happen, we need to start by making Emacs support
> it well. And only later, *maybe*, distros and other Info viewers will
> follow suit.
Then better to start with own dog food, and first display Emacs manuals
from HTML. There is already a make target that produces HTML files:
make html
Currently HTML files are generated in the source dir, that is wrong:
doc/emacs/emacs.html
The correct place would be in the Info output dir:
info/emacs.html
so it could reuse INFOPATH to find HTML Info manuals as well.
Then after visiting the generated HTML with eww, when proportional fonts
are enabled with `eww-toggle-fonts`, the output looks nice.
But rendering a large HTML file takes too much time. So while
a single HTML file is still preferable over multifile Info manuals,
the Info reader should limit rendering to the currently displayed
Info node only.
Using a single HTML file will also make online reading of remote HTML
manuals easier. For example, simply point the Emacs Info reader to
https://www.gnu.org/software/emacs/manual/html_mono/emacs.html
and it could fetch the whole HTML file, then navigate its nodes.
next prev parent reply other threads:[~2021-12-24 8:21 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 13:14 Variable pitch mode line Lars Ingebrigtsen
2021-12-22 14:01 ` Eli Zaretskii
2021-12-22 15:21 ` Stefan Kangas
2021-12-22 17:34 ` Juri Linkov
2021-12-22 20:14 ` Tassilo Horn
2021-12-22 20:42 ` Lars Ingebrigtsen
2021-12-22 20:49 ` Tassilo Horn
2021-12-23 17:16 ` Juri Linkov
2021-12-23 17:52 ` Stefan Kangas
2021-12-23 18:26 ` Eli Zaretskii
2021-12-23 18:38 ` Juri Linkov
2021-12-23 19:20 ` Eli Zaretskii
2021-12-23 19:39 ` Juri Linkov
2021-12-23 19:48 ` Eli Zaretskii
2021-12-23 19:55 ` Juri Linkov
2021-12-23 18:27 ` Lars Ingebrigtsen
2021-12-23 18:35 ` Juri Linkov
2021-12-23 18:47 ` Lars Ingebrigtsen
2021-12-23 19:00 ` Juri Linkov
2021-12-23 19:50 ` Stefan Monnier
2021-12-23 19:56 ` Eli Zaretskii
2021-12-23 20:12 ` Stefan Monnier
2021-12-23 20:17 ` Eli Zaretskii
2021-12-23 20:48 ` HTML info Yuan Fu
2021-12-24 8:34 ` Juri Linkov
2021-12-24 8:48 ` Eli Zaretskii
2021-12-24 9:02 ` Lars Ingebrigtsen
2021-12-24 9:38 ` Po Lu
2021-12-24 19:16 ` [External] : " Drew Adams
2021-12-25 18:01 ` Juri Linkov
2021-12-26 9:50 ` Yuan Fu
2021-12-26 10:20 ` Eli Zaretskii
2021-12-26 17:30 ` Juri Linkov
2021-12-27 18:32 ` Juri Linkov
2021-12-26 11:48 ` Lars Ingebrigtsen
2021-12-26 11:53 ` Eli Zaretskii
2021-12-26 11:57 ` Lars Ingebrigtsen
2021-12-26 12:07 ` Eli Zaretskii
2021-12-24 8:21 ` Juri Linkov [this message]
2021-12-24 11:42 ` Variable pitch mode line Eli Zaretskii
2021-12-24 12:08 ` Eli Zaretskii
2021-12-24 12:27 ` Lars Ingebrigtsen
2021-12-24 12:32 ` Po Lu
2021-12-24 12:53 ` Lars Ingebrigtsen
2021-12-24 13:12 ` Po Lu
2021-12-24 13:34 ` Lars Ingebrigtsen
2021-12-24 13:36 ` Po Lu
2021-12-24 13:45 ` Eli Zaretskii
2021-12-24 13:48 ` Lars Ingebrigtsen
2021-12-24 13:57 ` Eli Zaretskii
2021-12-24 14:01 ` Lars Ingebrigtsen
2021-12-24 14:33 ` Eli Zaretskii
2021-12-24 15:05 ` Lars Ingebrigtsen
2021-12-24 15:16 ` Eli Zaretskii
2021-12-24 15:43 ` Lars Ingebrigtsen
2021-12-24 15:44 ` Lars Ingebrigtsen
2021-12-24 17:03 ` Eli Zaretskii
2021-12-25 11:59 ` Lars Ingebrigtsen
2021-12-25 12:07 ` Eli Zaretskii
2021-12-26 11:28 ` Lars Ingebrigtsen
2021-12-26 11:43 ` Eli Zaretskii
2021-12-26 11:51 ` Lars Ingebrigtsen
2021-12-26 11:56 ` Eli Zaretskii
2021-12-26 12:02 ` Lars Ingebrigtsen
2021-12-26 12:11 ` Eli Zaretskii
2021-12-26 12:25 ` Lars Ingebrigtsen
2021-12-26 12:59 ` Eli Zaretskii
2021-12-27 10:32 ` Lars Ingebrigtsen
2021-12-27 14:52 ` Eli Zaretskii
2021-12-26 15:32 ` Stefan Monnier
2021-12-25 17:54 ` Juri Linkov
2021-12-26 1:27 ` Po Lu
2021-12-26 7:39 ` Juri Linkov
2021-12-26 8:46 ` Eli Zaretskii
2021-12-23 19:27 ` Tassilo Horn
2021-12-23 19:39 ` Eli Zaretskii
2021-12-23 19:48 ` Tassilo Horn
2021-12-23 20:02 ` Eli Zaretskii
2021-12-23 20:13 ` Eli Zaretskii
2021-12-23 19:45 ` Juri Linkov
2021-12-23 20:41 ` Tomas Hlavaty
2021-12-23 20:51 ` Yuan Fu
2021-12-23 20:56 ` Tomas Hlavaty
2021-12-23 21:00 ` Yuan Fu
2021-12-23 21:24 ` Tomas Hlavaty
2021-12-23 21:41 ` Yuan Fu
2021-12-23 23:00 ` Tomas Hlavaty
2021-12-23 23:28 ` Yuan Fu
2021-12-24 7:14 ` Tomas Hlavaty
2021-12-24 7:05 ` Eli Zaretskii
2021-12-24 0:50 ` [External] : " Drew Adams
2021-12-24 3:58 ` Yuan Fu
2021-12-24 5:00 ` Drew Adams
2021-12-24 6:53 ` Eli Zaretskii
2021-12-24 6:50 ` Eli Zaretskii
2021-12-24 7:55 ` Tomas Hlavaty
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=86ee62o4bs.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=tsdh@gnu.org \
/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).