Menu
▾
▴
#10 Fedora /etc/vimrc conflicts with our vim tutorial
Hi there
The instructions for adding cscope support into Vim don't work for me on Fedora Core 5 (Vim 7.0).
It would be great if someone could revise/update the page here and add whatever changes are required for newer versions.
http://cscope.sourceforge.net/cscope_vim_tutorial.html
FWIW I get an error message from Vim when I run do as described:
$ vim -t WriteWhyNotFound
Error detected while processing /home/john/.vim/plugin/cscope_maps.vim:
line 42:
E568: duplicate cscope database not added
Press ENTER or type command to continue
Perhaps cscope support has been pulled into core for Vim 7.0, or something like that. But the "ctrl-\ s" thing doesn't work.
Cheers
JP
Logged In: YES
user_id=27517
Originator: NO
I don't think your conclusion that this failure must have been caused by these instructions being for older versions of Vim is valid. I've just tried them with Vim-7 (up to correction 122) on Cygwin, and they worked out just fine.
That error message you got indicates to me that you probably have two instances of cscope_maps.vim in your ~/.vim/plugin and/or ~/.vimrc. It means that Vim won't add the same cscope database twice, so you probably already have it integrated.
Logged In: YES
user_id=849068
Originator: YES
Turns out that Fedora Core 5 includes some cscope stuff in /etc/vimrc. Which gets loaded somehow.
BUT I'm not getting the "ctrl-\ s" functionality. And I don't immediately see how I can do it. I guess I could chop off the top of that cscope_maps.vim file?
FWIW, I note that on Ubuntu, the /etc/vim/vimrc file does *not* include cscope stuff.
Cheers
JP
Logged In: YES
user_id=849068
Originator: YES
(reopened, hoping for comments on how to fix the "ctrl-\ s" functionality)
Logged In: YES
user_id=27517
Originator: NO
> BUT I'm not getting the "ctrl-\ s" functionality.
Well, that's nothing we can help you with. It works just fine if I follow the instructions on another system.
Fedora put that stuff in their /etc/vimrc --- it's they who have to maintain it. When you tell them, be sure to include more details of *how* it fails: error messages, crash dumps, whatever. Check what the ":map" command shows: are there cscope mappings in there?
And maybe you should try this with a pristine vim (move /etc/vimrc out of the way, or try the -u startup option), too.
Logged In: YES
user_id=827328
Originator: NO
what package is cscope_maps.vim associated with? I just checked both the cscope and vim-enhanced packages for fc6 and neither claims that file in its file list.