corrections
This commit is contained in:
parent
4f87d9d5b9
commit
c368334d05
2 changed files with 9 additions and 7 deletions
|
|
@ -167,9 +167,7 @@ We then say that the `manual.https_proxy.address` and the `manual.https_proxy.po
|
|||
|
||||
The other types of calculation we will be explained later in this tutorial.
|
||||
|
||||
Notice that the default value is not changed when :term:`user data <user data>` are settled.
|
||||
|
||||
If we set this :term:`user data`:
|
||||
We're going to load some :term:`user data <user data>` to see what happens:
|
||||
|
||||
.. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_041/config/01/config.yml
|
||||
:linenos:
|
||||
|
|
@ -226,9 +224,14 @@ We have this result:
|
|||
<span style="color: #5c5cff"> </span><span style="color: #5c5cff"> </span><span style="color: #5c5cff">┗━━ </span>📓 port (HTTPS Port): <span style="color: #ffd700">3128</span>
|
||||
</pre>
|
||||
|
||||
Notice that the default value is not changed when some values are settled from the :term:`user data file <user data>`.
|
||||
|
||||
The `https_proxy` variable's value is indeed modified, but the default value is still a calculated value (so the default value is indeed the value of the variable `http_proxy.address`, i.e., `"http.proxy.net"`), while the value defined by the user is `https.proxy.net`.
|
||||
|
||||
The Rougail CLI output usually displays the default value of a variable, even if a value has been assigned to this variable, meaning the default value is not used. Here we see that the variable's default value is not changed, but rather its actual value.
|
||||
With the standard output of the Rougail CLI, the terminal display output, we can see the default value of the variable.
|
||||
|
||||
By interpreting the results of this standard output, we can see that even if a value has been assigned to this variable
|
||||
(meaning the default value is not used) the variable's default value is not changed, but rather its actual value.
|
||||
|
||||
.. keypoints:: Key points progress
|
||||
|
||||
|
|
|
|||
|
|
@ -4,9 +4,9 @@ Define access to variable or family
|
|||
.. objectives:: Objectives
|
||||
|
||||
In this section we will see what a disabled variable or family is, and why it can be interesting
|
||||
to assign the `disabled` property to a variable or a family. We'll also learn the difference
|
||||
between disabling and hiding families or variables.
|
||||
to assign the `disabled` property to a variable or a family.
|
||||
Then we'll see the same thing for the `hidden` property.
|
||||
We'll also learn the difference between disabling and hiding families or variables.
|
||||
|
||||
We will:
|
||||
|
||||
|
|
@ -143,7 +143,6 @@ It outputs:
|
|||
<span style="color: #ff0000"> </span><span style="color: #ff0000"> </span><span style="color: #ff0000">from the YAML file "config/02/config.yml"</span>
|
||||
</pre>
|
||||
|
||||
|
||||
We can see that the Rougail CLI is warning us about the variables that we are trying to assign values on which are disabled.
|
||||
Because it is not logical. We are trying to assign values to variables that are not taken into account in the :term:`configuration`.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue