You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some limitations when running a selection or block of code with Alt+Enter; macros like @__FILE__ don't work and if there is an exception thrown, no information about where the error location within the file is, will be show. That's because the corresponding text is only copy/pasted into the Terminus instance. The VS Code extension has multiple ways of running a code block, described in https://www.julia-vscode.org/docs/dev/userguide/runningcode/, and some of them don't have these limitations. I should figure out how they do it and see whether it's possible to implement here too.
The text was updated successfully, but these errors were encountered:
From a quick look it seems VS Code uses a module VSCodeServer (included in the VS Code Julia extension) for communication with the REPL, but it is no published package, uses local dependencies and has lots of VS Code specific implementations. There seem to be quite a lot of code and non-trivial "hacks" for the REPL module. This "backend" apparently also handles things like inline results and a built-in plot pane. Due to this I don't think it's possible to reuse it here without a huge amount of adjustments and work. Therefore I guess the benefit wouldn't be worth working on this right now.
There are some limitations when running a selection or block of code with Alt+Enter; macros like
@__FILE__
don't work and if there is an exception thrown, no information about where the error location within the file is, will be show. That's because the corresponding text is only copy/pasted into the Terminus instance. The VS Code extension has multiple ways of running a code block, described in https://www.julia-vscode.org/docs/dev/userguide/runningcode/, and some of them don't have these limitations. I should figure out how they do it and see whether it's possible to implement here too.The text was updated successfully, but these errors were encountered: