-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration with code editors. #5
Comments
While the name is new and shiny, it should be noted that the project the code comes from is quite old (see ASTInterpreter2.jl). I know @pfitszeb has Atom IDE (Juno) working well with at least the previous version. Regarding vscode, I don't think there is any progress there yet. |
This repository is still working.
a better API~ I haven writen some wacky codes to implement the debugger: (based on ASTInterpreter2 ) |
@KristofferC is correct: we are watching all of this here with great interest from the VS Code side of things, but currently no one is working on any integration. Hopefully someone will eventually! |
No one? (exactly no one is working the debugger for VS Code) |
Most of the current development effort is going to JuliaInterpreter; be a bit patient, I think we will have something quite interesting fairly soon. |
(If you want to track status, the big push currently is JuliaDebug/JuliaInterpreter.jl#13.) |
The Debugger is awesome, thanks happy to see this coming online again! I would add a +1 for clean integration with Editors please. Should be better than PyCharm ;-) |
Almost all functionality for this is now in JuliaDebug/JuliaInterpreter.jl#126 so people interesting in writing other frontends for a debugger should most likely do it on top of that. |
Specifically, see JuliaInterpreter's |
This looks awesome, was quite happy to see this working as good as it did, considering that the project is quite new.
Are you thinking about integration with code editors (e.g. VS code) or do you know someone who is?
It'd be quite nice to see you joining forces with Julia Editor support !
The text was updated successfully, but these errors were encountered: