Consider No Output for Signal Interrupt
ChristianSilvermoon opened this issue · comments
Signal Interrupt (Exit Code 130) is generally not a failure per say.
While Shell Mommy's words of comfort and encouragement are lovely, nothing wrong necessarily happened here, this was a CTRL+C, an intentional interruption of the last command.
fixed with pr #16