me/guix
Archived
1
0
Fork 0
Code Activity

doc: cookbook: Fix misuses of double spacing.

Browse source 
* doc/guix-cookbook.texi (Extended example):
(StumpWM):
(Basic setup with manifests): Prevent Texinfo from ending a sentence where it
should not.
(Setting up a bind mount): Add two spaces where needed.
This commit is contained in:
Nicolas Goaziou 2020-04-24 18:32:56 +02:00
parent 9b42918edd
commit cc765e478a
No known key found for this signature in database
GPG key ID: DA00B4F048E92F2D
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/guix-cookbook.texi
View file

@ -1080,7 +1080,7 @@ mechanism of passing code around two running processes is called @uref{https://a
@subsubsection Utility functions @subsubsection Utility functions
When customizing @code{phases}, we often need to write code that mimics the When customizing @code{phases}, we often need to write code that mimics the
equivalent system invocations (@code{make}, @code{mkdir}, @code{cp}, etc.) commonly used during equivalent system invocations (@code{make}, @code{mkdir}, @code{cp}, etc.)@: commonly used during
regular ``Unix-style'' installations. regular ``Unix-style'' installations.
Some like @code{chmod} are native to Guile. Some like @code{chmod} are native to Guile.
@ -1576,7 +1576,7 @@ available for inclusion into the initrd.
You could install StumpWM with a Guix system by adding You could install StumpWM with a Guix system by adding
@code{stumpwm-checkout} and optionally @code{`(,stumpwm-checkout "lib")} @code{stumpwm-checkout} and optionally @code{`(,stumpwm-checkout "lib")}
packages to a system configuration file, e.g. @file{/etc/config.scm}. packages to a system configuration file, e.g.@: @file{/etc/config.scm}.
An example configuration can look like this: An example configuration can look like this:
@ -1792,7 +1792,7 @@ where we will store our profiles in the rest of this article.
Placing all your profiles in a single directory, with each profile getting its Placing all your profiles in a single directory, with each profile getting its
own sub-directory, is somewhat cleaner. This way, each sub-directory will own sub-directory, is somewhat cleaner. This way, each sub-directory will
contain all the symlinks for precisely one profile. Besides, "looping over contain all the symlinks for precisely one profile. Besides, "looping over
profiles" becomes obvious from any programming language (e.g. a shell script) by profiles" becomes obvious from any programming language (e.g.@: a shell script) by
simply looping over the sub-directories of @samp{$GUIX_EXTRA_PROFILES}. simply looping over the sub-directories of @samp{$GUIX_EXTRA_PROFILES}.
Note that it's also possible to loop over the output of Note that it's also possible to loop over the output of
@ -1862,7 +1862,7 @@ guix package -m /path/to/guix-my-project-manifest.scm -p "$GUIX_EXTRA_PROFILES"/
To upgrade all profiles, it's easy enough to loop over them. For instance, To upgrade all profiles, it's easy enough to loop over them. For instance,
assuming your manifest specifications are stored in assuming your manifest specifications are stored in
@samp{~/.guix-manifests/guix-$profile-manifest.scm}, with @samp{$profile} being the name @samp{~/.guix-manifests/guix-$profile-manifest.scm}, with @samp{$profile} being the name
of the profile (e.g. "project1"), you could do the following in Bourne shell: of the profile (e.g.@: "project1"), you could do the following in Bourne shell:
@example @example
for profile in "$GUIX_EXTRA_PROFILES"/*; do for profile in "$GUIX_EXTRA_PROFILES"/*; do