|
|
Post by Stefan on Oct 13, 2022 11:30:04 GMT -5
Why does the FIND command insist that I put the word "user" in quotes?
If I enter FIND USER ALL, I get a "missing FIND search string" error.
The documentation doesn't mention the word USER in relation to FIND and the word is not high-lighted as a FIND argument either.
No big deal, easy to circumvent, but why is USER a reserved term?
If it is legitimate, the high-lighting and relevant documentation should be changed accordingly.
|
|
|
|
Post by George on Oct 21, 2022 14:44:18 GMT -5
Yes, "it was decided that U was an abbreviation for USER". As in RESET USER
That's because I was convinced by someone to add a whole bunch of aliases for various commands and operands, many of them totally obscure. e.g. did you know BR and BRO are aliases for BROWSE? Have you ever in your life used them?
The parse routine handles all the aliases by creating a token for each parsed item. The command routines then only check for the token and not for each of the possible KW aliases.
The parse routine will be left unchanged. I have corrected the operand hi-lighting to at least hi-light the word.
George
|
|
