Fork me on GitHub
#calva
<
2024-03-07
>
Alexander Kouznetsov20:03:45

When I evaluate something in calva and it fails with an exception, how hard would it be to highlight the lines of the source code from the stacktrace in the editor? Similar to how it is done for failing tests? This would’ve sped up the development quite noticeably. Because today I have to switch to the repl output, click on Show stacktrace, find the line related to my source code, switch back to the source code, perform navigate to line number and type in the number that I found in the stacktrace.

2
pez20:03:54

Nice idea! Shouldn’t be too hard, I think.

👍 1
Alexander Kouznetsov21:03:04

Should I file an issue?

pez01:03:53

Yes, please do.

pez01:03:06

I guess we need to figure out when/how to clear the marker. But let’s discuss such things in the issue.

gtbono21:03:34

anyone using calva with vscode-neovim? how is the experience?

pez12:03:08

Not a vscode-neovim user, but I know that people are using it.

🙂 1
gtbono12:03:17

will try! my goal is to disable calva's paredit and keymaps, and use vscode-neovim with vim-sexp! we'll see how it goes

pez12:03:19

Keep us posted, please. And we may want to write about it in the Calva docs if you find a config that works.

calva 1