Not to derail either, but is debug mode faster nowadays for package development ? I started julia only a few years back, around 1.5 i think, and my past experience is awful with that. So I’m mostly running → error-ing (a lot) / @info-ing → Revise-ing.
1 Like
I’m afraid nothing has improved on the debugger side. And, if anything my perception is that it got worse with more erratic behavior of the breakpoints (stopping on removed BPs, not stopping on others when the debugging file is modified)
1 Like
This is different from my experience. From my unreliable memory, since 1.5 it has become drastically better. The ability to select which modules to run in compiled mode is newer than 1.5, isn’t it?
I used the debugger successfully today, at least, and it’s okay-ish responsive.
1 Like
Yes, I agree it is. But that is far from being a particular good experience (I use the debugger almost every day).
Support for Positron would be so great! https://youtu.be/8uRcB34Hhsw?si=RNlhc0k2oxvqJLtE
2 Likes
Not only is debugger slow, but the extensions implementation is often broken. Recently it could only @run once per session (hanging afterward). Today, I found that if I tried to use the debug console, Julia crashed immediately.
That one @davidanthoff kindly fixed it about 2 weeks ago.
2 Likes
I was shorter in that message that I should have been. I’m extremely grateful for the tireless and thankless work @davidanthoff and others are doing! My only point was that the bugs aren’t one off, so I only reach for the debugger as a last defense because I don’t trust that it’s rock solid.
2 Likes
With the debugger in Julia it’s like with my old office’s door handle that would, not always, but often enough, give me an electric shock. As a result I was always hesitant to touch it.
11 Likes
Anyone knows of a native good alternative for Android? (Large tablets in mind).
(I’m using code-server which is rather ok, but it lacks a bunch of plugins, as copilot and remote - SSH).
And something that didn’t work ?
I had no idea there was another person in the Julia community who also has a super barebones development and scripting set-up! This is how my spartan Vim session looks this morning:
(Sorry for the tangent!)
6 Likes
What I have found helpful with zed is to add the following block to keymaps.json
{
"context": "Editor && mode == full",
"bindings": {
"cmd-y": ["workspace::SendKeystrokes", "cmd-c ctrl-` cmd-v enter"]
}
}
This allows me to have a Julia session open in the terminal pane and that allows me the select a block of text and press CMD + y to execute that block in the terminal. Poor man’s hack till they get inline REPL bug fixed.
2 Likes
Two things:
First, the debugger part in the VS Code extension went through a major change this summer. I won’t bore you with the details, but those kind of very large changes are rare. It does mean, though, that it is likely some new bugs crept in during that change. My hope is that we can fix the remaining bugs, and then beyond that I don’t see anything with that amount of code churn for the debugger on the roadmap. The big upside of this change in the summer was that the debug adapter can now be used beyond VS Code, and we’ve started to see it utilized in emacs and vim, and in the VS Code extension it now is also available for notebooks and test items.
Second, can you open a bug report about the debug console thing you ran into it? I just tested a basic debug console stuff on my end, and it seemed to work, so we would probably need some more details.
14 Likes
I definitely will! I’m in the midst of a big deliverable so I haven’t managed to narrow to a MWE. The stress might have contributed to my curtness earlier 
1 Like
Let’s hear it for static electricity. Try first contacting the door knob with something metallic. See if that works. 
No, I just did not get a chance to try very much. I didn’t find anything broken.
1 Like
8 posts were split to a new topic: Maintenance of VSCode Julia extension?
Everyone actively engaging with Julia has opinions regarding this.
Instead of biasing towards those eager to write posts on this thread, it would be better to have a quick poll to gauge the Discourse audience. Ideally, the poll should have less than five questions.
Personally, hitching the wagon to VSCode too much doesn’t seem ideal. Julia should learn from the rise of LSP: the important issue is to make a clean API and a decent implementation of this API’s server which can then be adapted to any IDE. There are several facets to this API (and it is essentially a superset of the LSP API).
4 Likes
I tried out Cursor (with great integrated AI code support) and have never looked back. I teach classes of up to 200 and they love it. Very easy to migrate from VSCode. Similar interface, but in some ways simpler, but with additional features. [Only one slight issue… creating a new Jupyter notebook should be one-click and it’s not currently (but I’ll bet they will fix that)]
[NB: to get the best AI helper there is a small monthly subscription fee, but it has the best Julia code/programming support I have seen.]
3 Likes