David Anthoff

No, we'll need to find a different solution here in general. We hope to statically compile the LS at some point, and then we won't be able to use anything...

I still want to enable this eventually, so reopening. I am very (!) slowly reworking how we deal with projects, and eventually environments, and when I get to reworking that,...

Probably not easy to fix, a quick look didn't reveal an easy way to figure out whether sigint handling is currently disabled...

My understanding is that `disable_sigint` essentially flips some global flag. If we could eval what the state of that is, we could pause throwing `InterruptExceptions`, exactly like base is doing....

My best guess is that there is a generic VS Code setting for this. I think the default at the moment is that the formatter is only ever run on...

I think we'll have to do something like [here](https://github.com/julia-vscode/julia-vscode/blob/929da90e89c98ce93b3f0d3cde6100585e1dde63/scripts/packages/VSCodeServer/src/eval.jl#L54). But that requires first that we run the actual evaluated code in a different task, not the task that also processes...

This might in general also work better if we were to use the new custom terminal profile for our REPL starting story. But that first requires us to enable support...

Yeah, I think if we enable multiple REPLs, we should make it hard ;) Or at least such that one _really_ must want to leave the one-REPL situation.

One problem is that the location where Julia versions are installed by default has changed at least twice since 1.0.0 was released, so we will need some kind of branching...

Hm, works just fine for me...