As a vimer, how could I disable cscope jump to the first error in quickfix list when search? Because it is not the case I want. I want to select it by myself.
I search everywhere, but until now there is not a satisfactory answer.
Asked
Active
Viewed 1,398 times
3
-
What do you mean by "m"? – romainl Sep 04 '12 at 10:08
-
A "vimer"? What's a "vimer"? I use Vim all day long but I'm a vim-user. – the Tin Man Oct 03 '12 at 21:23
-
I'm not sure why this was closed. I'd like to know how to do this too. So far my research indicates that it's not possible, however. – Jim Stewart Mar 17 '13 at 06:10
-
hi, Jim. I have solved at the bottom. you could do it as what I pointed – harris Apr 21 '13 at 13:52
2 Answers
2
http://vim.1045645.n5.nabble.com/Re-Cscope-quickfix-not-jump-to-first-error-td1193959.html
while at lase i merged the if_cscope_bang.patch and it's OK now.
when complie the vim
also help me about my multi-byte support problem
0
Do you use cscope-specific :cs find foo or do you merge cscope with ctags and use :cstag foo?
Anyway, the default behavior is to not use the quickfix at all: both commands open a special window with a list of matches, even if there's only one match, and no jump is performed.
Check the value of cscopequickfix and read the associated doc :help cscopequickfix.
romainl
- 186,200
- 21
- 280
- 313
-
well,it's right. the value of cscopequickfix sets as follow: set cscopequickfix=s-,c-,d-,i-,t-,e- . with the setting,is there any way to solve the default jump problem. – harris Sep 05 '12 at 02:22
-
It doesn't seem to be configurable. There are ways, in other contexts, to use the quickfix without jumping to the first error: `:make!` or `vimgrep /foo/j *` but I don't know of a way to do that here or of a global setting. Sorry. If you don't like that behavior, you should revert back to the original. – romainl Sep 05 '12 at 04:58