unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Philip McGrath" <philip@philipmcgrath.com>
To: "Felix Lechner" <felix.lechner@lease-up.com>,
	"Nicolas Débonnaire" <n.debonnaire@gmail.com>,
	"Jack Hill" <jackhill@jackhill.us>
Cc: "Brian Cully" <guix-devel@gnu.org>
Subject: Re: git send-email
Date: Sun, 19 Nov 2023 12:30:18 -0500	[thread overview]
Message-ID: <951eab34-dac8-484a-96fa-3b6ac49fc823@app.fastmail.com> (raw)
In-Reply-To: <87o7fpwt5i.fsf@lease-up.com>

Hi,

On Sun, Nov 19, 2023, at 12:27 PM, Felix Lechner wrote:
> Hi Philip,
>
> On Sun, Nov 19 2023, Philip McGrath wrote:
>
>>  1. Can we reorganize things on the website so that the non-"devel" manual is much more prominent than the other one?
>
> Was the "non" possibly a typo? In my opinion, the non-devel manual
> should no longer be published.
>

Yes, a typo, or perhaps another example of how confusing this is!

> Please feel free to chime in under
>
>   https://issues.guix.gnu.org/51000
>
>>  2. I wish there were a Guix package I could install to read the HTML documentation locally.
>
> As an Emacs user, I select "guix" after hitting "C h R". I can search
> the index with "i".
>
> A standalone 'info' executable may provide a similarly convenient kind
> of local access to the manual.
>

I have used the local info version, but I like the HTML version better.

Philip


  reply	other threads:[~2023-11-19 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18 13:58 git send-email Nicolas Débonnaire
2023-11-18 17:26 ` Jack Hill
2023-11-19 15:59   ` Nicolas Débonnaire
2023-11-19 16:22     ` Philip McGrath
2023-11-19 17:27       ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-11-19 17:30         ` Philip McGrath [this message]
2023-11-19 17:30       ` Matt

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=951eab34-dac8-484a-96fa-3b6ac49fc823@app.fastmail.com \
    --to=philip@philipmcgrath.com \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --cc=jackhill@jackhill.us \
    --cc=n.debonnaire@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.
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).