From: Tom Tromey <tromey@redhat.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>,
ding@gnus.org, emacs-devel <emacs-devel@gnu.org>
Subject: Re: eww
Date: Tue, 18 Jun 2013 13:27:24 -0600 [thread overview]
Message-ID: <87zjun43tv.fsf@fleche.redhat.com> (raw)
In-Reply-To: <jwva9mn8cbe.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 18 Jun 2013 15:13:22 -0400")
>> Info has a bunch of commands for jumping to the index and searching the
>> entire manual, etc. Reading the HTML version of the manual will never
>> be as convenient as reading the info version.
Stefan> AFAIK, it's easy to make HTML pages which includes most/all the meta
Stefan> information that Info pages contain. So you can then provide the "bunch
Stefan> of commands" without much trouble.
makeinfo (I'm looking at the output of makeinfo 5.0) already supplies a
link to the index, like:
<link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index">
This seems to be in every node.
So I think implementing "i" isn't too bad.
makeinfo also lets us know if the node has a menu:
<table class="menu" border="0" cellspacing="0">
So "m" and the digit arguments seem doable.
Searching seems a bit trickier.
I didn't look at issues if the HTML is in a single file rather than a
file per node.
I also didn't look at info-lookup-symbol. Though I note that at least
the Gtk manuals use some similar markup, so moving to HTML would
potentially broaden the documentation conveniently available to Emacs
users.
Tom
next prev parent reply other threads:[~2013-06-18 19:27 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 14:53 eww Lars Magne Ingebrigtsen
2013-06-16 15:21 ` eww Adam Sjøgren
2013-06-16 15:29 ` eww Lars Magne Ingebrigtsen
2013-06-16 15:46 ` eww Lars Magne Ingebrigtsen
2013-06-16 17:01 ` eww Dmitry Gutov
2013-06-16 17:06 ` eww Lars Magne Ingebrigtsen
2013-06-17 21:00 ` eww Lars Magne Ingebrigtsen
2013-06-17 23:35 ` eww Ted Zlatanov
2013-06-18 0:01 ` eww Lars Magne Ingebrigtsen
2013-07-09 13:20 ` eww Ted Zlatanov
2013-08-01 14:39 ` eww Lars Magne Ingebrigtsen
2013-07-09 10:23 ` eww Julien Cubizolles
2013-07-09 10:42 ` eww David Edmondson
2013-06-16 23:42 ` eww lee
2013-06-17 5:57 ` eww Lars Magne Ingebrigtsen
2013-06-17 18:46 ` eww lee
2013-06-18 2:19 ` eww Tom Tromey
2013-06-18 11:23 ` eww Lars Magne Ingebrigtsen
2013-06-18 14:34 ` eww Tom Tromey
2013-06-18 15:01 ` eww Lars Magne Ingebrigtsen
2013-06-18 15:43 ` eww Tom Tromey
2013-06-18 14:39 ` eww Tom Tromey
2013-06-18 15:14 ` eww Lars Magne Ingebrigtsen
2013-06-18 16:17 ` eww Tom Tromey
2013-06-18 19:06 ` eww Steinar Bang
2013-06-18 19:07 ` eww Stefan Monnier
2013-06-18 11:31 ` eww Lars Magne Ingebrigtsen
2013-06-18 14:42 ` eww Tom Tromey
2013-06-18 15:04 ` eww Lars Magne Ingebrigtsen
2013-06-18 19:13 ` eww Stefan Monnier
2013-06-18 19:17 ` eww Eli Zaretskii
2013-06-18 20:21 ` eww Stefan Monnier
2013-06-18 23:34 ` eww James Cloos
2013-06-19 2:50 ` eww Eli Zaretskii
2013-06-19 4:49 ` eww Stefan Monnier
2013-06-18 23:03 ` eww Xue Fuqiao
2013-06-19 3:03 ` eww Eli Zaretskii
2013-06-18 19:27 ` Tom Tromey [this message]
2013-06-18 23:40 ` eww Juri Linkov
2013-06-19 0:51 ` eww Stefan Monnier
2013-06-19 1:08 ` eww Russ Allbery
2013-06-19 10:14 ` eww Rasmus
2013-06-19 10:34 ` eww Christopher Schmidt
2013-06-25 7:43 ` eww lee
2013-06-25 9:05 ` eww Tassilo Horn
2013-06-25 13:27 ` eww Steinar Bang
2013-06-27 9:05 ` eww lee
2013-06-18 11:32 ` eww joakim
2013-06-18 12:16 ` eww Andreas Schwab
2013-06-18 13:57 ` eww Lars Magne Ingebrigtsen
2013-06-18 14:01 ` eww joakim
2013-06-19 10:21 ` eww Ivan Kanis
2013-06-19 11:52 ` eww Steinar Bang
2013-06-19 12:14 ` eww Ivan Kanis
2013-08-01 11:59 ` eww John Williams
2013-08-02 0:20 ` eww John Williams
2013-08-02 0:27 ` eww Lars Magne Ingebrigtsen
2013-08-02 19:48 ` eww Richard Stallman
2013-08-03 11:30 ` eww Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zjun43tv.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.
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 NNTP newsgroup(s).