When $NOPREFIX is in use, the QB64 keywords do not need the _ prefix (hence the titular metacommand).
However, when using this feature of QB64 language, the VSCode extension help facilities with F1 fail to find the keywords.
Here is an example of use:
Here is what happens when F1 is pressed:
Contrast this with _LIMIT with the _ prefix, and F1 works as intended.
I'm not sure how to fix this, but maybe when the keyword lookups happen if there is no _ prefix we could add one dynamically?
If the extension could use some kind of file detection perhaps looking for a .md file named with a _ as a way to check? If it finds a file when no underscore is used with $NOPREFIX but uses underscore, lookup the _ QB64 word of the command dynamically?
e.g.
$NOPREFIX in use:
User puts cursor on LIMIT presses F1
Extension could check for existing file in documentation path. Nothing found, then try prefixing dynamically with _ to look for _LIMIT.md. If found, show that?
When
$NOPREFIXis in use, the QB64 keywords do not need the_prefix (hence the titular metacommand).However, when using this feature of QB64 language, the VSCode extension help facilities with F1 fail to find the keywords.
Here is an example of use:
Here is what happens when F1 is pressed:
Contrast this with
_LIMITwith the_prefix, and F1 works as intended.I'm not sure how to fix this, but maybe when the keyword lookups happen if there is no
_prefix we could add one dynamically?If the extension could use some kind of file detection perhaps looking for a
.mdfile named with a_as a way to check? If it finds a file when no underscore is used with$NOPREFIXbut uses underscore, lookup the_QB64 word of the command dynamically?e.g.
$NOPREFIXin use:User puts cursor on LIMIT presses F1
Extension could check for existing file in documentation path. Nothing found, then try prefixing dynamically with _ to look for _LIMIT.md. If found, show that?