Requests for comments -- raw strings and WRITE Peter McGoron (08 Mar 2026 17:36 UTC)
(missing)
Re: Requests for comments -- raw strings and WRITE Peter McGoron (10 Mar 2026 20:09 UTC)
Re: Requests for comments -- raw strings and WRITE Peter McGoron (10 Mar 2026 20:11 UTC)
Re: Requests for comments -- raw strings and WRITE Alex Shinn (12 Mar 2026 03:23 UTC)
Re: Requests for comments -- raw strings and WRITE Peter McGoron (12 Mar 2026 13:08 UTC)
Re: Requests for comments -- raw strings and WRITE Alex Shinn (12 Mar 2026 13:36 UTC)
Re: Requests for comments -- raw strings and WRITE Vincent Manis (he/him) (08 Mar 2026 19:05 UTC)

Re: Requests for comments -- raw strings and WRITE Peter McGoron 10 Mar 2026 20:07 UTC

It seems John's email didn't get sent to the list, I'll quote it here:

 > I think it would be better to have write-fancy, so that a list or
vector (or array) would come out with all string elements printed raw,
recursively. Since the procedure can see the whole string, it can choose
the tag by itself. Indeed, a single character would almost always
suffice, as there are more than 150,000 graphical Unicode characters.
Alternatively, there are more than that many six-letter strings.