From: Pronaip <pronaip@protonmail.com>
To: Gavin Smith <gavinsmith0123@gmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
"Ludovic Courtès" <ludo@gnu.org>, Texinfo <bug-texinfo@gnu.org>
Subject: Re: Any interest in using HTML for locally-installed Texinfo documentation?
Date: Sun, 14 Apr 2019 19:25:35 +0000 [thread overview]
Message-ID: <F1EwpYvQTQBmgLwulxKFZRTx69anhjVmrJz6j5DF5F7hJhuUKiKe3KJ3uXF8yxLTDLt7Qmcu0PvajLOEL1lRywWYCo6ijWtqAsBKRJfDP5w=@protonmail.com> (raw)
In-Reply-To: <20190413162121.GA28137@darkstar.example.net>
Not directly connected, but have yall seen how rust packages its documentation? Personally I am REALLY not a fan of everything running in a separate browser, one browser is more than enough. But as long as there is one browser, why not generate a searchable index that uses JS the way Rust did it?
And if people can't run JS, they can just grep through the folder with all the HTML files.
next prev parent reply other threads:[~2019-04-14 19:25 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 12:55 Any interest in using HTML for locally-installed Texinfo documentation? Gavin Smith
2019-04-01 14:01 ` sirgazil
2019-04-02 9:37 ` Ludovic Courtès
2019-04-02 15:02 ` Gavin Smith
2019-04-02 16:46 ` Per Bothner
2019-04-07 16:28 ` Gavin Smith
2019-04-08 15:12 ` Ludovic Courtès
2019-04-08 15:39 ` Pierre Neidhardt
2019-04-08 23:46 ` Gavin Smith
2019-04-09 6:25 ` Eli Zaretskii
2019-04-13 16:21 ` Gavin Smith
2019-04-14 19:25 ` Pronaip [this message]
2019-10-15 19:27 ` Gavin Smith
2019-10-15 20:20 ` P
2019-10-15 20:35 ` Gavin Smith
2019-10-15 20:40 ` Per Bothner
2019-10-15 21:00 ` Gavin Smith
2019-10-15 21:09 ` Per Bothner
2019-10-15 21:30 ` Gavin Smith
2019-10-16 1:39 ` Ricardo Wurmus
2019-10-19 20:31 ` Ludovic Courtès
2019-10-22 19:00 ` Gavin Smith
2019-10-22 20:18 ` Gavin Smith
2019-11-03 14:04 ` Ludovic Courtès
2019-11-03 15:37 ` Gavin Smith
2019-11-06 21:49 ` Ludovic Courtès
2019-04-03 21:21 ` Ludovic Courtès
2019-04-04 10:33 ` Gavin Smith
2019-04-02 15:31 ` Per Bothner
2019-04-03 21:11 ` Ludovic Courtès
2019-04-03 22:44 ` Per Bothner
2019-04-04 10:23 ` Gavin Smith
2019-04-04 16:02 ` Ludovic Courtès
2019-04-02 20:12 ` Ricardo Wurmus
2019-04-02 20:27 ` Ricardo Wurmus
2019-04-02 22:58 ` sirgazil
2019-04-02 22:10 ` Per Bothner
2019-04-02 23:09 ` sirgazil
2019-04-03 8:43 ` Gavin Smith
2019-04-03 14:23 ` sirgazil
2019-04-03 14:40 ` Per Bothner
2019-04-03 14:49 ` Ricardo Wurmus
2019-04-02 21:02 ` George Clemmer
2019-04-07 11:08 ` Gavin Smith
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='F1EwpYvQTQBmgLwulxKFZRTx69anhjVmrJz6j5DF5F7hJhuUKiKe3KJ3uXF8yxLTDLt7Qmcu0PvajLOEL1lRywWYCo6ijWtqAsBKRJfDP5w=@protonmail.com' \
--to=pronaip@protonmail.com \
--cc=bug-texinfo@gnu.org \
--cc=gavinsmith0123@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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/guix.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).