> i've tried in two ways, both failed: data matches='foo > ' (literal newline) and data matches='foo\n' (C-style escape sequence). first > trips plumber's parser, the other doesn't match anything -- perhaps \n is > taken literaly.
it looks like plumber's failure of vision. regexps don't take escapes like that. and on the other hand you can't say \ + literal newline, either. plumber misparses that. however, i thought of a really sneaky cheat, that is almost correct. since \n is 0a, and we almost never see 09 or 0b (ht and vt), we could build a sneaky character class to elude the parser: data matches 'error[ - ]' plumb start window and i've verified this does work on plan 9. a proper fix would be to change the string parser in plumber to convert '\' + 'n' to a newline. (but i do feel dirty.) - erik
