Skip to content
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

Debug ignoring specified runtime path? #305

Open
SAbboushi opened this issue Dec 1, 2023 · 2 comments
Open

Debug ignoring specified runtime path? #305

SAbboushi opened this issue Dec 1, 2023 · 2 comments

Comments

@SAbboushi
Copy link

Hi-
I'm now upgrading from AHKv2 alpha and your extension to current versions. Have been unable to get your debugger adapter to work again after the upgrades. NOTE: I am running portable versions of vscode and autohotkey v2.

My launch settings are in my workspace's .code-workspace file (in my case, AHKv2.code-workspace):
image

But when I start debug, I get this error:
image

We've spoken earlier about your extension supporting the settings in .code-workspace file:
#62 (comment)
#117 (comment)

I'm wondering whether I have misconfigured something or whether there is some reason the extension is not recognizing/honoring the runtime setting in .code-workspace file? It's been a couple of years since I was actively programming/debugging my AHK scripts, so I may be doing something silly...?

@SAbboushi
Copy link
Author

SAbboushi commented Dec 1, 2023

Note: when I click on "Open 'launch.json'" button in the error message window, vscode opens my AHKv2.code-workspace file

@zero-plusplus
Copy link
Owner

zero-plusplus commented Dec 2, 2023

I have checked that the runtime attribute works in two different ways: when set to launch in code-workspace and in .vscode/launch.json in the workspace folder, but no issue occurred.

The error shows that the default path is set for runtime, so it does not appear to be a path specification error.

At the moment I can only advise you to make sure that you have specified the debugging configuration correctly.


I decided to improve the messages so that when an error occurs, it is possible to determine which debugging configuration is specified. You can track it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants