unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Suhail <suhail@bayesians.ca>
To: Christina O'Donnell <cdo@mutix.org>
Cc: Help-Guix mailing list <help-guix@gnu.org>
Subject: Re: Location of Guix manpages in foreign distribution
Date: Mon, 29 Jan 2024 07:20:16 +0000	[thread overview]
Message-ID: <87zfwoobbn.fsf@> (raw)
In-Reply-To: <310c3276-14c8-147d-8c3f-f05b4fd33730@mutix.org>

"Christina O'Donnell" <cdo@mutix.org> writes:

> If I'm not mistaken, ~/.config/guix/ is only for the environment that Guix
> itself runs in.

Yes, and the specific manuals (manpages instead of info) I was looking
for were for the installed Guix version.  It's unclear if the manpages
for Guix were ever installed.  It's possible they were, but subsequent
updates through "sudo -i guix pull" didn't maintain them.

Upon digging some more, I realized that "guix" doesn't have an output
that only generates the manpages.  So doing something like "guix install
guix:manpages" was a no-go.  Additionally, even if something like that
had existed the version I would've gotten would have lagged behind the
Guix installed on the system.  Doing a "guix install guix" will get you
access to the Guix manpages, but will also override the system Guix with
a slightly older revision.  The latter being undesirable for my needs.

It turns out Guix, when built, generates the manpages via a tool called
help2man which generates manpages from the --help and --version output.
So a not-as-well-formatted alternative to something like "man guix-gc"
is simply to invoke "guix gc --help".  On Emacs, this can be made
slightly more user-friendly via [noman].

[noman]: <https://github.com/andykuszyk/noman.el>

-- 
Suhail



       reply	other threads:[~2024-01-29  7:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <310c3276-14c8-147d-8c3f-f05b4fd33730@mutix.org>
2024-01-29  7:20 ` Suhail [this message]
2024-01-26 15:26 Location of Guix manpages in foreign distribution Suhail

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=87zfwoobbn.fsf@ \
    --to=suhail@bayesians.ca \
    --cc=cdo@mutix.org \
    --cc=help-guix@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.
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).