| Pronouns | he/him |
| GitHub | https://github.com/Olical |
| Website | https://oli.me.uk |
@prozacchiwawa An absolute nightmare. That's why I wanted to get the VS Code canonical versions happy now so I have a baseline to compare issues in other editors to.
I straight up crashed Helix multiple times, that might be fine now that I've addressed the issues through VS Code tbh. And I could never tell if the bugs were Neovim debugger UI plugin bugs or my protocol misinterpretations.
There's so much to it! But it's a hard problem so I get it. Implementing schema validation helps.
And since it shares an nREPL connection, you can set a break point then eval with Calva etc, you don't have to use the debugger REPL.
It SHOULD also work cross editor too. So I could use VS Code as my debugger interface and Conjure in Neovim to eval.
https://github.com/Olical/clojure-dap and https://github.com/Olical/typedclojure-lsp both have working (on my machine) VS Code plugins now. So you can have Clojure interactive debugging and type checking from VS Code.
The type checking LSP also works in Helix and Neovim really well.
The debug adaptor works amazing in VS Code, seemed to work okay in Neovim with the right mix of plugins (fiddly!) and Helix just crashed but that's still in dev in Helix I think. Promising!
Clojure DAP working in VSCode too! https://github.com/Olical/clojure-dap
Let's get this published and in the hands of some testers!
The hilarious thing is it lets me in sometimes then kicks me out after some number of minutes with an obscure error.
I cannot stand anything Microsoft touches, the only reason I still have Windows on a drive is so I can play Counter-Strike on faceit.
