guix-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

03/03: doc: Replace remaining 'unset mentions with %unset-value.


From: guix-commits
Subject: 03/03: doc: Replace remaining 'unset mentions with %unset-value.
Date: Thu, 25 Aug 2022 00:13:41 -0400 (EDT)

apteryx pushed a commit to branch master
in repository guix.

commit 98457ba47be4e8fc48a5d6256787c7a8dbd82b31
Author: Maxim Cournoyer <maxim.cournoyer@gmail.com>
AuthorDate: Thu Aug 25 00:10:57 2022 -0400

    doc: Replace remaining 'unset mentions with %unset-value.
    
    * doc/guix.texi (Networking Services): Replace 'unset with %unset-value.
    (Power Management Services): Likewise.
    (Complex Configurations): Likewise.
---
 doc/guix.texi | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index c8f18a1482..1e7fff9868 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -19846,7 +19846,7 @@ network.  A specific port value can be provided by 
appending the
 @code{:PORT} suffix.  By default, it uses the Jami bootstrap nodes, but
 any host can be specified here.  It's also possible to disable
 bootstrapping by explicitly setting this field to the
-@code{'unset} value.
+@code{%unset-value} value.
 
 @item @code{port} (default: @code{4222}) (type: maybe-number)
 The UDP port to bind to.  When left unspecified, an available port is
@@ -31362,7 +31362,7 @@ Each parameter definition is preceded by its type; for 
example,
 @samp{boolean foo} indicates that the @code{foo} parameter should be
 specified as a boolean.  Types starting with @code{maybe-} denote
 parameters that won't show up in TLP config file when their value is
-left unset, or is explicitly set to the @code{'unset} value.
+left unset, or is explicitly set to the @code{%unset-value} value.
 
 @c The following documentation was initially generated by
 @c (generate-tlp-documentation) in (gnu services pm).  Manually maintained
@@ -38983,8 +38983,7 @@ macro which is a shorthand of this.
 Sometimes a field should not be serialized if the user doesn’t specify a
 value.  To achieve this, you can use the @code{define-maybe} macro to
 define a ``maybe type''; if the value of a maybe type is left unset, or
-is set to the @code{'unset} value, then it will not be
-serialized.
+is set to the @code{%unset-value} value, then it will not be serialized.
 
 When defining a ``maybe type'', the corresponding serializer for the
 regular type will be used by default.  For example, a field of type



reply via email to

[Prev in Thread] Current Thread [Next in Thread]