unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: myglc2 <myglc2@gmail.com>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Documentation
Date: Fri, 02 Sep 2016 18:43:34 -0400	[thread overview]
Message-ID: <86oa45hqi1.fsf@gmail.com> (raw)
In-Reply-To: <CAEwRq=rMnT55mFVXEbvsgFGobmXd+ij5RWdXJ2ODzNmvqfDT2w@mail.gmail.com> (Vincent Legoll's message of "Fri, 2 Sep 2016 17:45:02 +0200")

Vincent Legoll <vincent.legoll@gmail.com> writes:

> Hello,
>
> when & how is the documentation here :
> https://www.gnu.org/software/guix/manual/guix.html
> updated ?
>
> I ask, because doing some git grep in a recent git checkout
> showed me something in doc/guix.texi that I couldn't find in
> that online manual...

Hi Vincent, the INFO that "comes with" 'guix pull' is from an earlier
git commit. The www html version may be even earlier, not sure.

Anyway, to read INFO from the latest 'git pull' you can do ...

git clone http://git.savannah.gnu.org/cgit/guix.git/
cd guix
guix environment guix
./bootstrap
./configure --localstatedir=/var
make

To read the INFO in emacs ...

emacs
'C-u F1 i'
"<YOURPATHTOGUIX>/guix/doc/guix.1"

Or, to always read the git version, I add this to my emacs init file ...

(with-eval-after-load 'info
  (info-initialize)
  (add-to-list 'Info-directory-list
	       " <YOURPATHTOGUIX>/guix/doc"))

HTH, George

      parent reply	other threads:[~2016-09-02 22:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 15:45 Documentation Vincent Legoll
2016-09-02 16:08 ` Documentation Leo Famulari
2016-09-02 16:45   ` Documentation Vincent Legoll
2016-09-02 17:09     ` Documentation Leo Famulari
2016-09-02 17:46       ` Documentation Vincent Legoll
2016-09-02 18:45         ` Documentation Leo Famulari
2016-09-03 10:43         ` Documentation Ludovic Courtès
2016-09-02 22:43 ` myglc2 [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=86oa45hqi1.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=vincent.legoll@gmail.com \
    /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).