Well, I have now renamed it from BugOrFeature to a less-generic name...

-- GaranceDrosehn - 31 Dec 2003

Reparent it under a "FixedIssues" item. And perhaps rename it, as BugOrFeature^? is horribly generic.

This bug-or-feature was much more of a bug than a feature, and has been fixed at RPI. However, I have also added a /message command at RPI, so you can use '/alias blah /message ...' for what you had used '/alias blah send ...' for.

This was a very good issue to bring up, although I suspect it would be better as a PR (via /submit) than an entry in the Wiki. I'm not sure what to do with this Wiki entry now that the issue is fixed. Rename it? Or steal this Wiki entry for discussing any number of bug-or-feature questions?

-- GaranceDrosehn - 25 Dec 2003

Not random verbs. Just verbs on $command_mode, which is designed to hold that kind of verb anyway. (So it's not as dangerous as letting a user call, say, #3:@rmverb)

-- CoKe - 24 Dec 2003

I expect we could eliminate the bug and still allow for the feature to exist for cases where it is useful (such as send). It seems like a really bad idea to allow users to execute random verbs with whatever arguments they want, even if it's only a small subset of the available verbs.

-- GaranceDrosehn - 24 Dec 2003

-- JeffR - 25 Nov 2003

I had no idea this was possible. Interestingly, it means that:

/alias /gib huh This will never work

Is also valid, if goofy.

-- CoKe - 04 Dec 2003

-- JeffR - 25 Nov 2003 Using /alias, you can alias something to "send" because it lives in $command_mode even though its not a /command.

This can be useful, e.g for bot interaction: /alias stock send cj: stock

But this behavior may also be considered a bug, as it allows direct invocation of something that shouldn't be directly invoked.