mirror of
https://git.in.rschanz.org/ryan77627/guix.git
synced 2025-01-11 13:49:23 -05:00
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.
This commit is contained in:
parent
6fb9759ef3
commit
98457ba47b
1 changed files with 3 additions and 4 deletions
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue