Re: cscope & gvim (was: Re: (1) cscope & gvim; (2) ctags & C++/STL)

From: Fred Ma (fma_at_doe.carleton.ca)
Date: 01/30/04 

Date: 30 Jan 2004 13:08:51 GMT

Hans-Bernhard Broeker wrote:
>
> Please try to avoid posting two rather unrelated questions in a single
> article.

Sorry. cscope is separate from ctags, despite their similarities
from within gvim.

> I rather strongly suspect the problem is with that vim plugin for
> cscope, which is maintained by the vim people. But you may want to
> check the results generated by cscope itself, too, to see if there's
> anything that sticks out. Run cscope on your existing cscope.out
> file, like vim does it:
>
> cscope -ld
>
> from the directory cscope.out is in, and type the line '0foo' to
> search for all occurances of symbol 'foo'. Include the output of this
> in any report you make to the vim guys, or here. It's extremely hard
> to debug such problems without a complete, reproducable example or at
> least some hard data to inspect.

Yes, actually I mentioned that cscope worked fine when
used outside of gvim. It will take some time to come up
with a code case, since I don't want to send out large
chunks of my own code at this time (I don't have lots
of different code). As a first step, I was checking
to see if my experience with the gvim plugin was an isolated
one. If so, then it was time to find a suitable chunk of
code that reproduces the problem, though that will be
sleighted somewhat into the future, after a deadline I'm
working toward at the moment.

> It can't be in the cscope man page --- the VIM interface is none of
> cscope's business.

Got it. I should have emphasized that the problem was
with the gvim plugin.

Fred 

-- 
Fred Ma
Dept. of Electronics, Carleton University
1125 Colonel By Drive, Ottawa, Ontario
Canada, K1S 5B6

Relevant Pages

  • (1) cscope & gvim; (2) ctags & C++/STL
    ... cscope choosese wrong match from list ... to the vim group comp.editors, ... under the cursor. ... posting about how to get it to tag local variables, ...
    (comp.unix.programmer)
  • Re: Linux user interested in *BSD
    ... vim is a very good example. ... On another newsgroup people ignored the mere existence of cscope. ... >> Hence hardwiring a dependence on cscope in vim is not necessary. ... >> support, ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Linux user interested in *BSD
    ... >> This is a typical example of the bloatware that the ports maintainers ... In this case vim is an ... >> editor which is used by programmers and other people, while cscope is a ... > and it won't install cscope by default from port. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: should I use cscope or ctags?
    ... I am using cscope and ctags in Vim. ... You can chase declaration of a function in *.h by [i ...
    (comp.editors)
  • Re: Read the VI source code?
    ... Vim to examine the sources. ... like ctags, ... , or cscope ... I personally prefer the Lucent cscope (it is what we used in the ...
    (comp.editors)