Open soupmatt opened 12 years ago
Not a bad idea. Sometimes I wish that as well.
I'm not decided whether it should be an environment variable or a list passed by argument.
I can see the arg and env var both being useful. For typical one-time usage, the arg list makes the most sense. However, I could see a particular setup wherein a single ruby version is "special" for some reason, and is generally excluded from any -each command. In that case, having the versions specified in a long-lived env var would make sense.
I would expect the arglist form to be recommended (and more common).
Looking for the equivalent of rvm do
today, I found this discussion.
The community plugin at https://github.com/johann-koebbe/rbenv-iterate seems to be an interesting option.
It would be slick if we could put a .rbenv-each in each project to limit which rubies get run when using rbenv-each, or specify that in an env var.