It would be cool if the tool supported an output format similar to "typical compilers", so that it could be easily fetched into vim's "quickfix" window, for easy jumping through the lines shown in the trace. For example:
1: running...
/foo/bar/baz/tool.go:123: (*whatever) FlavorText()
/foo/bar/baz/tool.go:55: (*whatever) Something()
/foo/bar/baz/main.go:22: CREATED BY: main()
5: ...
...
7: ...
...
When imported to vim with :cex system('panicparse -format=vim -only < foobar.log') | copen, this should make it trivial to jump between tool.go l.123, main.go l.22, etc., using :cn and :cp commands. (With properly configured :set errorformat=... in vim, the lines like 1: running... would still get displayed in the quickfix window, clearly separating the goroutines.)
edit: the Go oracle tool has it as: -format=plain
It would be cool if the tool supported an output format similar to "typical compilers", so that it could be easily fetched into vim's "quickfix" window, for easy jumping through the lines shown in the trace. For example:
When imported to vim with
:cex system('panicparse -format=vim -only < foobar.log') | copen, this should make it trivial to jump between tool.go l.123, main.go l.22, etc., using:cnand:cpcommands. (With properly configured:set errorformat=...in vim, the lines like1: running...would still get displayed in the quickfix window, clearly separating the goroutines.)edit: the Go
oracletool has it as:-format=plain