being able to /alias certain things like /if creates difficult situations that make near impossible to trace

[Sicprofundus]

sorry for the title :p

things like "/if" you can alias to something else --- why you would do that i have no idea, but you can do it.

There were a few (~5) users last year that for some undetermined reason had an alias for /if

/if=(NULL) /mqlog all /if (NULL) /mqlog all

this, to me, looks like an obvious mistake - but the intent is still yet to be determined --- it looks like like it was meant to be a line in a macro, not an actual /alias /if creation.

my thought was there should be a list of things that can't be aliased including but not limited to: /if, /while, /for

Brainiac's suggestion was that better error reporting would be able to solve situations like this should/when/if (lul, /if) they arrive, and then you don't have a hard-coded list of things to maintain/manage.

I failed to open the issue when that conversation was had, so my fault there.

[Sicprofundus]

here is the thread where we finally figured out what was causing it and how to fix it

https://www.redguides.com/community/threads/ka-error.79110/

[Sicprofundus]

here is another example of someone aliasing /echo (for who knows why)

https://www.redguides.com/community/threads/findclicky-mac-by-chatwiththisname.60929/post-549198