summaryrefslogtreecommitdiff
path: root/doc/doc-docbook
diff options
context:
space:
mode:
authorHeiko Schlittermann (HS12-RIPE) <hs@schlittermann.de>2017-10-04 22:25:45 +0200
committerHeiko Schlittermann (HS12-RIPE) <hs@schlittermann.de>2017-10-06 21:46:34 +0200
commit1b7cf216d933b395dee691f05becca4dd44b26f7 (patch)
treedea219f75e33c52dbdbe49c7286c67ad4fb748fa /doc/doc-docbook
parent81f358daccc6f759456eb1ae0f8e456a9118ca9f (diff)
Check for proper output separator in expanding ${addresses:STRING} (Closes 2171)
Better yet would be to force setting the output separator literally, and not after expansion of the STRING. But this would be an incompatible change.
Diffstat (limited to 'doc/doc-docbook')
-rw-r--r--doc/doc-docbook/spec.xfpt10
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index 4a8e1d06e..c14094515 100644
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -10118,7 +10118,15 @@ character. For example:
.code
${addresses:>& Chief <ceo@up.stairs>, sec@base.ment (dogsbody)}
.endd
-expands to &`ceo@up.stairs&&sec@base.ment`&. Compare the &*address*& (singular)
+expands to &`ceo@up.stairs&&sec@base.ment`&. The string is expanded
+first, so if the expanded string starts with >, it may change the output
+separator unintentionally. This can be avoided by setting the output
+separator explicitly:
+.code
+${addresses:>:$h_from:}
+.endd
+
+Compare the &*address*& (singular)
expansion item, which extracts the working address from a single RFC2822
address. See the &*filter*&, &*map*&, and &*reduce*& items for ways of
processing lists.