diff options
| author | Kevin McCarthy <kevin@8t8.us> | 2022-12-12 15:05:18 -0800 |
|---|---|---|
| committer | Kevin McCarthy <kevin@8t8.us> | 2022-12-12 15:05:18 -0800 |
| commit | 16d8ad647bd1723bcd3cc14f5f299dbce65e2743 (patch) | |
| tree | ef68a868827781d1d7562121c9477c8e791f528c | |
| parent | ef2abed29fe02d3a38768ca62b2c8c485074bad3 (diff) | |
Move MuttLisp boolean config note.
I think it probably makes more sense to be inside the (if) function
documentation than (equal).
| -rw-r--r-- | doc/manual.xml.head | 38 |
1 files changed, 19 insertions, 19 deletions
diff --git a/doc/manual.xml.head b/doc/manual.xml.head index dea8eeaa..6f3de06c 100644 --- a/doc/manual.xml.head +++ b/doc/manual.xml.head @@ -7767,25 +7767,6 @@ echo (equal "one two" "`echo one two`") ==> "t" note: backticks inside double quotes generates a single argument: "one two" </screen> - <para> - Note that boolean configuration variables evaluate to the strings - "yes" or "no". You can see the value of other - kinds of configuration variables using the - <link linkend="echo">echo</link> command. - </para> -<screen> -unset allow_ansi -echo $allow_ansi - ===> "no" - -# the correct way to test a boolean: -echo (if (equal $allow_ansi "yes") "set" "unset") - ===> "unset" - -# the incorrect way to test a boolean: -echo (if $allow_ansi "set" "unset") - ===> "set" -</screen> </sect3> <sect3 id="muttlisp-not"> @@ -7864,6 +7845,25 @@ set spoolfile = "/var/mail/user" echo (if (equal $spoolfile "/var/mail/user") yes no) ==> "yes" </screen> + <para> + Note that boolean configuration variables evaluate to the strings + "yes" or "no". You can see the value of other + kinds of configuration variables using the + <link linkend="echo">echo</link> command. + </para> +<screen> +unset allow_ansi +echo $allow_ansi + ===> "no" + +# the correct way to test a boolean: +echo (if (equal $allow_ansi "yes") "set" "unset") + ===> "unset" + +# the incorrect way to test a boolean: +echo (if $allow_ansi "set" "unset") + ===> "set" +</screen> </sect3> </sect2> |