Although rvm-configuration-file-name was configured, rvm--rvmrc-locate was not using it. #26
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Although rvm-configuration-file-name was configured, rvm--rvmrc-locate was not using it.
|
@gaizka thanks, this makes perfect sense ;). merged. |
senny
added a commit
that referenced
this pull request
Jul 14, 2012
Although rvm-configuration-file-name was configured, rvm--rvmrc-locate was not using it.
|
You are welcome. Thank YOU for rvm.el, it's really useful!!! -- Gaizka El día 14/07/12 07:01 -0700, Yves Senn escribió:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My .rvmrc is a shell script, pretty complex (depending on $HOSTNAME), so it cannot be parsed by rvm.el.
I created .rvmrc.el with just one line, and customized rvm-configuration-file-name to ".rvmrc.el".
I expected rvm--rvmrc-locate to find this file, but it was always using ".rvmrc".
This should fix it.
Sorry about not providing any tests, but there are no tests for this behaviour and I am not so fluent testing emacs modules to be able to test it.