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 nice to run tests and get the stacktrace populated in the quickfix list. I imagine this is not straightforward but setting the right errorformat is probably a good place to start. This is what a sample stacktrace looks like:
KeyError: key foobar not found
[1] getindex
@ ./dict.jl:481 [inlined]
[2] function_name!()
@ ModuleName /path/to/folder/PackageName/src/filename.jl:17
I imagine a file placed in ./runtime/compiler/julia.vim might be able to parse this line: @ ModuleName /path/to/folder/PackageName/src/filename.jl:17:
I haven't tested this. I used other compiler plugin files in the vim source directory as reference. The help documentation for errorformat has a lot more options: https://vimhelp.org/quickfix.txt.html#errorformat.
The text was updated successfully, but these errors were encountered:
kdheepak
changed the title
Support for errorfmt
Support for errorformatSep 7, 2021
Vim has support for writing compiler plugins: https://vimhelp.org/usr_41.txt.html#write-compiler-plugin
It would be nice to run tests and get the stacktrace populated in the quickfix list. I imagine this is not straightforward but setting the right errorformat is probably a good place to start. This is what a sample stacktrace looks like:
I imagine a file placed in
./runtime/compiler/julia.vim
might be able to parse this line:@ ModuleName /path/to/folder/PackageName/src/filename.jl:17
:I haven't tested this. I used other compiler plugin files in the vim source directory as reference. The help documentation for
errorformat
has a lot more options: https://vimhelp.org/quickfix.txt.html#errorformat.The text was updated successfully, but these errors were encountered: