Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1582 - VIM not build with --enable-cscope option

Attached to Project: Arch Linux
Opened by Casey McGinty (cmcginty) - Tuesday, 05 October 2004, 04:52 GMT
Last edited by Judd Vinet (judd) - Wednesday, 06 October 2004, 18:32 GMT
Task Type Feature Request
Category Packages: Current
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

The Vim package in base does is not built with --enable-cscope option. Cscope allows for C/C++ tagging similiar to ctags but adds more enhanced search capabilities. Cscope is already a package in Arch so I think Vim should be built to support it.
This task depends upon

Closed by  Judd Vinet (judd)
Wednesday, 02 February 2005, 17:37 GMT
Reason for closing:  Implemented
Comment by Damir Perisa (damir.perisa) - Monday, 31 January 2005, 13:31 GMT
cscope is in extra::devel
vim is in current

that's the reason for not using --enable-cscope, right?
Comment by Judd Vinet (judd) - Monday, 31 January 2005, 20:14 GMT
Having trouble getting it to work. I build with cscope enabled, generated the cscope data file. cscope itself works fine, but the "CTRL-\ s" key combo cited in the cscope/vim tutorial does not do anything.

Am I missing something?
Comment by Casey McGinty (cmcginty) - Tuesday, 01 February 2005, 02:54 GMT
The point is that VIM should be enabled to use CScope. If you enable it, and don't have CScope, it acts exactly the same way as it normally should. The only thing this compile switch gives you is the ability for Vim to read a CScope database file, and have default key bindings. So people who want to take advantage of the feature can. By not building with --enable-cscope Vim will not know how to use the CScope database so nobody can use it, even if they want to.

Once you have CScope support enabled in VIM:
1. cd to your root source directory and run 'cscope -Rb'
2. run vi
3. connect Vi to the CScope database ':cs add cscope.out'
4. open a project file in Vi, put the curser over tag and type '<CTL>-\' (control-backslash together) and then 's'
5. you can also use CScope like the normal tag command command <CTL>-] (control-close brace together) and <CTL>-t (control-t together)
Comment by Casey McGinty (cmcginty) - Tuesday, 01 February 2005, 02:56 GMT
FlySpray messed up my comment. The commands are...

"CTL-\" then s
"CTL-]"
"CTL-t"
Comment by Casey McGinty (cmcginty) - Tuesday, 01 February 2005, 02:57 GMT
"CTL-\" then s

"CTL-]"

"CTL-t"
Comment by Judd Vinet (judd) - Tuesday, 01 February 2005, 18:52 GMT
Hmmm, I must be screwing up somewhere.

Built vim fine with --enable-scope, generated cscope.out.

":cs add cscope.out" worked without error.

But "CTL-backslash s" does nothing.
Comment by Casey McGinty (cmcginty) - Wednesday, 02 February 2005, 02:28 GMT
I'm not sure what you are doing wrong. Try to follow this tutorial very closely if it still does not work.

http://cscope.sourceforge.net/cscope_vim_tutorial.html
Comment by Judd Vinet (judd) - Wednesday, 02 February 2005, 02:49 GMT
Well, let's start with the vim package. Can you see if this one works with cscope or not?

# pacman -U ftp://dragon.archlinux.org/current/os/i686/vim-6.3-4.pkg.tar.gz

Comment by Casey McGinty (cmcginty) - Wednesday, 02 February 2005, 03:12 GMT
Works fine.
Comment by Judd Vinet (judd) - Wednesday, 02 February 2005, 17:36 GMT
Okay, then my problem is just incompetency then. :)

I'll commit the new VIM package.

Loading...