@swagfag
Thanks. I tried the ahk code. It didn't work for me.
It does open the AutoHotkey Help (as administrator? why? I get the UAC each time), but it doesn't open the desired keyword. It always opens the default "HomePage".

Anyway,

swagfag wrote:this idea already exists and is called Go To Definition, in your editor of choice, that hopefully supports it

I think you are talking about the solution of opening the Documentation in the documentation pages itself. Similar to what I can do already in the white frame of the code above. *

While I'm talking about improving more than that:

Stamimail wrote:I think https://regex101.com/ is a good example to understand the concept of what I'm looking for.
You paste the code (in this case, you paste the regular expression), and then you can get the meaning of each part of the code by hovering the regular expression characters. Tooltips with relevant explanation are displayed.

Stamimail wrote:Instead of opening each link to its help, it will be more convenient to have a tooltip with short explantion (Wikipedia recently has this feature).
or
to make 2 panes/frames.
In one pane you paste the code, and in the other pane you can view the translation/explanation to each character/word according to the location where is the cursor moved with the arrows.

I think it will be either more convenient and will save more time.
____________
* That was what I meant by:

Stamimail wrote:Take the AHK forum for example.
When you paste a code into
a code display
you get links for some words to Help.

One more thing.
This HelpTool should also "translate" the meaning of syntax parts like:
^
+
{Esc}
::
:=
<>
!=
It seems you can't currently do it by the trick above.
How a beginner user can understand the meaning of those syntax parts?! There is no reference (links) to help for those syntax parts.

I'd argue the point that a total beginner unfamiliar with programming in general shouldn't start off learning by parsing scripts token by token. That's what the tutorials are there for, but that's just me.

I could accommodate it to an extent in the script (lacking a full fledged parser, it will be at times inaccurate) though I find little value in having the IDE tell me a plus sign is a plus sign. With regex it might make more sense as they could get a bit cryptic, but built in language operators? It takes 15 min to go over the Operators man page, and that's as much as you're ever gonna need to spend on them.

1. I think it will improve the learning curve for the beginner.
2. It will be better to have "translation" to ^ + ... <> !=, but currently there is no references to ^ + ... <> != so the beginner can't even reach the relevant place in the help ("Sending Keystrokes", "Assignment Operators", "Expression Operators" ...)