-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add clarity to dotfile edits #4053
Comments
What do you mean by delineate? Would you expect RVM to print info during installation or include comment whenever dotfile is modified by RVM? |
@pkuczynski something like this: 1873ef2#diff-e2aa477d4d8062608817e3021b4ed39d :) |
Yeah, I asked question before I notice your PR :) |
#4052 adds more clarity to files created by RVM. We could implement the logic of recognizing which shell is installed in the system, but I am not sure if that's worth the effort. Now if you would install new shell after installing RVM, it would work out of the box. Otherwise, user after installing a shell would have to run |
Thanks for all your work to make this acceptably robust! |
Description
The RVM installer edits several dot-files (and creates them, if they do not already exist). It can be confusing for a user to find dot-files in their home directory for shells they have never installed (e.g. .mkshrc, if they are not a mksh user). It can also be hard for a novice user to know which edits to their dot-files were made by what, when, and why.
Possible example of such confusion: #3130
Steps to reproduce
.mkshrc
,.bashrc
,.profile
,.bash_profile
, etc) are created or modified.Expected behavior
RVM should clearly delineate the edits it makes to dot-files.
Actual behavior
RVM is terse. It is hard to be confident whether the file was modified by RVM itself, or did I instead make the edit manually at some point? Why do I even have a
.mkshrc
, given that I don't havemksh
installed? Example, after installing a slightly earlier version of RVM:Environment info
N/A
The text was updated successfully, but these errors were encountered: