-
Notifications
You must be signed in to change notification settings - Fork 22
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
Incompatibility with VS Code #23
Comments
Yeah... Don't run Infiltrator via inline evaluation; use the REPL only. Nothing to be done about this here, unfortunately. |
Not sure what is meant by using only the REPL? The use case is to insert the infiltrate macro in the code and inspect the variables in this part of the code (referred to as 'inline'?) - how to do that using the REPL? |
And what is the reason for the glitch? Is it a bug in the VS Code extension? |
You need to call the function that contains an |
Thanks, that works fine! I have been rewriting code from Matlab into Julia the last weeks and I like Julia, however, I think the tooling is still missing some core functionalities - such as proper debugging as the most important. The IDE VS Code debugging in Julia is extremely slow and cannot be used, so it would be great to integrate your solution into the IDE (of course, adding breakpoints in the usual way would clearly be preferable) |
Is there a corresponding bug/issue in the VS Code project for this? It's certainly a bug somewhere, and if it's not this project's responsibility then it seems like it needs a ticket over there. |
This is a symptom of julia-vscode/julia-vscode#785, basically. |
I have been using Infiltrator.jl in Juno for a while, but can't seem to get it to work with VS Code. The REPL is very buggy and doesn't stay in the
> debug
environment. I am on Mac OSX 10.13.6, running Julia 1.5.2 on VS Code 1.51.1.The text was updated successfully, but these errors were encountered: