Sebastian Pfitzner

Ref https://github.com/JuliaLang/JuliaSyntax.jl/issues/545#issuecomment-2778397133 maybe? Adding a convenience function does seem like a good idea though.

[This is an incorrect warning](https://github.com/julia-vscode/StaticLint.jl/issues/315).

The difficulty here is finding a good heuristic for determining which exact expression to evaluate. Currently we're running the the biggest non-module expression we can find, which, as you said,...

You can execute arbitrary code in the local scope via the Debug Console (which admittedly is not quite as nice as the REPL, but it exists). > If I may...

The simplest implementation of your idea would be "eval the expr that covers all of the line, disregarding trivia". That would however only eval `log` on the first line (because...

We should make it the same size as the normal VS Code UI text, agreed. Until then you can scale your VS Code window, including the table viewer, with Ctrl-+.

> Also, it seems like changing the name "all" to "All threads" (or in fact, anything but "all") means that option gets sorted last in the profile viewer. That's particularly...

So the issue here is that the implicit return statement is attached to the last expression in the function call. This needs to be fixed in JuliaInterpreter or Base: ```...

That works fine for me: 

This was on stable, but there shouldn't be any difference between the two atm. I suspect something else in that file or somewhere in your code either breaks or slows...