summaryrefslogtreecommitdiff
path: root/files/EXPRESSIONS
diff options
context:
space:
mode:
authorKlaus T. Aehlig <aehlig@linta.de>2023-03-07 09:40:05 +0100
committerKlaus Aehlig <aehlig@linta.de>2023-03-07 10:08:06 +0100
commitffa07d6f3b536f1a4b111c3bf5850484bb9bf3dc (patch)
treeaaa71f13d8a6de22039c5d4b79693e026788cf71 /files/EXPRESSIONS
parent418c90a02d13a2dd05bd604250ff8da889e1ef86 (diff)
downloadrules-typesetting-ffa07d6f3b536f1a4b111c3bf5850484bb9bf3dc.tar.gz
["latex", "verbatim"] make portable by using cat
... and the BLOB construct instead of echo. The echo(1) function is usually shell built in. This in itself is a reasonalbe design decission, as there is no need to start an external program just to join a couple of strings by spaces. Unfortunately, however, shells don't agree on the semantics of echo, in particular about what the correct invocation is to output a literal backslash; this can be seen from the following invovations. ~>dash -c 'echo '\''\\'\''' \ ~>bash -c 'echo '\''\\'\''' \\ ~> Now, both of those shells can act as the, supposedly POSIX-compliant sh. Work around these incompatibilities by generating BLOBs for the \begin/\end{verbatim} literal and join them with cat(1).
Diffstat (limited to 'files/EXPRESSIONS')
0 files changed, 0 insertions, 0 deletions