From 68364bd3637b6944fa1f63a00dae5caf375afab9 Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Sun, 26 Jul 2026 02:36:20 +0200 Subject: conditionals can be terminated with F" now in addition to a single-quote (') This is useful when writing small macros directly on the command-line as in `sciteco --eval`. If you use double quoted shell strings, too many characters have to be escaped. If you use single-quotes, though, embedding the conditional end (') is annoying -- it would have to be written as '\''. --- doc/sciteco.7.template | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'doc/sciteco.7.template') diff --git a/doc/sciteco.7.template b/doc/sciteco.7.template index a3139bf..9d257a2 100644 --- a/doc/sciteco.7.template +++ b/doc/sciteco.7.template @@ -2337,7 +2337,7 @@ They are described in the reference section of this manual. .SS Conditionals .\" NOTE: Two quoted double-quotes are necessary to escape .\" a single double quote in macro arguments -.SCITECO_TOPIC """" conditional if then else +.SCITECO_TOPIC """" "|" "'" "F""" conditional if then else . Last but not least, \*(ST supports so called conditionals. They correspond to structured IF-THEN-ELSE statements @@ -2359,6 +2359,9 @@ stack \(em the remaining arguments may be evaluated by the Values accumulated on the expression stack by the \fIif\fP or \fIelse\fP blocks are not discarded by the terminating single-quote. In other words, conditionals may also return values. +Instead of a single quote, \(lqF"\(rq can also be used to terminate +the conditional \(em this can be handy when passing \*(ST scripts +on the command line, e.g. after \(lq\-\-eval\(rq. The possible conditions are defined in the following list. Unless \fIn\fP is defined optional, the conditionals described below yield an error if \fIn\fP is omitted: -- cgit v1.2.3