You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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.
The text was updated successfully, but these errors were encountered: