We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using code that previously worked, with VS Code 1.68.0 and extension 1.11.0, grouping of debug messages is not working for me.
On my main system, I tried rolling back to a few previous versions of the extension, with no luck.
I also tested with the following on a new Windows 11 install, with fresh install of VS Code, vscode-autohotkey-debug and vscode-autohotkey2-lsp.
; @Debug-Output:start => Started ; @Debug-Output => Test message ; @Debug-Output:end MsgBox
The result was
Started Test message
The directive is clearly being processed, but there is no grouping. Am I missing something, or is it a bug?
The text was updated successfully, but these errors were encountered:
Thanks for the report. I confirmed that this bug has been present since 1.10.0.
I have added this issue to the next version of the plan.
This may take some time as I am currently working on another project in parallel.
Sorry, something went wrong.
Fix: #220
a6c6016
Grouping of messages using Debug Directive is not working, such as `; @Debug-Output:start`, `; @Debug-Output:end`
Merge branch '#220' into develop
284752f
No branches or pull requests
Using code that previously worked, with VS Code 1.68.0 and extension 1.11.0, grouping of debug messages is not working for me.
On my main system, I tried rolling back to a few previous versions of the extension, with no luck.
I also tested with the following on a new Windows 11 install, with fresh install of VS Code, vscode-autohotkey-debug and vscode-autohotkey2-lsp.
The result was
The directive is clearly being processed, but there is no grouping. Am I missing something, or is it a bug?
The text was updated successfully, but these errors were encountered: