unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <rvgn@disroot.org>
To: sirgazil <sirgazil@zoho.com>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Feature Request for Guix Site
Date: Sun, 28 Apr 2019 11:50:05 -0400	[thread overview]
Message-ID: <ba27244c2701be242041f4271a9170d249b1b4c2.camel@disroot.org> (raw)
In-Reply-To: <49b356be-1b51-ae24-6d99-e7a36ae0a6ca@zoho.com>

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

xD. That actually makes sense. "Help" is actually the right term in
this context. My bad.
On Sun, 2019-04-28 at 09:14 -0500, sirgazil wrote:
> El 28/04/19 a las 7:55 a. m., Ludovic Courtès escribió:
> Hello,
> "Raghav Gururajan" <rvgn@disroot.org> skribis:
> Can someone who have admin privileges, add "Manual" tab to the menu
> of Guix Site (www.gnu.org/software/guix), which links to the Guix
> Manual (www.gnu.org/software/guix/manual)?
> There’s already a “Help” entry in the menu, which I think is
> goodenough, though perhaps we should rename it to “Support” or
> somethinglike that for clarity?
> 
> In the desktop, "Help" is conventionally used to access the manuals
> and other resources to help the user. Many applications list their
> manuals in a Help menu too. So I don't know if it should be renamed.
> Unless using "Help" is the reason why most people don't read manuals
> :P
> 
> 

[-- Attachment #2: Type: text/html, Size: 1767 bytes --]

  reply	other threads:[~2019-04-28 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-27  4:05 Feature Request for Guix Site Raghav Gururajan
2019-04-28 12:55 ` Ludovic Courtès
2019-04-28 14:14   ` sirgazil
2019-04-28 15:50     ` Raghav Gururajan [this message]
2019-04-29  9:59     ` Ludovic Courtès
2019-04-28 15:48   ` Raghav Gururajan

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=ba27244c2701be242041f4271a9170d249b1b4c2.camel@disroot.org \
    --to=rvgn@disroot.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=sirgazil@zoho.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).