Recent changes does not return all gems anymore

[khelben]

I've found out that your latest changes introduced a bug where calling e.g.

:Bedit rails

returned a message saying it couldnot find the gem 'rails'

When I reverted to commit ecfb0a27a6ad125d2057cb162e9b01ac6b5e9e84 I can succesfully do the same command.

Steps to reproduce:

• just generate a simple rails app

rails new bundler_test

• fire up vi with the vim-bundler plugin enabled
• Try to open the rails gem

:Bedit rails

When I execute the following in vim

:echo bundler#buffer().project().gems()

the following is returned when I use vim-bundler HEAD

{'action_mailer': '/Users/cvp/.rbenv/versions/fast-require/lib/ruby/gems/1.9.1/gems/actionmailer-3.2.9'}

You can find my .vim dir here: https://github.com/khelben/vimfiles It is just pathogen controlled set of vim plugins

[tpope]

Thanks. This was pretty sloppy on my part.

[khelben]

awesome!

thx for the quick fix.

[nashbridges]

After upgrading to 2.0, I've got pg and nokogiri red highlighted in my Gemfile.lock. :Bopen pg reports that gem is in a bundle but wasn't installed. However $bundle show pg returns a path to installed gem.

What debug information should I provide?

[tpope]

What is the path to the installed gem, and how does it noticably differ from gems it was able to find?

[nashbridges]

damn, I had to figure it out myself. I believe the problem is in win32 version of gems:

...
nokogiri (1.5.2)
nokogiri (1.5.2-x86-mingw32)
...
pg (0.14.1)
pg (0.14.1-x86-mingw32)

[tpope]

Sorry you had to do your own debugging. :violin:

Digging around a bit, I found one occurrence of this on Linux as well. Latest should fix it.

[nashbridges]

Ah, I had to be more specific, I'm not a MS user, but we still have one in our team. Seems the last commit didn't change anything, I've tested it on Mac OS 10.7, Ubuntu 12.04. But! At least I could narrow this problem down, see https://gist.github.com/nashbridges/5357964. Both pgs are red, and :Bopen pg is failing.

[tpope]

Assuming this is still reproducible, a path to the installed gem would be helpful in resolving.