Sebastian Pfitzner
Sebastian Pfitzner
Yes, that's almost trivial to do. I'd kinda like to have tighter integration though, but that's a bigger project; might be worth doing the simple thing first.
Yeah, that's the big thing. AFAICT that should basically just work, as long as you actually have a local VSCode instance (so not in the browser via codespaces or code-server)....
Ref https://github.com/julia-vscode/julia-vscode/pull/1507. Getting the completions is easy, dealing with "merge conflicts" isn't :)
We can just stick with the current implementation I think, yes.
Don't you need `"${env:JULIA_DIR}/bin/julia.exe"` here?
Updating JuliaFormatter to v2 is not currently possible, since it still depends on JuliaSyntax 0.4.
I think this basically is https://github.com/JuliaEditorSupport/zed-julia/issues/50. That extension should be shipping a full environment instead of relying [this](https://github.com/JuliaEditorSupport/zed-julia/blob/main/src/julia.rs#L22-L45). Related: https://github.com/julia-vscode/LanguageServer.jl/issues/1366.
Are you using Julia normally or via WSL/on a remote machine?
Yes. Effectively, the process that runs all extension code gets terminated, so the original REPL gets completely detached from it. The fact that the error says "**Remote** Extension Host terminated"...
Hm, I feel like that's a bug in the flisp parser and should be a syntax error...