Minimally document externall debugging tools

[MariusDrulea]

No description provided.

[davidanthoff]

I'm confused, why does this belong in the VS Code docs? Neither of this is a VS Code extension feature, and there doesn't seem to be anything VS Code specific in these docs? I wouldn't mind pointers to the two packages, but I don't think we should become a place for generic Julia programming advice.

[MariusDrulea]

This is not advice for generic Julia programming. It's about providing users with a decent debugging experience. As I motivated here, all new users use the vscode extension and their first intro into debugging Julia is the julia-vscode documentation. Mentioning Debugger.jl and Infiltrator.jl in vscode docs is a must I think. It's much better than letting the user search the internet and the discourse forums to fix their debugging.
Now I agree with you extensive debugging examples shall be provided by these packages and I have removed the note that visual debugging examples will come in the vscode docs. Although Debugger.jl ships with the vscode extension so maybe...but let's have it like this for now.

[davidanthoff]

So, I really think we should not start to add documentation about things that are unrelated to the VS Code extension to the docs for the VS Code extension. I am not saying that this kind of doc should not exist, but it should be somewhere else. We barely have the person power to keep docs that are focused on the extension up-to-date, if we start to add docs about other packages now that will just get worse.

Also, just for completeness: Debugger.jl does not ship with the extension. The visual UI in the extension and Debugger.jl use the same underlying debugging engine (JuliaInterpreter.jl), but beyond that they are just alternative UIs, one visual one text based.

I think a short sentence at the end of the docs saying "Here are some alternative debugging options" with links would be fine.

[MariusDrulea]

I think a short sentence at the end of the docs saying "Here are some alternative debugging options" with links would be fine.

I think this is way too minimalistic. I would add a brief description for them, just like the one for Infiltrator, plus pro and cons eventually. Remember vscode-docs is the first place all new users learn about debugging in Julia.
For the Debugger.jl pieces of code, let me try to add them to the Debugger.jl itself, once I have some more time.

Question:
So JuliaInterpreter is the one which ships with the extension. Is it possible to configure the Interpreter (the one used by the UI) with something like this?

union!(JuliaInterpreter.compiled_modules, setdiff(Base.loaded_modules_array(), Main))

[MariusDrulea]

I have updated the section to only contain a brief description about each tool + links. I guess it's clear enough from the doc that these tools are not related to the vscode extension itself.

[MariusDrulea]

@davidanthoff gentle reminder