terminal: handle ctrl+c

[tox2ik]

control + C should terminate a text-stream handler like this.
Check out how cat, awk, sed and every other program in this category behaves.
Thanks.

[maruel]

The current behavior is very much intentional, see https://github.com/maruel/panicparse/#investigate-deadlock

[tox2ik]

crtl+c is not ctrl+\. I understand you may have reasons for ignoring ctrl+\, but your program is not behaving as a terminal program should by ignoring ctrl+c. I see that ctrl+d works as usual, which is something, at least. Not a big deal, but you are "wrong" about dismissing my pull request. Who cares about conventions, anyway, right?

Also, the installation instructions; go get github.com/maruel/panicparse/v2/cmd/pp , simply does not work;

$ go get github.com/maruel/panicparse/v2/cmd/pp
package github.com/maruel/panicparse/v2/cmd/pp: cannot find package "github.com/maruel/panicparse/v2/cmd/pp" in any of:
	/usr/lib/go/src/github.com/maruel/panicparse/v2/cmd/pp (from $GOROOT)
	/home/jaroslav/src/go/src/github.com/maruel/panicparse/v2/cmd/pp (from $GOPATH)

[maruel]

Part of the rationale is Windows. There's no SIGQUIT there.

Part of the rationale is that Ctrl-C will be caught by the first app in the pipe (generally go test) and will close nicely. If panicparse exits because stdin closes, it may cause problems. If panicparse was to close before the piped in tool would terminate, it would mess the pipeline.

I understand that normal tooling like cat, awk and sed just quit on SIGINT but panicparse intentionally wants to catch surprising failures.

About go get, I get:

$ go get github.com/maruel/panicparse/v2/cmd/pp
go: found github.com/maruel/panicparse/v2/cmd/pp in github.com/maruel/panicparse/v2 v2.0.1

There's some idiosyncracy with go module versioning I think the fix is try_real_v2 but I haven't had the time to confirm yet.