gnunet-svn
[Top][All Lists]
Advanced

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

[taler-docs] branch master updated: document environment variable substi


From: gnunet
Subject: [taler-docs] branch master updated: document environment variable substitution (#7013)
Date: Fri, 25 Aug 2023 13:08:09 +0200

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new afbf55d8 document environment variable substitution (#7013)
afbf55d8 is described below

commit afbf55d869ed29f094c256a442edd49e1d1c9e2b
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Aug 25 13:08:07 2023 +0200

    document environment variable substitution (#7013)
---
 frags/common-conf-syntax.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/frags/common-conf-syntax.rst b/frags/common-conf-syntax.rst
index b2c364c0..27c8ba87 100644
--- a/frags/common-conf-syntax.rst
+++ b/frags/common-conf-syntax.rst
@@ -27,7 +27,8 @@ reference.  This can be simple, such as ``$TMPDIR/foo``, or 
complex, such as
 ``${TMPDIR:-${TMP:-/tmp}}/foo``.  The variables are expanded either using
 key-values from the ``[PATHS]`` section (see below) or from the environment
 (``getenv()``). The values from ``[PATHS]`` take precedence over those from
-the environment.
+the environment.  If the variable name is found in neither ``[PATHS]`` nor the
+environment, a warning is printed and the value is left unchanged.  Variables 
(including those from the environment) are expanded recursively, so if 
``FOO=$BAR`` and ``BAR=buzz`` then the result is ``FOO=buzz``.  Recursion is 
bounded to at most 128 levels to avoid undefined behavior for mutually 
recursive expansions like if ``BAR=$FOO`` in the example above.
 
 The ``[PATHS]`` section is special in that it contains paths that can be
 referenced using ``$`` in other configuration values that specify

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

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