Merging the alias and utility modules

[sorin-ionescu]

alias does not contain strictly aliases but also functions, and utility does not contain utility functions such as, for example, administrative functions that would create users, directory hierarchies, and copy dot files; instead it contains aliases and alias-like functions. In fact, these two modules used to be a single file that was split for no reason other than that OMZ Robby had a functions.zsh file that at the time I thought should be populated.

There are three options available:

1. Merge alias into utility.
2. Merge utility into alias.
3. Merge alias and utility into a new module.

I'm leaning towards 3 since, again, the code contains neither just aliases nor just functions, but a mix of both. At the moment, I cannot think of a good name.

[ColinHebert]

I'm not sure that's a good idea.

Having that means that functions defined in this module can't have completion at all, because completion must be loaded after the current alias (LS_COLORS).

The big advantage of alias containing only aliases is that we don't have to care about completion at all (aliases are expanded before the completion process).

[sorin-ionescu]

I was thinking of moving the compdef calls into a _foo file, for they are a pain in the rear no matter what.

[ColinHebert]

Well, we should always use _foo files anyway, it's just that writing them is annoying.

It could be a good policy to just say "no calls to compdef allowed (except if the module depends on completion), use completion files instead."