Zugg Software :: View topic - Feature Request: aliases with multiple action names

Newbie Joined: 22 Dec 2008 Posts: 5

I really wish I didn't have to make multiple aliases to cover my bases.

For instance, when I am in the heat of battle, I don't know what combination of characters I'll type to flee.

I might type: flee, fle, or fl.

Rather than train my brain and fingers to only use one, I've created multiple aliases to perform the same sets of commands. What would be awesome would be something like:

#alias {flee, fle, fl} {...actions...}

Magician Joined: 28 Jan 2007 Posts: 430

You can use Oninput trigger instead of Alias in that case, imo.

For example,

Oninput trigger with a regex pattern of

Posted: Mon Dec 22, 2008 3:21 am

#oninput {^fle?e?$} {stuff} "" {regex}

If you don't understand the pattern, have a look at some regex cheat sheets.

EDIT: Damn you, prog :(

Newbie Joined: 22 Dec 2008 Posts: 5

Okay, that does sound good. It will work perfectly.

Of course, now I have to ask: why do we still have aliases? We could use both simple and complex oninput triggers for everything.

Posted: Mon Dec 22, 2008 4:07 am

The chief reason that aliases still exist, I think, is that they came first, and removing them when oninput triggers were added would've broken everyone's aliases. The second reason is probably that people find aliases slightly easier to understand. Finally, aliases are simpler than oninput triggers in some respects - they automatically capture their parameters in a few useful ways (both %1 and %-1, for example) and they can be set to automatically append arguments you haven't explicitly mentioned, as well. You're right that input triggers would work just as well, but they're uglier.