Enter in Gblame window fails if dbext is installed #143

Closed
andreasmueller opened this Issue Jan 20, 2012 · 6 comments

Projects

None yet

4 participants

@andreasmueller

Hello Tim,

When I hit enter in the window opened by Gblame, I get the error message

Error detected while processing function 34_BlameJump:
line 22:

E492: Not an editor command: Gblame

After some testing I noticed that the problem disappears if I remove the dbext plugin. I'm not sure if the problem is on the side of vim-fugitive or dbext, but it would be great if both plugins can be used at the same time.

Owner
tpope commented Feb 23, 2012

Works for me. Do you have any unusual configuration options set? I can't conceive of how these two could interfere with each other.

vexxor commented Mar 22, 2012

I can confirm exactly the same thing. I disable dbext, and the problem goes away. I probably have many unusual configuration options set :), but no special ones related to dbext.

As far as I can figure out, the trigger is enabling the plugin. I enable the plugin, go straight to a tracked file, run :GBlame. When I use enter on a line in the blame window I get the same message:

Error detected while processing function 26_BlameJump: line 22: E492: Not an editor command: Gblame

Owner
tpope commented Apr 5, 2012

I tried again and was able to confirm (presumably because this time I did it in a project where rails.vim had configured dbext). I narrowed it down to https://github.com/vim-scripts/dbext.vim/blob/f539f2f9f3b71f77b2cfa8b9743cc626ba00da41/autoload/dbext.vim#L5801-5843. The buffer switch throws fugitive off. I'm doubtful I can do anything on my end. It looks like the buffer switch is only to access buffer local variables, in which case dbext could potentially be changed to use bufsetvar() instead (but I could be wrong). If someone want to contact dbext's maintainer about this, that would be great, as I don't really have the bandwidth right now.

vexxor commented Apr 5, 2012

I have informed dbext's author via email. Tim, thanks for taking the time to look into this.

Great, thanks for tracking this down!

badosu commented Nov 6, 2012

Thank you @vexxor foi pointing this out, I always had the same problem, but was not able to diagnose it.

I'll remember dbext's author of the issue.

@tpope tpope closed this Apr 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment