From 9cc3342e4085d645484ce373496d1391e5756da1 Mon Sep 17 00:00:00 2001 From: Nathan Boyer <65452054+nathanrboyer@users.noreply.github.com> Date: Wed, 15 Jan 2025 12:14:22 -0500 Subject: [PATCH] Add more information on VSCode debugger interpreted modules --- writing/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/writing/index.md b/writing/index.md index 0c374ca..88cbfbf 100644 --- a/writing/index.md +++ b/writing/index.md @@ -737,7 +737,8 @@ Using the toolbar at the top of the editor, you can then _continue_, _step over_ The debugger will open a pane showing information about the code such as local variables inside of the current function, their current values and the full call stack. The debugger can be [sped up](https://www.julia-vscode.org/docs/dev/userguide/debugging/#Settings-to-speed-up-the-debugger) by selectively compiling modules that you will not need to step into via the `+` symbol at the bottom of the debugging pane. -It is often easiest to start by adding `ALL_MODULES_EXCEPT_MAIN` to the compiled list, and then selectively remove the modules you need to have interpreted. +It is often easiest to start by adding `ALL_MODULES_EXCEPT_MAIN` to the compiled list, and then selectively remove the modules you need to have interpreted +by typing their name into the same `+` menu but with a `-` sign in front e.g. `-MyModule`. }