Closed phmarek closed 12 years ago
Hi,
I've tried and I can't reproduce this. What do you mean by 'get a new buffer with Gitv'? gitv doesn't generate many buffers. Mostly it is just a wrapper around fugitive. I seem to remember it being sensitive to the current working directory. Do you change this in any way? Do you have 'autochdir' set? Or maybe an autocmd?
Can you try with a completely empty .vim/ and empty .vimrc, except gitv and fugitive of course. Maybe you have a setting that is causing the problem?
Failing that, can you describe very precisely how I can reproduce the problem and I'll do my best to fix it.
Thanks,
Greg
"get a new buffer with Gitv" means running ":Gitv".
Hmmm ... I can't reproduce that anymore, too. Strange. What could cause a command to be recognized in one buffer, but not in another?
Well, thanks all the same ... I hope that this problem won't surface again.
JFI: the problem was version 13.00 of dbext: http://www.vim.org/scripts/script.php?script_id=356
I use latest version of dbext. also have this problem. This repo is what I use https://github.com/edsono/vim-dbext
When I open a file from a git repository, eg. Ge ^ works as expected.
But if I get a new buffer with Gitv, pressing
<CR>
on a line saysPlease see https://github.com/tpope/vim-fugitive/issues/142 for more details.