- Thread Starter
- #26
Hi all, I thought I'd bring this one up again as I'm struggling a bit and I've not been able to find help elsewhere.
Basically I've really taken to cscope and ctags, but I've not been able to get any confirmation on nvi's cscope integration capabilities.
Using
will immediately open up the first result it finds without prompt. This is undesirable behaviour because it's usually the wrong one.
Looking at the usage:
Does anybody have any ideas about this? I've tried emailing the nvi maintainer but he's not very active and isn't sure about this. On the off-chance they were into vi, I emailed the cscope maintainers, but they didn't know either. I've posted to the hackers mailing list but haven't got a response yet.
Could it be that nvi isn't used very much to actually develop with? This seems like a very limiting bug(?) - you could get around it with just launching cscope from a command line, but you lose your tag stack, which is a very nifty thing indeed.
Confused!
Basically I've really taken to cscope and ctags, but I've not been able to get any confirmation on nvi's cscope integration capabilities.
Using
Code:
:cs find s <symbol>
Looking at the usage:
To me, this suggests that it should take you into interactive mode (find ALL, find FILES) as it does expect more than one result, so it should not be opening up the first thing it finds. At least, that's what I think.+=+=+=+=+=+=+=+
Command: find (Query the databases for a pattern)
Usage: find c|d|e|f|g|i|s|t buffer|pattern
c: find callers of name
d: find all function calls made from name
e: find pattern
f: find files with name as substring
g: find definition of name
i: find files #including name
s: find all uses of name
t: find assignments to name
Does anybody have any ideas about this? I've tried emailing the nvi maintainer but he's not very active and isn't sure about this. On the off-chance they were into vi, I emailed the cscope maintainers, but they didn't know either. I've posted to the hackers mailing list but haven't got a response yet.
Could it be that nvi isn't used very much to actually develop with? This seems like a very limiting bug(?) - you could get around it with just launching cscope from a command line, but you lose your tag stack, which is a very nifty thing indeed.
Confused!