Update changelog with known issues

changelog.md

@@ -2,12 +2,18 @@
 
 ## 6.4.1 - unreleased 🛠️
 
+### Known issues
+
+-   If your AHK v2 interpreter is not recognized and you try to debug an AHK v2 script, an "AutoHotkey execute bin not found: ..." output log will appear and take focus in the AHK++ (v1) output channel (open issue [#570](https://github.com/mark-wiemer-org/ahkpp/issues/570))
+-   The "Select AHK v2 interpreter" command does not work, instead please try to run (not debug) an AHK v2 script and use the quick pick from the "... does not exist" error message (open issue [#571](https://github.com/mark-wiemer-org/ahkpp/issues/571))
+
+### Fixes
+
 -   Add [troubleshooting guide](docs/Troubleshooting.md)
 -   Fix go to definition in AHK v1 files ([#559](https://github.com/mark-wiemer-org/ahkpp/issues/559))
 -   Remove unnecessary error message "Couldn't resolve AHK v2 interpreter" ([#493](https://github.com/mark-wiemer-org/ahkpp/issues/493))
-    -   This has been moved to a console log visible in the AHK++ (v2) output channel
-    -   A similar error message will still appear when attempting to debug with an unrecognized interpreter path
-    -   See the new [troubleshooting guide](docs/Troubleshooting.md) for details
+    -   This has been moved to a output log visible in the AHK++ (v2) output channel
+    -   A "... does not exist" error message will still appear when trying to run an AHK v2 script with an unrecognized interpreter path
 -   Fix quick pick for "... does not exist" error message on run AHK v2 script ([PR #569](https://github.com/mark-wiemer-org/ahkpp/issues/569))
     > Note: this fix copies your config into your workspace settings. If you don't like this, please manually enter the path via the settings, and don't use the quick pick. Learn more at [PR #569](https://github.com/mark-wiemer-org/ahkpp/issues/569).
 

docs/Troubleshooting.md

@@ -6,7 +6,10 @@ If AHK++ isn't behaving as you expect, here are some things you can try.
 
 For AHK v2, the language server may not behave correctly if it fails to identify a valid path to an interpreter like `AutoHotkey.exe`. The status bar at the bottom left of your IDE should show the current interpreter or an option to "Select AHK v2 Interpreter".
 
-Currently, AHK++ does not support the Windows Store edition of AHK v2, but there are plans to support it by the end of 2024, ref [#496](https://github.com/mark-wiemer-org/ahkpp/issues/496).
+> Currently, the "Select AHK v2 Interpreter" command does not work, ref [#571](https://github.com/mark-wiemer-org/ahkpp/issues/571).
+> To ensure the extension fully recognizes your interpreter, try to run (not debug) an AHK v2 script. If you get a "... does not exist" error message, the corresponding quick pick will work.
+
+> Currently, AHK++ does not support the Windows Store edition of AHK v2, but there are plans to support it by the end of 2024, ref [#496](https://github.com/mark-wiemer-org/ahkpp/issues/496).
 
 Interpreter found:
 

src/debugger/debugDispatcher.ts

@@ -101,6 +101,7 @@ export class DebugDispatcher extends EventEmitter {
         const programName = getFileNameOnly(args.program);
 
         if (!existsSync(runtime)) {
+            // Exact text is referenced in docs, update docs when updating this value
             Out.log(`AutoHotkey execute bin not found: ${runtime}`);
             this.end();
             return;