It's not just "technically not a bug"; it's intended behaviour. I will attempt to explain.
doc wrote:
However, if a hotkey needs to execute only a single line, that line can be listed to the right of the double-colon. In other words, the return is implicit
In other words, these are
exactly equivalent:
Code:
^a::MsgBox
Code:
^a::
MsgBox
return
There is no distinction between "single-line" and "multi-line" hotkeys.
A label points at the next line of executable code; that is, a command, assignment or expression. ^a:: and ::hotstring:: are also labels, not executable code. So when you write...
Code:
label1:
label2:
^a::
MsgBox
... all three labels point at MsgBox.
doc wrote:
After the script has been loaded, it begins executing at the top line, continuing until a Return, Exit, hotkey/hotstring label, or the physical end of the script is encountered (whichever comes first).
If there is a line between the label and hotkey, that line is what the label points at. In that case, the label is inside the auto-execute section, which ends the same way as if the label wasn't there:
Code:
<auto-execute section>
label:
<any command or expression> ; label points at this line.
^a:: ; This ends the auto-execute section.
MsgBox
On the other hand, if there is no executable line between the label and the hotkey, the label points at the first line of the hotkey:
Code:
<auto-execute section>
label:
^a:: ; This ends the auto-execute section,
MsgBox ; but label still points at this line.
Furthermore, since the auto-execute section has already ended, subsequent hotkeys do not have this behaviour. In the following example, execution will always fall through the ^b hotkey label:
Code:
goto label
^a:: ; This ends the auto-execute section.
label:
x=y
^b::
MsgBox % x
ExitApp
Login
Register
FAQ
Search
