unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: znavko@disroot.org
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Danny Milosavljevic" <dannym@scratchpost.org>
Cc: 35525-done@debbugs.gnu.org
Subject: bug#35525: guix-manual proposals
Date: Fri, 03 May 2019 04:51:37 +0000	[thread overview]
Message-ID: <cd41f3d9c69ed63222ec540505749291@disroot.org> (raw)
In-Reply-To: <87h8acsfbm.fsf@gnu.org>

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

These are my current suggestions:
Here GuixSD rests instead of Guix System:

#. type: Plain text
#: doc/guix.texi:2650
msgid ""
"If you are not using the Guix System Distribution, consider adding the "
"following lines to your @file{~/.bash_profile} (@pxref{Bash Startup Files,,, "
"bash, The GNU Bash Reference Manual}) so that newly-spawned shells get all "
"the right environment variable definitions:"
#. type: Plain text
#: doc/guix.texi:3140
msgid ""
"Substitutes from the official build farm are enabled by default when using "
"the Guix System Distribution (@pxref{GNU Distribution}). However, they are "
"disabled by default when using Guix on a foreign distribution, unless you "
"have explicitly enabled them via one of the recommended installation steps "
"(@pxref{Installation}). The following paragraphs describe how to enable or "
"disable substitutes for the official build farm; the same procedure can also "
"be used to enable substitutes for any other substitute server."
The word 'installed' is wrong:

#. type: itemx
#: doc/guix.texi:3011 doc/guix.texi:3024
#, no-wrap
msgid "-A [@var{regexp}]"

#. type: table
#: doc/guix.texi:3015 doc/guix.texi:3028
msgid ""
"List packages currently available in the distribution for this system "
"(@pxref{GNU Distribution}). When @var{regexp} is specified, list only "
"installed packages whose name matches @var{regexp}."

In my own as I see, it does not list installed but all available packages.
Here it is 'many types of fs', but only one mentioned as example:

#. type: Plain text
#: doc/guix.texi:2268
msgid ""
"Alternatively, you may use a swap file. For example, assuming that in the "
"new system you want to use the file @file{/swapfile} as a swap file, you "
"would run@footnote{This example will work for many types of file systems (e."
"g., ext4). However, for copy-on-write file systems (e.g., btrfs), the "
"required steps may be different. For details, see the manual pages for "
"@command{mkswap} and @command{swapon}.}:"
And also if another language is ready to use (Spanish), need to say it on:

#. type: Plain text
#: doc/guix.texi:117
msgid ""
"This manual is also available in French (@pxref{Top,,, guix.fr, Manuel de "
"référence de GNU Guix}) and German (@pxref{Top,,, guix.de, Referenzhandbuch "
"zu GNU Guix}). If you would like to translate it in your native language, "
"consider joining the @uref{https://translationproject.org/domain/guix-manual."
"html, Translation Project}."
May 2, 2019 9:43 PM, "Ludovic Courtès" <ludo@gnu.org (mailto:ludo@gnu.org)> wrote:
 Danny Milosavljevic <dannym@scratchpost.org (mailto:dannym@scratchpost.org)> skribis:
 as far as I can see, it's also wrong in the original in the manual.

doc/guix.texi:

@item --list-available[=@var{regexp}]
@itemx -A [@var{regexp}]
List packages currently available in the distribution for this system
(@pxref{GNU Distribution}). When @var{regexp} is specified, list only
installed packages whose name matches @var{regexp}.
^^^^^^^^^ ?? 

Oops indeed! I guess you can push a fix. :-)

Ludo'.

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

  parent reply	other threads:[~2019-05-03  4:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 15:58 bug#35525: guix-manual proposals znavko
2019-05-01 18:03 ` znavko
2019-05-02  8:38 ` znavko
2019-05-02 15:22   ` Ludovic Courtès
2019-05-02 15:37     ` Danny Milosavljevic
2019-05-02 21:43       ` Ludovic Courtès
2019-05-03  4:51       ` znavko [this message]
2019-05-09 19:12       ` znavko

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=cd41f3d9c69ed63222ec540505749291@disroot.org \
    --to=znavko@disroot.org \
    --cc=35525-done@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=ludo@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.
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).