Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to limit which rubies are run via a file or ENV var #1

Open
soupmatt opened this issue Nov 19, 2011 · 3 comments
Open

Ability to limit which rubies are run via a file or ENV var #1

soupmatt opened this issue Nov 19, 2011 · 3 comments

Comments

@soupmatt
Copy link

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.

@mislav
Copy link
Member

mislav commented Sep 15, 2014

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.

@jasonkarns
Copy link
Member

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).

@thbar
Copy link

thbar commented Apr 28, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants