[...]
I am wondering about that, too. Maybe a [pderror] would be canvas-local and only report errors from objects belonging to the local canvas? And it would prepend the name of the object to the message?
Yes, that's a good idea, but what if there are two identical objects on the same canvas?
'text /tmp/foo.txt: can't open' 'text /tmp/foo.txt: read failed'
I think this could be solved with an extra outlet to [textfile], [soundfiler], [readsf~] and similar objects without going through the hassle of inventing a completely parsable error-message object.