When a CommandInvocation encounters a broken pipe, an exception is thrown which is currently not caught. For example if a MessageMatch tries to feed the message into file(1), after matching magic numbers right at the beginning of the file, file(1) exits with the result while Piper still tries to feed the rest of the message. In this case the whole Piper context menu entry is missing since the uncaught exception fell right through the whole context menu factory.
This exception should be handled just by ignoring it, maybe issuing a warning to the error output if developer mode is on.
When a
CommandInvocationencounters a broken pipe, an exception is thrown which is currently not caught. For example if aMessageMatchtries to feed the message intofile(1), after matching magic numbers right at the beginning of the file,file(1)exits with the result while Piper still tries to feed the rest of the message. In this case the whole Piper context menu entry is missing since the uncaught exception fell right through the whole context menu factory.This exception should be handled just by ignoring it, maybe issuing a warning to the error output if developer mode is on.