From ec95d1a6a6c015844e412572b6e5a185b072e01e Mon Sep 17 00:00:00 2001 From: Philip Hazel Date: Mon, 26 Feb 2007 14:07:04 +0000 Subject: MH's patch for allowing control characters as list separators. --- doc/doc-txt/NewStuff | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) (limited to 'doc/doc-txt/NewStuff') diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff index 677ab21aa..d39c6d3e2 100644 --- a/doc/doc-txt/NewStuff +++ b/doc/doc-txt/NewStuff @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/NewStuff,v 1.142 2007/02/14 15:33:40 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/NewStuff,v 1.143 2007/02/26 14:07:04 ph10 Exp $ New Features in Exim -------------------- @@ -375,6 +375,22 @@ Version 4.67 continue = condition = ${if eq{0}{}{true}{true}} +18. It is now possible to use newline and other control characters (those with + values less than 32, plus DEL) as separators in lists. Such separators must + be provided literally at the time the list is processed, but the string + expansion that happens first means that you can write them using normal + escape sequences. For example, if a new-line separated list of domains is + generated by a lookup, you can now process it directly by a line such as + this: + + domains = <\n ${lookup mysql{.....}} + + This avoids having to change the list separator in such data. Unlike + printing character separators, which can be included in list items by + doubling, it is not possible to include a control character as data when it + is set as the separator. Two such characters in succession are interpreted + as enclosing an empty list item. + Version 4.66 ------------ -- cgit v1.2.3