As always, feel free to post issues over at the julia-vscode repo and enable crash reporting if possible – it really helps tremendously with providing a stable extension.
The big focus for the next minor release is to get rid of local indexing, which is probably the biggest pain point currently; hopefully the infrastructure work put into the last to releases allows for a speedy release, so stay tuned.
The Debugger change is huge, thanks for this. When I had to debug large files, I often have to siwtch into compiled mode and put tons of breakpoints to go to the nested-function of interest. This is now direct and greatly improve the debugging experience.
Cheers !
Does the tmux thing offer a way on Windows to connect to an external REPL from VSCode or is this a Linux only feature? I have never used tmux but I want to use an external REPL both to restart less often and to use my second screen more effectively.
Ok I tried this, one problem is that the paths don’t work because of unescaped backslashes. When I fixed that, the command ran but I didn’t see any change in VSCode. alt+enter on 1+1 did however print 2 in the REPL.
Not sure, any kind of indication that I’m connected to an external REPL session. If I come to an open VSCode window and I don’t know if there’s already a repl connected, how can I find out?
Fair point. You can check whether the workspace is populated or you can see the module selector in the lower right. Not sure how to make this more obvious without adding another status bar item.
Ok one more question, if I close and reopen VSCode, how do I close the old session in the REPL (or does it close automatically if VSCode exits), so that I can connect to the new window?
Ok thanks I will try it out some more, this is very cool! The terminal vs code vs plot pane placement in VSCode was bugging me for a long time, now I can show those huge dataframes on the other screen
In my personal experience - far from it. I’m especially when I’m editing a module and want to evaluate a new function definition it will often evaluate the entire file.
Another common case is when I am in a test script where the tests are enclosed in @testset ... begin end then executing a line within those with ALT+ENTER will always execute the entire file.
Seems to me this is using only indentation to determine code blocks?