Parser stops working on AHK v1.1 files

[Seraangel]

Description

Parser stops working, on plugin page I get this error (screenshot). I get no outlines anymore and functions jumping doesn't also work anymore.

I'm using newst VSC version, with plugin version from 2023-8-12, 15:33:40.

Plugin > Runtime:

Reproduction steps

Steps to reproduce the behavior:

Open ahk v1.1 file. CTRL on a function. Look on outline.

Expected behavior

Working of advertised features ;-)

[mark-wiemer]

Are you sure this is v1.1? It says "onLanguage:ahk2". Are you able to translate that language (German?) for me? Humans are still better than machines at translation 😄

I'm also not sure how to find this "Plugin > Runtime" screen you mention :/

[Seraangel]

Well I'm sure, because I have only installed ahk v1.1.x on my system and write code for this in vsc.

With the last update ahk v2 support was added and I think I have the problems since then.

and for translation

[Seraangel]

I think this log might help.

2023-08-15 10:59:04.926 [info] ExtensionService#_doActivateExtension vscode.microsoft-authentication, startup: false, activationEvent: 'onAuthenticationRequest:microsoft' 2023-08-15 10:59:06.025 [error] TypeError: Cannot read properties of undefined (reading 'document') at r.value (c:\Users\user\.vscode\extensions\mark-wiemer.vscode-autohotkey-plus-plus-5.0.2\out\extension.js:70:89) at f.w (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1902) at f.x (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1972) at fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2188) at r.value (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:15496) at f.w (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1902) at fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2119) at c.acceptDocumentsAndEditorsDelta (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:104:12570) at c.$acceptDocumentsAndEditorsDelta (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:104:10941) at t.N (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:114:7983) at t.M (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:114:7749) at t.H (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:114:6830) at t.G (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:114:5906) at r.value (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:114:4736) at f.w (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1902) at fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2119) at y.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:79:13931) at r.value (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:130:30355) at f.w (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1902) at fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2119) at y.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:79:13931) at MessagePortMain. (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:130:28635) at MessagePortMain.emit (node:events:513:28) at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:367)

[mark-wiemer]

Ah, should have a fix open soon, thanks for the log :)