You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 :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
The text was updated successfully, but these errors were encountered:
akavel
changed the title
[feature] "vim/compiler-like format"
[feature] "vim/compiler-like format" [-format=vim? =quickfix?]
Jul 7, 2016
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:cn
and:cp
commands. (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
oracle
tool has it as:-format=plain
The text was updated successfully, but these errors were encountered: