"AutoHotkey interpreter not found" message when debugging something unrelated to AHK

[RandScullard]

Description

Since AHK++ v6 was installed, every time I start debugging a C# project in VS Code, I get this notification popup:

AutoHotkey interpreter not found, check settings: AHK++.v2.file.interpreterPath

This is in a workspace with no AutoHotkey files, totally unrelated to AutoHotkey. I don't have AHK v2 installed - I am still on v1 and don't plan to upgrade anytime soon.

Reproduction steps

Steps to reproduce the behavior:

1. Open a C# workspace
2. Start debugging

Expected behavior

Expected not to get any notifications related to AHK++. I think the AHK++ extension should check whether you are debugging an AutoHotkey script before it looks for the AHK interpreter. I couldn't find anything in the AHK++ docs about support for v1, but it seems to still be supported, so it's not clear if having v2 installed is a requirement.

[mark-wiemer]

Hmm, sorry about that. How exactly are you starting debugging--via keybinding, command palette, GUI, something else? In the short term, you can disable AHK++ for the C# workspace so that it doesn't interfere.

I'll put this near the top of the backlog :)

[RandScullard]

It happens whether I start debugging via a keybinding or the command palette. However, I just noticed that it only happens the first time I start debugging after loading a particular workspace. So I can go in and out of the debugger without additional popups appearing. Which is good - this is only a minor annoyance.

[RobbyMeeker]

Yeah same issue. It also happens even without debugging anything. I get the error message on every startup. v2 is not installed, only v1.

[Identifier]

Same here. Have uninstalled this extension and switched to one of the other AutoHotkey extensions until this is fixed.

[CatBraaain]

after a patience, finally I installed ahk2 just to prevent the message

[mark-wiemer]

Thanks for the feedback and sorry for the inconvenience. I should have a fix for this published next week.

[mastrodaro]

I am not using v2, the message about interpreter appear and "Go to definition" stopped working:

I get this extension updated yesterday and can't use it since then.

[mark-wiemer]

Hi @mastrodaro, please open a new issue. And please try downgrading back to 6.3.0 to see if that mitigates the issue: