Apparent syntax error parses correctly but causes a hotkey to be ignored
Posted: 12 May 2022, 09:26
[Moderator's note: Topic moved from Bug Reports.]
Using 1.1.34.01 on Windows 10 20H2 64-bit Home Edition, I accidentally left an extraneous > character on a line by itself in my script, and it still parsed successfully, but the hotkey immediately below the line with the > character is ignored. See the minimal reproducible test case below.
Oddly, if I remove the 2 #IfWinActive lines around the first hotkey, the 2nd hotkey is not ignored (and the script still parses correctly).
Using 1.1.34.01 on Windows 10 20H2 64-bit Home Edition, I accidentally left an extraneous > character on a line by itself in my script, and it still parsed successfully, but the hotkey immediately below the line with the > character is ignored. See the minimal reproducible test case below.
Oddly, if I remove the 2 #IfWinActive lines around the first hotkey, the 2nd hotkey is not ignored (and the script still parses correctly).
Code: Select all
#IfWinActive ahk_exe notepad.exe
^n::MsgBox OK
#IfWinActive
>
^z::MsgBox Ctrl-Z pressed