-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Unable to open gems managed by rbenv #43
Comments
That first one looks strange; can you confirm it's as expected? |
Happily. I'm not exactly sure what it's supposed to look like; however, the first directory Heres the output of
As mentioned, the user installation directory doesnt actually exist on my system. Not sure if that's actually an issue. Did some reading and discovered that that directory is for gems install with
|
It seems that actually a bash function in my zshrc that I use to launch vim is causing this issue. Running the vim binary from the command line without using my bash function remedies my problems with vim-bundler. I guess that this function is messing with the working directory for the binary. |
Hey there. I'm reopening this issue as I've uncovered some weirdness happening with macvim. It seems that when I launch macvim from a terminal vim-bundler initializes correctly and I can
I'm totally stumped. I guess my next step is to start throwing in "echo"s into vim-bundler and debug the script. |
That path is a bit too short to actually see any gems. Check |
I'm using vim 7.4, vim-rbenv, and the latest vim-bundler code, and I'm having trouble with :Bopen <GEM_NAME>. :Bundle works for me as expected but :Bopen is returning the error "Gem <GEM_NAME> is in bundle but not installed". Also in my Gemfile.lock all ruby gems are highlighted as not being installed. Heres the output of two commands run from within vim:
which is the exact same output as on my command line shell (zsh). All this seems to point to a gem_path issue. Do you have any tips on how to debug this further? Unfortunately I'm very new to vimscript. Thanks.
The text was updated successfully, but these errors were encountered: