Got me
I just spent a bunch of time with the load groove code and have added the option to load from a specific directory. So, you can now do "groove casio:80sPopIntro" instead of the more verbose "groove casio/80spop:80sPopIntro". But, I didn't look a the alias code.
If memory serves, the idea behind the alias stuff is really just to create an alternate name for an existing groove. The advantage being that it's also a copy. That is because you now have 2 references to the groove info. Well, that's the way it's supposed to work. I will check that again!!
Certainly the docs here need work! I'd rather fix the docs than the code ... less chance of breaking things.
I'd not thought about autoloading grooves at this point. It would be easy enough to fork off, search and load, and then define. Guess I have to ask why and what are the downfalls? One "problem" I see is that if loading the groove involves reading a file (esp. from another directory) you could inadvertently clobber existing groove info which may not be desired.
To be honest, it's a feature I've never used. Could be that it's not that useful and should be dumped???