unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Disseminate Dissent <disseminatedissent@protonmail.com>
Cc: 51538@debbugs.gnu.org
Subject: [bug#51538] First Patch Submit Ever: Additions to the Cookbook Documentation
Date: Mon, 8 Nov 2021 10:29:00 +0100	[thread overview]
Message-ID: <20211108092900.ldk4lkh3p7wl7msd@pelzflorian.localdomain> (raw)
In-Reply-To: <VyPYRcYjf2ooTP-SvB7fMY6DEwmp0tN6nbLgPruYVLs3fkxWrsSyhnfcPCVgjtlkijvdDo-HTkUZB77qgt-kKIF16JS2B0VNYBTWA2atPXk=@protonmail.com>

Hello Disseminate.

On Thu, Nov 04, 2021 at 03:17:48PM +0000, Disseminate Dissent via Guix-patches via wrote:
> Fixed the previous commit by adding the corresponding ToC heading to the new FAQ section.
> 
> Disseminate, Peace.

Thank you for your contribution!  It is good you add what you are
missing.  I’d prefer if someone else commented, though here are my
thoughts.  A FAQ seems like a good idea, however see below.


On Thu, Nov 04, 2021 at 03:17:48PM +0000, Disseminate Dissent via Guix-patches via wrote:
> From fce239a311724e38987640af02127179d569d88e Mon Sep 17 00:00:00 2001
> From: dissent <disseminatedissent@protonmail.com>
> Date: Sat, 30 Oct 2021 17:00:02 -0400
> Subject: [PATCH] doc: Added FAQ section with entry on using clear.

For the commit message, Guix uses the active voice “Add a FAQ section
with …”.


> * doc/guix-cookbook.texi: Added FAQ section.

Here too.


> ---
>  doc/guix-cookbook.texi | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/doc/guix-cookbook.texi b/doc/guix-cookbook.texi
> index dc52f6d38c..14c55926c2 100644
> --- a/doc/guix-cookbook.texi
> +++ b/doc/guix-cookbook.texi
> @@ -70,6 +70,7 @@ Weblate} (@pxref{Translating Guix,,, guix, GNU Guix reference manual}).
>  * System Configuration::        Customizing the GNU System
>  * Advanced package management:: Power to the users!
>  * Environment management::      Control environment
> +* FAQ::                         Commonly asked questions
>  
>  * Acknowledgments::             Thanks!
>  * GNU Free Documentation License::  The license of this document.

Menu comments like “Commonly asked questions” usually end in a period,
although the surrounding menu comments are missing the period as well.
Could you add a period for “Commonly asked questions”?  But see below.


> @@ -2964,6 +2965,21 @@ will have predefined environment variables
and procedures.
>  
>  Run @command{direnv allow} to setup the environment for the first time.
>  
> +@c *********************************************************************
> +@node FAQ
> +@chapter FAQ
> +
> +This chapter collects some frequently asked questions that might arise for new users.
> +
> +@menu
> +* How do I clear my terminal screen?
> +@end menu
> +
> +@node How do I clear my terminal screen?
> +@section How do I clear my terminal screen?
> +
> +The @command{clear} command is found in the @command{ncurses} package. 
> +
>  @c *********************************************************************
>  @node Acknowledgments
>  @chapter Acknowledgments
> -- 
> 2.33.1

I am uncertain if this tip should be in the cookbook, because I think
GNU Bash’s C-l (control+L) keyboard shortcutis easier to use and is
available in a default setup.  (Actually it may be GNU Readline’s
keyboard shortcut and Bash just uses Readline?)

Now indeed users may not know about it.  I do not know how to help
Guix users learn about features of programs that Guix offers but are
not part of Guix.


Nitpick: you have added an unnecessary space character at the end of the line

> +The @command{clear} command is found in the @command{ncurses} package. 

You should configure your editor to display those.

Regards,
Florian




  reply	other threads:[~2021-11-08  9:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-31 23:56 [bug#51538] First Patch Submit Ever: Additions to the Cookbook Documentation Disseminate Dissent via Guix-patches via
2021-11-01 15:10 ` [bug#51538] TOC jgart via Guix-patches via
2021-11-04 15:17 ` [bug#51538] First Patch Submit Ever: Additions to the Cookbook Documentation Disseminate Dissent via Guix-patches via
2021-11-08  9:29   ` pelzflorian (Florian Pelz) [this message]
2021-11-08  9:53     ` pelzflorian (Florian Pelz)
2021-11-08 13:50   ` Disseminate Dissent via Guix-patches via
2021-11-08 17:18     ` pelzflorian (Florian Pelz)
2021-11-08 19:04       ` Julien Lepiller
2021-11-11 17:04         ` pelzflorian (Florian Pelz)
2021-11-08 13:52 ` Disseminate Dissent via Guix-patches via
2021-11-09  0:21 ` [bug#51538] (no subject) jgart via Guix-patches via

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=20211108092900.ldk4lkh3p7wl7msd@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=51538@debbugs.gnu.org \
    --cc=disseminatedissent@protonmail.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).