Mercurial > vim

comparison runtime/doc/if_cscop.txt @ 2873:eeb1ac4f66d1 v7.3.210

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
updated for version 7.3.210 Problem: Can't always find the file when using cscope. Solution: Add the 'cscoperelative' option. (Raghavendra D Prabhu)
author Bram Moolenaar <bram@vim.org>
date Sun, 12 Jun 2011 20:42:22 +0200
parents fae782ef63dd
children fd09a9c8468e
comparison
equal deleted inserted replaced
2872:3e0a07715023 2873:eeb1ac4f66d1
269 setting 'cst', you will always search your cscope databases as well as your 269 setting 'cst', you will always search your cscope databases as well as your
270 tag files. The default is off. Examples: > 270 tag files. The default is off. Examples: >
271 :set cst 271 :set cst
272 :set nocst 272 :set nocst
273 < 273 <
274 *cscoperelative* *csre*
275 If 'cscoperelative' set, then in absence of a prefix given to cscope (prefx
276 is the argument to -P option of cscope), basename of cscope.out location
277 (usually the project root directory) will be used as the prefix to construt
278 absolute path.The default is off. Note: This option is only effective when
279 cscope (cscopeprg) is initialized without a prefix path (-P). Examples: >
280 :set csre
281 :set nocsre
282 <
274 *cscopetagorder* *csto* 283 *cscopetagorder* *csto*
275 The value of 'csto' determines the order in which |:cstag| performs a search. 284 The value of 'csto' determines the order in which |:cstag| performs a search.
276 If 'csto' is set to zero, cscope database(s) are searched first, followed 285 If 'csto' is set to zero, cscope database(s) are searched first, followed
277 by tag file(s) if cscope did not return any matches. If 'csto' is set to 286 by tag file(s) if cscope did not return any matches. If 'csto' is set to
278 one, tag file(s) are searched before cscope database(s). The default is zero. 287 one, tag file(s) are searched before cscope database(s). The default is zero.