diff options
author | Norbert Preining <norbert@preining.info> | 2020-04-04 03:02:28 +0000 |
---|---|---|
committer | Norbert Preining <norbert@preining.info> | 2020-04-04 03:02:28 +0000 |
commit | 4f71d4ff0d1e7ff4607b58eb7d030bd860e44f3a (patch) | |
tree | d4e56c2a7dc233a34c572829037ac8fb346f14bc /support/arara/doc/chapters/concepts.tex | |
parent | 6cacb7b2abf477262c442913f467f219649afb26 (diff) |
CTAN sync 202004040302
Diffstat (limited to 'support/arara/doc/chapters/concepts.tex')
-rw-r--r-- | support/arara/doc/chapters/concepts.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/support/arara/doc/chapters/concepts.tex b/support/arara/doc/chapters/concepts.tex index 0612279229..ef71eb10ab 100644 --- a/support/arara/doc/chapters/concepts.tex +++ b/support/arara/doc/chapters/concepts.tex @@ -10,7 +10,7 @@ Time for our first proper contact with \arara! I must stress that is very import A \emph{rule} is a formal description of how \arara\ handles a certain task. For instance, if we want to use \rbox{pdflatex} with our tool, we should have a rule for that. Directives are mapped to rules, so a call to a non-existent rule \rbox{foo}, for instance, will indeed raise an error: \begin{codebox}{Terminal}{teal}{\icnote}{white} - __ _ _ __ __ _ _ __ __ _ + __ _ _ __ __ _ _ __ __ _ / _` | '__/ _` | '__/ _` | | (_| | | | (_| | | | (_| | \__,_|_| \__,_|_| \__,_| @@ -263,7 +263,7 @@ Note that virtually any type of data can be used as parameter value, so lists, i When handling parametrized directives, \arara\ always checks if directive parameters and rule arguments match. If we try to inject a non-existent parameter in a parametrized directive, the tool will raise an error about it: \begin{codebox}{Terminal}{teal}{\icnote}{white} - __ _ _ __ __ _ _ __ __ _ + __ _ _ __ __ _ _ __ __ _ / _` | '__/ _` | '__/ _` | | (_| | | | (_| | | | (_| | \__,_|_| \__,_|_| \__,_| |