* on the Wed, Feb 21, 2007 at 08:05:20AM +0000, Peter Bowyer wrote:
>> I'd like to suggest a modification of string_nextinlist() to make it possible
>> to use certain control characters as list separators (as you probably know, a
>> less-than followed by any punctuation characters in the beginning of most
>> lists tell Exim that said punctuation character is the list separator).
>>
>> The simplest syntax would be if "<n" meant that newline (\n) is the separator
>> and "<t" meant tab (\t). "<s" for space might also be useful (or simply "< ",
>> which doesn't work today since space isn't considered a punctuation
>> character). Would this be likely to break existing configurations?
> I support that - it would remove the need for ugly 'sg'-ing of lists
> derived from (for example) MySQL queries. I guess there's a chance it
> might break a config that uses a literal 'n' as a separator, since
> it's a valid thing to do...
If possible, <\n would be better than <n imo. It's more obvious what
it's doing, and wont break anyones obscure config. There might be
reasons why you can't do it where there are 2 chars after the < though?
