Sebastian Pfitzner

Right, but the normal REPL already uses two different tasks for display and evaluation, so I'm not sure how that's different? We simply add yet another task into the mix....

But we already *are* respecting AST transforms in the REPL.

Not particularly recent, no. Should've been [here](https://github.com/julia-vscode/julia-vscode/blob/master/CHANGELOG.md#1126---2021-02-20) unless I messed up while writing the changelog.

The race condition should still be there; we didn't change anything about this code on the VSCode side.

Yeah, that makes sense. Tricky to fix though because we don't have control over when REPL hooks are added and we need to be careful not to run them twice,...

This also won't fix the whole issue, because IIRC the REPL transforms aren't run for inline evaluation.

Yes, they should. Just need to take care to do everything on the same task, which will require a bit of a refactor.

That's not too surprising, considering that nothing changed in how this is implemented in VS Code.

> At the very least, I think we should require compat entries for every dependency for registered packages. Otherwise the default is no compatibility bounds, which is bound to cause...

I can look into this, but for now I'd recommend turning on the `Scroll Past End` checkbox in the settings, which should give more than enough screen space for inline...