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

.ruby-version is not empty, moving aside to preserve. #3678

Open
philipjabenton opened this issue May 12, 2016 · 2 comments
Open

.ruby-version is not empty, moving aside to preserve. #3678

philipjabenton opened this issue May 12, 2016 · 2 comments

Comments

@philipjabenton
Copy link

I am using the latest Stable version 1.27 and have added a .ruby-version & .ruby-gemset file to my project.

When I cd into my project I receive this message:

.ruby-version is not empty, moving aside to preserve.
.ruby-gemset is not empty, moving aside to preserve.

And a timestamped new version of each file is created.

Is this a bug? If not how can I stop this happening?

@sjayanna
Copy link

sjayanna commented Jun 30, 2016

@philipbenton Just run rvm get head at the terminal and that should fix this issue.

@robingram
Copy link

Is this old issue still a problem? Every time I restart VSCode I get multiple timestamped .ruby-version and .ruby-gemset files created that are identical to the originals.

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

3 participants