From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>,
Philip McGrath <philip@philipmcgrath.com>
Cc: Peter Polidoro <peter@polidoro.io>,
Julien Lepiller <julien@lepiller.eu>,
help-guix@gnu.org
Subject: Re: Finding Dependencies at Run Time
Date: Thu, 14 Jul 2022 15:27:52 +0200 [thread overview]
Message-ID: <86bktr3jtz.fsf@gmail.com> (raw)
In-Reply-To: <87a69cvsh7.fsf@elephly.net>
Hi,
(I am an avid Emacs user but to be honest I barely use Info manuals. Even
after many attempts to use them, I find the Info interface
counter-intuitive. Initially, I thought it was because I do not have
the habits and I forced myself to exclusively use it. The conclusions
are:
1. it is easier for me to open
https://guix.gnu.org/manual/devel/en/guix.html
even sometimes eww (which is a bit slow, BTW) and just directly
search. It is also really easy to reach the index.
2. aside the case where I exactly know beforehand what I am looking
for, I do not use the index. Instead, I use:
a) directly query a keyword, say C-f with Chromium or else
b) query with a search engine
end of the parenthesis. :-))
On Thu, 14 Jul 2022 at 13:28, Ricardo Wurmus <rekado@elephly.net> wrote:
> The convenience of using the Info document is that it is installed with
> “guix pull”, so it will always match your current version of Guix. The
> Info document is also more accessible than the HTML version because of
> the manually curated index (hit “i” in your Info reader and type away to
> get to a topic more quickly).
Why not also distribute the HTML manual along with the Info one? For
instance, on Debian,
$ find /usr/share/doc/ -type f -name "*.html" | wc -l
681
and I do not remember installing some *-doc packages.
For instance, why not just have
~/.config/guix/current/share/doc/guix/manual.html
at first, then populate this /doc/guix folder with all the fancy things
used for the online rendering. WDYT?
Cheers,
simon
prev parent reply other threads:[~2022-07-14 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 14:56 Finding Dependencies at Run Time Peter Polidoro
2022-07-13 16:03 ` Julien Lepiller
2022-07-13 17:47 ` Peter Polidoro
2022-07-13 18:39 ` Julien Lepiller
2022-07-13 18:51 ` Peter Polidoro
2022-07-13 21:02 ` Julien Lepiller
2022-07-14 17:47 ` Peter Polidoro
2022-07-16 21:53 ` Thiago Jung Bauermann
2022-07-14 8:25 ` Ricardo Wurmus
2022-07-14 8:48 ` Philip McGrath
2022-07-14 11:28 ` Ricardo Wurmus
2022-07-14 13:27 ` zimoun [this message]
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=86bktr3jtz.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--cc=peter@polidoro.io \
--cc=philip@philipmcgrath.com \
--cc=rekado@elephly.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).