Skip to content
This repository has been archived by the owner on Apr 24, 2020. It is now read-only.

Fix RVM #1149

Merged
merged 3 commits into from
Feb 9, 2019
Merged

Fix RVM #1149

merged 3 commits into from
Feb 9, 2019

Conversation

dritter
Copy link
Member

@dritter dritter commented Feb 1, 2019

This is a cleaned up Version of #832 .

This reverts commit 643555a.

This does allow rvm to be detected even without using the depreciated
gemset settings.
@dritter dritter mentioned this pull request Feb 1, 2019
@dritter dritter merged commit dcd7718 into Powerlevel9k:master Feb 9, 2019
@dritter
Copy link
Member Author

dritter commented Feb 9, 2019

I don't think this will break anything, so I merged this one. @HaoZeke thanks and have a look at master. ;)

@dritter dritter mentioned this pull request Feb 20, 2019
@csalvato
Copy link

csalvato commented May 4, 2019

I don't believe this fixes the RVM prompt. In my installation, this only shows the ruby version, but not the gemset. In my local repo, I changed this:

prompt_rvm() {
  if [ $commands[rvm-prompt] ]; then
    local version_and_gemset=${$(rvm-prompt v p)/ruby-}

    if [[ -n "$version_and_gemset" ]]; then
      "$1_prompt_segment" "$0" "$2" "240" "$DEFAULT_COLOR" "$version_and_gemset" 'RUBY_ICON'
    fi
  fi
}

to this...

prompt_rvm() {
  if [ $commands[rvm-prompt] ]; then
    local version_and_gemset=${$(rvm-prompt)/ruby-}

    if [[ -n "$version_and_gemset" ]]; then
      "$1_prompt_segment" "$0" "$2" "240" "$DEFAULT_COLOR" "$version_and_gemset" 'RUBY_ICON'
    fi
  fi
}

And it now displays as I want it to:
image

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

Successfully merging this pull request may close these issues.

3 participants