if you add an alias to another command, if the alias is listed BEFORE the command, it doesn't work.
currently LoadCommandConfiguration just looks for an EXISTING command name matching this command body.
Would require a two-pass load that "deletes" all the first-pass commands that turns out were aliases.
Work-around: just add in "separate alias" directions that it has to come after the original command.
if you add an alias to another command, if the alias is listed BEFORE the command, it doesn't work.
currently LoadCommandConfiguration just looks for an EXISTING command name matching this command body.
Would require a two-pass load that "deletes" all the first-pass commands that turns out were aliases.
Work-around: just add in "separate alias" directions that it has to come after the original command.