Скачать или смотреть How to Fix VSCode Using the Wrong Ruby Version with rbenv on Ubuntu

Struggling with VSCode using an outdated Ruby version? Discover how to solve this issue by configuring rbenv correctly on Ubuntu.
---
This video is based on the question https://stackoverflow.com/q/73897013/ asked by the user 'Michael Moran' ( https://stackoverflow.com/u/10878648/ ) and on the answer https://stackoverflow.com/a/77430747/ provided by the user 'Kalsan' ( https://stackoverflow.com/u/7009068/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: VSCode uses wrong ruby version

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Fixing VSCode: Incorrect Ruby Version Issue on Ubuntu

If you're developing on Ubuntu and using Visual Studio Code (VSCode), you might encounter a frustrating problem: VSCode uses the wrong Ruby version. Despite having the correct version installed via rbenv, the editor may still default to an older version. This guide will guide you through understanding and resolving this common issue.

The Problem: What’s Going Wrong?

When running code inside VSCode, you might see errors similar to these:

rbenv: version '2.5.1' is not installed (set by RBENV_VERSION environment variable)

command /home/{username}/.rbenv/shims/rubocop returns empty output! please check configuration.

Reason for the Errors

In this particular situation, your project is configured to use Ruby version 2.7.6, but for some reason, VSCode is trying to access version 2.5.1, which you have since removed. Here are some observations that could lead to such a discrepancy:

Running rbenv local and rbenv global correctly shows 2.7.6.

The .ruby-version file in your project specifies 2.7.6.

In a regular terminal, executing echo $RBENV_VERSION might show nothing, while in VSCode’s terminal it shows 2.5.1.

So, why is there a difference?

Solution: Setting Up rbenv Properly in VSCode

The primary issue is likely due to how your shell environment is configured. Let's tackle it step-by-step:

1. Run rbenv Init Command

You first need to initialize rbenv in your shell. This involves adding the rbenv initialization command to your shell configuration file.

Open a terminal window on your Ubuntu machine.

Type the following command:

[[See Video to Reveal this Text or Code Snippet]]

After running this command, it will give you instructions to add a line of code into your shell configuration file, such as .bashrc or .bash_profile.

2. Modifying Your Shell Configuration File

Depending on your shell, follow these steps:

If you're using bash, run:

[[See Video to Reveal this Text or Code Snippet]]

For zsh, you would modify .zshrc instead:

[[See Video to Reveal this Text or Code Snippet]]

3. Restart the Terminal

Once you've made these changes, you need to restart your terminal for them to take effect:

Close your current terminal window.

Open a new terminal window.

4. Validate the Configuration

Test that your changes worked successfully by running:

[[See Video to Reveal this Text or Code Snippet]]

You should see the correct version of Ruby (i.e., 2.7.6). Additionally, try running rubocop in both the terminal and within VSCode to confirm the configuration is functioning correctly.

Conclusion

By ensuring that your shell environment is correctly set up with rbenv, you can get VSCode to use the correct Ruby version. This solution not only resolves the errors you've encountered but also streamlines your development process by ensuring consistency across environments.

Don’t forget, if any further issues arise, checking your .ruby-version file and ensuring extensions in VSCode are properly configured can help pinpoint the problem. Happy coding!