Hi sirjofri, Thank you for your reply. I was referring to having newlines specifically in filenames. Sometimes it's not one's own fault that filenames have them.
I wasn't really speaking about the way to represent a newline in rc, although thanks for details on that problem. My problem is to parse command output that has a newline in a filename. On my system, find(1) just prints the newline as is. So if the output looks like this: a b It is actually possible that it means one "a\n" file, not file "a" and file "b". Some commands, including ls(1) from plan9port, support quoting such files. But then the problem is how to parse them. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T11149f1f949593f5-M2e88845b92e7a51dca615ea9 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
