Q: how to configure VS Code launch.json & settings.json about ahkpp

[fade2gray]

it look like it does not run properly on my machine...

That's a little vague - just works out-of-the-box for me - what problems are you having?

[PackElend]

cannot debug anything, so I would like to compare settings

[fade2gray]

Never had to create a launch.json or settings.json. What method are you using to launch the debugger?

[PackElend]

when I start debug

call stack is empty

I can tell that the extension is installed

and it calls AutoHotkey

[FuPeiJiang]

use vscode-autohotkey-debug by zero-plusplus

Debugging support for AutoHotkey(includes H) v1 and v2

https://marketplace.visualstudio.com/items?itemName=zero-plusplus.vscode-autohotkey-debug

[fade2gray]

OutputDebug > If the script's process has no debugger, the system debugger displays the string. If the system debugger is not active, this command has no effect.
https://www.autohotkey.com/docs/commands/OutputDebug.htm

How about trying a simple

text = text
MsgBox, % text

[PackElend]

How about trying a simple

text = text
MsgBox, % text

run script works

debug script seems not to work

pressing on restart makes appear the Debugger but MsgBox appears as well, so scrip was not stopped at the breakpoint

[fade2gray]

Not sure what to advise you other than to suggest there could be a conflict with another extension.

Perhaps try disabling all other extensions and just re-enable ahk++, or try the Start Extension Bisect from the same menu.

If there is no obvious conflict, try the debugger as suggested by Mr. Doge above - haven't needed to myself. ¯\(ツ)/¯

[PackElend]

back from vacation, have just tried disabling all other, still the same

---

added https://marketplace.visualstudio.com/items?itemName=zero-plusplus.vscode-autohotkey-debug makes it working but why?

Moreover, I see (now):

This is deprecated, the new recommended way to configure your default shell is by creating a terminal profile in #terminal.integrated.profiles.windows# and setting its profile name as the default in #terminal.integrated.defaultProfile.windows#. This will currently take priority over the new profiles settings but that will change in the future.

[fade2gray]

Maybe this might help - think I remember having to do this myself when I first installed VSCode.

https://stackoverflow.com/questions/67601161/the-new-way-to-configure-default-shell-and-argument-commands-in-vscode

[PackElend]

may I ask what you did in regard to AH?
This refers to PowerShell, CMD. Trying to do the right thing for AH would like trial&error for me.

[fade2gray]

Getting back to this.

"...makes it working but why?". The vscode-autohotkey-debug extension takes precedence over AKK++ inbuilt debugger - I've never had to use the former, so I have no answer.

On inspecting my settings.json, I can see no evidence that I made any changes to it as shown in the answer to the stackoverflow post that I linked to - all I did was just search for the text that in the image that you posted.

I do seem to remember following a series of on-screen prompts to do with the terminal and powershell when I initially installed VSCode, but this would have been before installing AHK++.

If you are only seeing that deprecation warning when you have an ahk script open in the editor - I really don't know why.

It's a shame that @mark-wiemer seems too busy to offer advice at the moment.

[mark-wiemer]

...only 9 months late! Closing this as @PackElend seems to have resolved the issue. Do let me know if there is something else I can help with, but generally your best bet for debug support would be with the debugger suggested in the comments.