Mercurial > vim
annotate runtime/doc/tagsrch.txt @ 13963:1174611ad715 v8.1.0000
Vim 8.1 release
commit https://github.com/vim/vim/commit/b1c9198afb7ff902588b45fbe44f0760a9f48375
Author: Bram Moolenaar <Bram@vim.org>
Date: Thu May 17 17:04:55 2018 +0200
Vim 8.1 release
Update version number and information. Fix a couple of tests.
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Thu, 17 May 2018 17:15:08 +0200 |
| parents | e751b5c9dff3 |
| children | 2f7e67dd088c |
| rev | line source |
|---|---|
| 13963 | 1 *tagsrch.txt* For Vim version 8.1. Last change: 2018 May 04 |
| 7 | 2 |
| 3 | |
| 4 VIM REFERENCE MANUAL by Bram Moolenaar | |
| 5 | |
| 6 | |
| 7 Tags and special searches *tags-and-searches* | |
| 8 | |
| 9 See section |29.1| of the user manual for an introduction. | |
| 10 | |
| 11 1. Jump to a tag |tag-commands| | |
| 12 2. Tag stack |tag-stack| | |
| 13 3. Tag match list |tag-matchlist| | |
| 14 4. Tags details |tag-details| | |
| 15 5. Tags file format |tags-file-format| | |
| 16 6. Include file searches |include-search| | |
| 17 | |
| 18 ============================================================================== | |
| 19 1. Jump to a tag *tag-commands* | |
| 20 | |
| 21 *tag* *tags* | |
| 22 A tag is an identifier that appears in a "tags" file. It is a sort of label | |
| 23 that can be jumped to. For example: In C programs each function name can be | |
| 24 used as a tag. The "tags" file has to be generated by a program like ctags, | |
| 25 before the tag commands can be used. | |
| 26 | |
| 27 With the ":tag" command the cursor will be positioned on the tag. With the | |
| 28 CTRL-] command, the keyword on which the cursor is standing is used as the | |
| 29 tag. If the cursor is not on a keyword, the first keyword to the right of the | |
| 30 cursor is used. | |
| 31 | |
| 32 The ":tag" command works very well for C programs. If you see a call to a | |
| 33 function and wonder what that function does, position the cursor inside of the | |
| 34 function name and hit CTRL-]. This will bring you to the function definition. | |
| 35 An easy way back is with the CTRL-T command. Also read about the tag stack | |
| 36 below. | |
| 37 | |
| 38 *:ta* *:tag* *E426* *E429* | |
| 13857 | 39 :[count]ta[g][!] {name} |
| 40 Jump to the definition of {name}, using the | |
| 41 information in the tags file(s). Put {name} in the | |
| 7 | 42 tag stack. See |tag-!| for [!]. |
| 13857 | 43 {name} can be a regexp pattern, see |tag-regexp|. |
| 44 When there are several matching tags for {name}, jump | |
| 685 | 45 to the [count] one. When [count] is omitted the |
| 46 first one is jumped to. See |tag-matchlist| for | |
| 47 jumping to other matching tags. | |
| 7 | 48 |
| 49 g<LeftMouse> *g<LeftMouse>* | |
| 50 <C-LeftMouse> *<C-LeftMouse>* *CTRL-]* | |
| 51 CTRL-] Jump to the definition of the keyword under the | |
| 13857 | 52 cursor. Same as ":tag {name}", where {name} is the |
| 685 | 53 keyword under or after cursor. |
| 13857 | 54 When there are several matching tags for {name}, jump |
| 685 | 55 to the [count] one. When no [count] is given the |
| 56 first one is jumped to. See |tag-matchlist| for | |
| 57 jumping to other matching tags. | |
| 58 {Vi: identifier after the cursor} | |
| 7 | 59 |
| 60 *v_CTRL-]* | |
| 13857 | 61 {Visual}CTRL-] Same as ":tag {name}", where {name} is the text that |
| 7 | 62 is highlighted. {not in Vi} |
| 63 | |
| 64 *telnet-CTRL-]* | |
| 65 CTRL-] is the default telnet escape key. When you type CTRL-] to jump to a | |
| 66 tag, you will get the telnet prompt instead. Most versions of telnet allow | |
| 67 changing or disabling the default escape key. See the telnet man page. You | |
| 68 can 'telnet -E {Hostname}' to disable the escape character, or 'telnet -e | |
| 69 {EscapeCharacter} {Hostname}' to specify another escape character. If | |
| 56 | 70 possible, try to use "ssh" instead of "telnet" to avoid this problem. |
| 7 | 71 |
| 72 *tag-priority* | |
| 73 When there are multiple matches for a tag, this priority is used: | |
| 74 1. "FSC" A full matching static tag for the current file. | |
| 75 2. "F C" A full matching global tag for the current file. | |
| 76 3. "F " A full matching global tag for another file. | |
| 77 4. "FS " A full matching static tag for another file. | |
| 78 5. " SC" An ignore-case matching static tag for the current file. | |
| 79 6. " C" An ignore-case matching global tag for the current file. | |
| 80 7. " " An ignore-case matching global tag for another file. | |
| 81 8. " S " An ignore-case matching static tag for another file. | |
| 82 | |
| 83 Note that when the current file changes, the priority list is mostly not | |
| 84 changed, to avoid confusion when using ":tnext". It is changed when using | |
| 13857 | 85 ":tag {name}". |
| 7 | 86 |
|
9913
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
87 The ignore-case matches are not found for a ":tag" command when: |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
88 - the 'ignorecase' option is off and 'tagcase' is "followic" |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
89 - 'tagcase' is "match" |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
90 - 'tagcase' is "smart" and the pattern contains an upper case character. |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
91 - 'tagcase' is "followscs" and 'smartcase' option is on and the pattern |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
92 contains an upper case character. |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
93 |
|
10218
584c835a2de1
commit https://github.com/vim/vim/commit/50ba526fbf3e9e5e0e6b0b3086a4d5df581ebc7e
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
94 The ignore-case matches are found when: |
|
9913
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
95 - a pattern is used (starting with a "/") |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
96 - for ":tselect" |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
97 - when 'tagcase' is "followic" and 'ignorecase' is off |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
98 - when 'tagcase' is "match" |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
99 - when 'tagcase' is "followscs" and the 'smartcase' option is off |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
100 |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
101 Note that using ignore-case tag searching disables binary searching in the |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
102 tags file, which causes a slowdown. This can be avoided by fold-case sorting |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
103 the tag file. See the 'tagbsearch' option for an explanation. |
| 7 | 104 |
| 105 ============================================================================== | |
| 106 2. Tag stack *tag-stack* *tagstack* *E425* | |
| 107 | |
| 108 On the tag stack is remembered which tags you jumped to, and from where. | |
| 109 Tags are only pushed onto the stack when the 'tagstack' option is set. | |
| 110 | |
| 111 g<RightMouse> *g<RightMouse>* | |
| 112 <C-RightMouse> *<C-RightMouse>* *CTRL-T* | |
| 113 CTRL-T Jump to [count] older entry in the tag stack | |
| 114 (default 1). {not in Vi} | |
| 115 | |
| 116 *:po* *:pop* *E555* *E556* | |
| 117 :[count]po[p][!] Jump to [count] older entry in tag stack (default 1). | |
| 118 See |tag-!| for [!]. {not in Vi} | |
| 119 | |
| 120 :[count]ta[g][!] Jump to [count] newer entry in tag stack (default 1). | |
| 121 See |tag-!| for [!]. {not in Vi} | |
| 122 | |
| 123 *:tags* | |
| 124 :tags Show the contents of the tag stack. The active | |
| 125 entry is marked with a '>'. {not in Vi} | |
| 126 | |
| 127 The output of ":tags" looks like this: | |
| 128 | |
| 2681 | 129 # TO tag FROM line in file/text |
| 7 | 130 1 1 main 1 harddisk2:text/vim/test |
| 131 > 2 2 FuncA 58 i = FuncA(10); | |
| 132 3 1 FuncC 357 harddisk2:text/vim/src/amiga.c | |
| 133 | |
| 134 This list shows the tags that you jumped to and the cursor position before | |
| 135 that jump. The older tags are at the top, the newer at the bottom. | |
| 136 | |
| 137 The '>' points to the active entry. This is the tag that will be used by the | |
| 138 next ":tag" command. The CTRL-T and ":pop" command will use the position | |
| 139 above the active entry. | |
| 140 | |
| 141 Below the "TO" is the number of the current match in the match list. Note | |
| 142 that this doesn't change when using ":pop" or ":tag". | |
| 143 | |
| 144 The line number and file name are remembered to be able to get back to where | |
| 145 you were before the tag command. The line number will be correct, also when | |
| 146 deleting/inserting lines, unless this was done by another program (e.g. | |
| 147 another instance of Vim). | |
| 148 | |
| 2681 | 149 For the current file, the "file/text" column shows the text at the position. |
| 7 | 150 An indent is removed and a long line is truncated to fit in the window. |
| 151 | |
| 152 You can jump to previously used tags with several commands. Some examples: | |
| 153 | |
| 154 ":pop" or CTRL-T to position before previous tag | |
| 155 {count}CTRL-T to position before {count} older tag | |
| 156 ":tag" to newer tag | |
| 157 ":0tag" to last used tag | |
| 158 | |
| 159 The most obvious way to use this is while browsing through the call graph of | |
| 160 a program. Consider the following call graph: | |
| 161 | |
| 162 main ---> FuncA ---> FuncC | |
| 163 ---> FuncB | |
| 164 | |
| 165 (Explanation: main calls FuncA and FuncB; FuncA calls FuncC). | |
| 166 You can get from main to FuncA by using CTRL-] on the call to FuncA. Then | |
| 167 you can CTRL-] to get to FuncC. If you now want to go back to main you can | |
| 168 use CTRL-T twice. Then you can CTRL-] to FuncB. | |
| 169 | |
| 13857 | 170 If you issue a ":ta {name}" or CTRL-] command, this tag is inserted at the |
| 7 | 171 current position in the stack. If the stack was full (it can hold up to 20 |
| 172 entries), the oldest entry is deleted and the older entries shift one | |
| 173 position up (their index number is decremented by one). If the last used | |
| 174 entry was not at the bottom, the entries below the last used one are | |
| 175 deleted. This means that an old branch in the call graph is lost. After the | |
| 176 commands explained above the tag stack will look like this: | |
| 177 | |
| 2681 | 178 # TO tag FROM line in file/text |
| 179 1 1 main 1 harddisk2:text/vim/test | |
| 180 2 1 FuncB 59 harddisk2:text/vim/src/main.c | |
| 7 | 181 |
| 182 *E73* | |
| 183 When you try to use the tag stack while it doesn't contain anything you will | |
| 184 get an error message. | |
| 185 | |
| 186 ============================================================================== | |
| 187 3. Tag match list *tag-matchlist* *E427* *E428* | |
| 188 | |
| 189 When there are several matching tags, these commands can be used to jump | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
190 between them. Note that these commands don't change the tag stack, they keep |
| 7 | 191 the same entry. |
| 192 | |
| 193 *:ts* *:tselect* | |
| 13857 | 194 :ts[elect][!] [name] List the tags that match [name], using the |
| 7 | 195 information in the tags file(s). |
| 13857 | 196 When [name] is not given, the last tag name from the |
| 7 | 197 tag stack is used. |
|
12756
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
198 See |tag-!| for [!]. |
| 7 | 199 With a '>' in the first column is indicated which is |
| 200 the current position in the list (if there is one). | |
| 13857 | 201 [name] can be a regexp pattern, see |tag-regexp|. |
| 7 | 202 See |tag-priority| for the priorities used in the |
| 203 listing. {not in Vi} | |
| 204 Example output: | |
| 205 | |
| 206 > | |
| 207 nr pri kind tag file | |
| 208 1 F f mch_delay os_amiga.c | |
| 209 mch_delay(msec, ignoreinput) | |
| 210 > 2 F f mch_delay os_msdos.c | |
| 211 mch_delay(msec, ignoreinput) | |
| 212 3 F f mch_delay os_unix.c | |
| 213 mch_delay(msec, ignoreinput) | |
| 214 Enter nr of choice (<CR> to abort): | |
| 215 < | |
| 216 See |tag-priority| for the "pri" column. Note that | |
| 217 this depends on the current file, thus using | |
| 218 ":tselect xxx" can produce different results. | |
| 219 The "kind" column gives the kind of tag, if this was | |
| 220 included in the tags file. | |
| 221 The "info" column shows information that could be | |
| 222 found in the tags file. It depends on the program | |
| 223 that produced the tags file. | |
| 224 When the list is long, you may get the |more-prompt|. | |
| 225 If you already see the tag you want to use, you can | |
| 226 type 'q' and enter the number. | |
| 227 | |
| 228 *:sts* *:stselect* | |
| 13857 | 229 :sts[elect][!] [name] Does ":tselect[!] [name]" and splits the window for |
| 7 | 230 the selected tag. {not in Vi} |
| 231 | |
| 232 *g]* | |
| 233 g] Like CTRL-], but use ":tselect" instead of ":tag". | |
| 234 {not in Vi} | |
| 235 | |
| 236 *v_g]* | |
| 237 {Visual}g] Same as "g]", but use the highlighted text as the | |
| 238 identifier. {not in Vi} | |
| 239 | |
| 240 *:tj* *:tjump* | |
| 13857 | 241 :tj[ump][!] [name] Like ":tselect", but jump to the tag directly when |
| 7 | 242 there is only one match. {not in Vi} |
| 243 | |
| 244 *:stj* *:stjump* | |
| 13857 | 245 :stj[ump][!] [name] Does ":tjump[!] [name]" and splits the window for the |
| 7 | 246 selected tag. {not in Vi} |
| 247 | |
| 248 *g_CTRL-]* | |
| 249 g CTRL-] Like CTRL-], but use ":tjump" instead of ":tag". | |
| 250 {not in Vi} | |
| 251 | |
| 252 *v_g_CTRL-]* | |
| 253 {Visual}g CTRL-] Same as "g CTRL-]", but use the highlighted text as | |
| 254 the identifier. {not in Vi} | |
| 255 | |
| 256 *:tn* *:tnext* | |
| 257 :[count]tn[ext][!] Jump to [count] next matching tag (default 1). See | |
| 258 |tag-!| for [!]. {not in Vi} | |
| 259 | |
| 260 *:tp* *:tprevious* | |
| 261 :[count]tp[revious][!] Jump to [count] previous matching tag (default 1). | |
| 262 See |tag-!| for [!]. {not in Vi} | |
| 263 | |
| 264 *:tN* *:tNext* | |
| 265 :[count]tN[ext][!] Same as ":tprevious". {not in Vi} | |
| 266 | |
| 267 *:tr* *:trewind* | |
| 268 :[count]tr[ewind][!] Jump to first matching tag. If [count] is given, jump | |
| 269 to [count]th matching tag. See |tag-!| for [!]. {not | |
| 270 in Vi} | |
| 271 | |
| 272 *:tf* *:tfirst* | |
| 237 | 273 :[count]tf[irst][!] Same as ":trewind". {not in Vi} |
| 7 | 274 |
| 275 *:tl* *:tlast* | |
| 276 :tl[ast][!] Jump to last matching tag. See |tag-!| for [!]. {not | |
| 277 in Vi} | |
| 278 | |
| 651 | 279 *:lt* *:ltag* |
| 13857 | 280 :lt[ag][!] [name] Jump to tag [name] and add the matching tags to a new |
| 281 location list for the current window. [name] can be | |
| 282 a regexp pattern, see |tag-regexp|. When [name] is | |
| 651 | 283 not given, the last tag name from the tag stack is |
| 284 used. The search pattern to locate the tag line is | |
| 285 prefixed with "\V" to escape all the special | |
| 286 characters (very nomagic). The location list showing | |
| 287 the matching tags is independent of the tag stack. | |
| 288 See |tag-!| for [!]. | |
| 289 {not in Vi} | |
| 7 | 290 |
| 291 When there is no other message, Vim shows which matching tag has been jumped | |
| 292 to, and the number of matching tags: > | |
| 293 tag 1 of 3 or more | |
| 294 The " or more" is used to indicate that Vim didn't try all the tags files yet. | |
| 295 When using ":tnext" a few times, or with ":tlast", more matches may be found. | |
| 296 | |
| 297 When you didn't see this message because of some other message, or you just | |
| 298 want to know where you are, this command will show it again (and jump to the | |
| 299 same tag as last time): > | |
| 300 :0tn | |
| 301 < | |
| 302 *tag-skip-file* | |
| 303 When a matching tag is found for which the file doesn't exist, this match is | |
| 304 skipped and the next matching tag is used. Vim reports this, to notify you of | |
| 305 missing files. When the end of the list of matches has been reached, an error | |
| 306 message is given. | |
| 307 | |
| 651 | 308 *tag-preview* |
| 7 | 309 The tag match list can also be used in the preview window. The commands are |
| 310 the same as above, with a "p" prepended. | |
| 311 {not available when compiled without the |+quickfix| feature} | |
| 312 | |
| 313 *:pts* *:ptselect* | |
| 13857 | 314 :pts[elect][!] [name] Does ":tselect[!] [name]" and shows the new tag in a |
| 237 | 315 "Preview" window. See |:ptag| for more info. |
| 7 | 316 {not in Vi} |
| 317 | |
| 318 *:ptj* *:ptjump* | |
| 13857 | 319 :ptj[ump][!] [name] Does ":tjump[!] [name]" and shows the new tag in a |
| 237 | 320 "Preview" window. See |:ptag| for more info. |
| 7 | 321 {not in Vi} |
| 322 | |
| 323 *:ptn* *:ptnext* | |
| 324 :[count]ptn[ext][!] ":tnext" in the preview window. See |:ptag|. | |
| 325 {not in Vi} | |
| 326 | |
| 327 *:ptp* *:ptprevious* | |
| 328 :[count]ptp[revious][!] ":tprevious" in the preview window. See |:ptag|. | |
| 329 {not in Vi} | |
| 330 | |
| 331 *:ptN* *:ptNext* | |
| 332 :[count]ptN[ext][!] Same as ":ptprevious". {not in Vi} | |
| 333 | |
| 334 *:ptr* *:ptrewind* | |
| 335 :[count]ptr[ewind][!] ":trewind" in the preview window. See |:ptag|. | |
| 336 {not in Vi} | |
| 337 | |
| 338 *:ptf* *:ptfirst* | |
| 237 | 339 :[count]ptf[irst][!] Same as ":ptrewind". {not in Vi} |
| 7 | 340 |
| 341 *:ptl* *:ptlast* | |
| 342 :ptl[ast][!] ":tlast" in the preview window. See |:ptag|. | |
| 343 {not in Vi} | |
| 344 | |
| 345 ============================================================================== | |
| 346 4. Tags details *tag-details* | |
| 347 | |
| 348 *static-tag* | |
| 349 A static tag is a tag that is defined for a specific file. In a C program | |
| 350 this could be a static function. | |
| 351 | |
| 352 In Vi jumping to a tag sets the current search pattern. This means that | |
| 353 the "n" command after jumping to a tag does not search for the same pattern | |
| 354 that it did before jumping to the tag. Vim does not do this as we consider it | |
| 355 to be a bug. You can still find the tag search pattern in the search history. | |
| 356 If you really want the old Vi behavior, set the 't' flag in 'cpoptions'. | |
| 357 | |
| 358 *tag-binary-search* | |
| 359 Vim uses binary searching in the tags file to find the desired tag quickly | |
| 360 (when enabled at compile time |+tag_binary|). But this only works if the | |
| 361 tags file was sorted on ASCII byte value. Therefore, if no match was found, | |
| 362 another try is done with a linear search. If you only want the linear search, | |
| 363 reset the 'tagbsearch' option. Or better: Sort the tags file! | |
| 364 | |
| 365 Note that the binary searching is disabled when not looking for a tag with a | |
| 366 specific name. This happens when ignoring case and when a regular expression | |
| 367 is used that doesn't start with a fixed string. Tag searching can be a lot | |
| 368 slower then. The former can be avoided by case-fold sorting the tags file. | |
| 369 See 'tagbsearch' for details. | |
| 370 | |
| 371 *tag-regexp* | |
| 5244 | 372 The ":tag" and ":tselect" commands accept a regular expression argument. See |
| 7 | 373 |pattern| for the special characters that can be used. |
| 374 When the argument starts with '/', it is used as a pattern. If the argument | |
| 375 does not start with '/', it is taken literally, as a full tag name. | |
| 376 Examples: > | |
| 377 :tag main | |
| 378 < jumps to the tag "main" that has the highest priority. > | |
| 379 :tag /^get | |
| 380 < jumps to the tag that starts with "get" and has the highest priority. > | |
| 381 :tag /norm | |
| 382 < lists all the tags that contain "norm", including "id_norm". | |
| 383 When the argument both exists literally, and match when used as a regexp, a | |
| 384 literal match has a higher priority. For example, ":tag /open" matches "open" | |
| 385 before "open_file" and "file_open". | |
| 415 | 386 When using a pattern case is ignored. If you want to match case use "\C" in |
| 387 the pattern. | |
| 7 | 388 |
| 389 *tag-!* | |
| 390 If the tag is in the current file this will always work. Otherwise the | |
| 391 performed actions depend on whether the current file was changed, whether a ! | |
| 392 is added to the command and on the 'autowrite' option: | |
| 393 | |
| 394 tag in file autowrite ~ | |
| 395 current file changed ! option action ~ | |
| 396 ----------------------------------------------------------------------------- | |
| 397 yes x x x goto tag | |
| 398 no no x x read other file, goto tag | |
| 399 no yes yes x abandon current file, read other file, goto | |
| 400 tag | |
| 401 no yes no on write current file, read other file, goto | |
| 402 tag | |
| 403 no yes no off fail | |
| 404 ----------------------------------------------------------------------------- | |
| 405 | |
| 406 - If the tag is in the current file, the command will always work. | |
| 407 - If the tag is in another file and the current file was not changed, the | |
| 408 other file will be made the current file and read into the buffer. | |
| 409 - If the tag is in another file, the current file was changed and a ! is | |
| 410 added to the command, the changes to the current file are lost, the other | |
| 411 file will be made the current file and read into the buffer. | |
| 412 - If the tag is in another file, the current file was changed and the | |
| 413 'autowrite' option is on, the current file will be written, the other | |
| 414 file will be made the current file and read into the buffer. | |
| 415 - If the tag is in another file, the current file was changed and the | |
| 416 'autowrite' option is off, the command will fail. If you want to save | |
| 417 the changes, use the ":w" command and then use ":tag" without an argument. | |
| 418 This works because the tag is put on the stack anyway. If you want to lose | |
| 419 the changes you can use the ":tag!" command. | |
| 420 | |
| 421 *tag-security* | |
| 422 Note that Vim forbids some commands, for security reasons. This works like | |
| 423 using the 'secure' option for exrc/vimrc files in the current directory. See | |
| 424 |trojan-horse| and |sandbox|. | |
| 425 When the {tagaddress} changes a buffer, you will get a warning message: | |
| 426 "WARNING: tag command changed a buffer!!!" | |
| 427 In a future version changing the buffer will be impossible. All this for | |
| 428 security reasons: Somebody might hide a nasty command in the tags file, which | |
| 429 would otherwise go unnoticed. Example: > | |
| 430 :$d|/tag-function-name/ | |
| 237 | 431 {this security prevention is not present in Vi} |
| 7 | 432 |
| 433 In Vi the ":tag" command sets the last search pattern when the tag is searched | |
| 434 for. In Vim this is not done, the previous search pattern is still remembered, | |
| 435 unless the 't' flag is present in 'cpoptions'. The search pattern is always | |
| 436 put in the search history, so you can modify it if searching fails. | |
| 437 | |
| 438 *emacs-tags* *emacs_tags* *E430* | |
| 439 Emacs style tag files are only supported if Vim was compiled with the | |
| 440 |+emacs_tags| feature enabled. Sorry, there is no explanation about Emacs tag | |
| 441 files here, it is only supported for backwards compatibility :-). | |
| 442 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
443 Lines in Emacs tags files can be very long. Vim only deals with lines of up |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
444 to about 510 bytes. To see whether lines are ignored set 'verbose' to 5 or |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
445 higher. |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
446 |
| 7 | 447 *tags-option* |
| 448 The 'tags' option is a list of file names. Each of these files is searched | |
| 449 for the tag. This can be used to use a different tags file than the default | |
| 450 file "tags". It can also be used to access a common tags file. | |
| 451 | |
| 452 The next file in the list is not used when: | |
| 453 - A matching static tag for the current buffer has been found. | |
| 454 - A matching global tag has been found. | |
|
9913
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
455 This also depends on whether case is ignored. Case is ignored when: |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
456 - 'tagcase' is "followic" and 'ignorecase' is set |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
457 - 'tagcase' is "ignore" |
|
9975
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
458 - 'tagcase' is "smart" and the pattern only contains lower case |
|
9913
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
459 characters. |
|
9975
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
460 - 'tagcase' is "followscs" and 'smartcase' is set and the pattern only |
|
9913
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
461 contains lower case characters. |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
462 If case is not ignored, and the tags file only has a match without matching |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
463 case, the next tags file is searched for a match with matching case. If no |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
464 tag with matching case is found, the first match without matching case is |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
465 used. If case is ignored, and a matching global tag with or without matching |
|
bb00c661b3a4
commit https://github.com/vim/vim/commit/66e29d7112e437b2b50efe1f82c7e892736d23e4
Christian Brabandt <cb@256bit.org>
parents:
7266
diff
changeset
|
466 case is found, this one is used, no further tags files are searched. |
| 7 | 467 |
| 468 When a tag file name starts with "./", the '.' is replaced with the path of | |
| 469 the current file. This makes it possible to use a tags file in the directory | |
| 470 where the current file is (no matter what the current directory is). The idea | |
| 471 of using "./" is that you can define which tag file is searched first: In the | |
| 472 current directory ("tags,./tags") or in the directory of the current file | |
| 473 ("./tags,tags"). | |
| 474 | |
| 475 For example: > | |
| 476 :set tags=./tags,tags,/home/user/commontags | |
| 477 | |
| 478 In this example the tag will first be searched for in the file "tags" in the | |
| 479 directory where the current file is. Next the "tags" file in the current | |
| 480 directory. If it is not found there, then the file "/home/user/commontags" | |
| 481 will be searched for the tag. | |
| 482 | |
| 483 This can be switched off by including the 'd' flag in 'cpoptions', to make | |
| 557 | 484 it Vi compatible. "./tags" will then be the tags file in the current |
| 7 | 485 directory, instead of the tags file in the directory where the current file |
| 486 is. | |
| 487 | |
| 488 Instead of the comma a space may be used. Then a backslash is required for | |
| 489 the space to be included in the string option: > | |
| 490 :set tags=tags\ /home/user/commontags | |
| 491 | |
| 492 To include a space in a file name use three backslashes. To include a comma | |
| 493 in a file name use two backslashes. For example, use: > | |
| 494 :set tags=tag\\\ file,/home/user/common\\,tags | |
| 495 | |
| 496 for the files "tag file" and "/home/user/common,tags". The 'tags' option will | |
| 497 have the value "tag\ file,/home/user/common\,tags". | |
| 498 | |
| 499 If the 'tagrelative' option is on (which is the default) and using a tag file | |
| 500 in another directory, file names in that tag file are relative to the | |
| 501 directory where the tag file is. | |
| 502 | |
| 503 ============================================================================== | |
| 504 5. Tags file format *tags-file-format* *E431* | |
| 505 | |
| 506 *ctags* *jtags* | |
| 507 A tags file can be created with an external command, for example "ctags". It | |
| 508 will contain a tag for each function. Some versions of "ctags" will also make | |
| 509 a tag for each "#defined" macro, typedefs, enums, etc. | |
| 510 | |
| 511 Some programs that generate tags files: | |
| 512 ctags As found on most Unix systems. Only supports C. Only | |
| 513 does the basic work. | |
| 20 | 514 *Exuberant_ctags* |
| 7 | 515 exuberant ctags This a very good one. It works for C, C++, Java, |
| 516 Fortran, Eiffel and others. It can generate tags for | |
| 517 many items. See http://ctags.sourceforge.net. | |
| 518 etags Connected to Emacs. Supports many languages. | |
| 519 JTags For Java, in Java. It can be found at | |
| 520 http://www.fleiner.com/jtags/. | |
| 521 ptags.py For Python, in Python. Found in your Python source | |
| 522 directory at Tools/scripts/ptags.py. | |
| 523 ptags For Perl, in Perl. It can be found at | |
| 524 http://www.eleves.ens.fr:8080/home/nthiery/Tags/. | |
| 525 gnatxref For Ada. See http://www.gnuada.org/. gnatxref is | |
| 526 part of the gnat package. | |
| 527 | |
| 528 | |
| 529 The lines in the tags file must have one of these three formats: | |
| 530 | |
| 531 1. {tagname} {TAB} {tagfile} {TAB} {tagaddress} | |
| 532 2. {tagfile}:{tagname} {TAB} {tagfile} {TAB} {tagaddress} | |
| 533 3. {tagname} {TAB} {tagfile} {TAB} {tagaddress} {term} {field} .. | |
| 534 | |
| 535 The first is a normal tag, which is completely compatible with Vi. It is the | |
| 536 only format produced by traditional ctags implementations. This is often used | |
| 537 for functions that are global, also referenced in other files. | |
| 538 | |
| 539 The lines in the tags file can end in <LF> or <CR><LF>. On the Macintosh <CR> | |
| 540 also works. The <CR> and <NL> characters can never appear inside a line. | |
| 541 | |
| 542 *tag-old-static* | |
| 543 The second format is for a static tag only. It is obsolete now, replaced by | |
| 544 the third format. It is only supported by Elvis 1.x and Vim and a few | |
| 545 versions of ctags. A static tag is often used for functions that are local, | |
| 546 only referenced in the file {tagfile}. Note that for the static tag, the two | |
| 547 occurrences of {tagfile} must be exactly the same. Also see |tags-option| | |
| 548 below, for how static tags are used. | |
| 549 | |
| 550 The third format is new. It includes additional information in optional | |
| 551 fields at the end of each line. It is backwards compatible with Vi. It is | |
| 552 only supported by new versions of ctags (such as Exuberant ctags). | |
| 553 | |
| 554 {tagname} The identifier. Normally the name of a function, but it can | |
| 555 be any identifier. It cannot contain a <Tab>. | |
| 556 {TAB} One <Tab> character. Note: previous versions allowed any | |
| 557 white space here. This has been abandoned to allow spaces in | |
| 558 {tagfile}. It can be re-enabled by including the | |
| 559 |+tag_any_white| feature at compile time. *tag-any-white* | |
| 560 {tagfile} The file that contains the definition of {tagname}. It can | |
| 561 have an absolute or relative path. It may contain environment | |
| 562 variables and wildcards (although the use of wildcards is | |
| 563 doubtful). It cannot contain a <Tab>. | |
| 564 {tagaddress} The Ex command that positions the cursor on the tag. It can | |
| 565 be any Ex command, although restrictions apply (see | |
| 566 |tag-security|). Posix only allows line numbers and search | |
| 567 commands, which are mostly used. | |
| 568 {term} ;" The two characters semicolon and double quote. This is | |
| 569 interpreted by Vi as the start of a comment, which makes the | |
| 570 following be ignored. This is for backwards compatibility | |
| 571 with Vi, it ignores the following fields. | |
| 572 {field} .. A list of optional fields. Each field has the form: | |
| 573 | |
| 574 <Tab>{fieldname}:{value} | |
| 575 | |
| 576 The {fieldname} identifies the field, and can only contain | |
| 577 alphabetical characters [a-zA-Z]. | |
| 578 The {value} is any string, but cannot contain a <Tab>. | |
| 579 These characters are special: | |
| 580 "\t" stands for a <Tab> | |
| 581 "\r" stands for a <CR> | |
| 582 "\n" stands for a <NL> | |
| 583 "\\" stands for a single '\' character | |
| 584 | |
| 585 There is one field that doesn't have a ':'. This is the kind | |
| 586 of the tag. It is handled like it was preceded with "kind:". | |
| 587 See the documentation of ctags for the kinds it produces. | |
| 588 | |
| 589 The only other field currently recognized by Vim is "file:" | |
| 590 (with an empty value). It is used for a static tag. | |
| 591 | |
| 592 The first lines in the tags file can contain lines that start with | |
| 593 !_TAG_ | |
| 594 These are sorted to the first lines, only rare tags that start with "!" can | |
| 595 sort to before them. Vim recognizes two items. The first one is the line | |
| 596 that indicates if the file was sorted. When this line is found, Vim uses | |
| 597 binary searching for the tags file: | |
| 598 !_TAG_FILE_SORTED<Tab>1<Tab>{anything} ~ | |
| 599 | |
|
7266
6ba7182fb7bd
commit https://github.com/vim/vim/commit/0f6562e9036f889185dff49a75c7fc5ffb28b307
Christian Brabandt <cb@256bit.org>
parents:
5400
diff
changeset
|
600 A tag file may be case-fold sorted to avoid a linear search when case is |
|
6ba7182fb7bd
commit https://github.com/vim/vim/commit/0f6562e9036f889185dff49a75c7fc5ffb28b307
Christian Brabandt <cb@256bit.org>
parents:
5400
diff
changeset
|
601 ignored. (Case is ignored when 'ignorecase' is set and 'tagcase' is |
|
6ba7182fb7bd
commit https://github.com/vim/vim/commit/0f6562e9036f889185dff49a75c7fc5ffb28b307
Christian Brabandt <cb@256bit.org>
parents:
5400
diff
changeset
|
602 "followic", or when 'tagcase' is "ignore".) See 'tagbsearch' for details. |
|
6ba7182fb7bd
commit https://github.com/vim/vim/commit/0f6562e9036f889185dff49a75c7fc5ffb28b307
Christian Brabandt <cb@256bit.org>
parents:
5400
diff
changeset
|
603 The value '2' should be used then: |
| 7 | 604 !_TAG_FILE_SORTED<Tab>2<Tab>{anything} ~ |
| 605 | |
| 606 The other tag that Vim recognizes, but only when compiled with the | |
| 607 |+multi_byte| feature, is the encoding of the tags file: | |
| 608 !_TAG_FILE_ENCODING<Tab>utf-8<Tab>{anything} ~ | |
| 609 Here "utf-8" is the encoding used for the tags. Vim will then convert the tag | |
| 610 being searched for from 'encoding' to the encoding of the tags file. And when | |
| 611 listing tags the reverse happens. When the conversion fails the unconverted | |
| 612 tag is used. | |
| 613 | |
| 614 *tag-search* | |
| 615 The command can be any Ex command, but often it is a search command. | |
| 616 Examples: | |
| 617 tag1 file1 /^main(argc, argv)/ ~ | |
| 618 tag2 file2 108 ~ | |
| 619 | |
| 620 The command is always executed with 'magic' not set. The only special | |
| 621 characters in a search pattern are "^" (begin-of-line) and "$" (<EOL>). | |
| 622 See |pattern|. Note that you must put a backslash before each backslash in | |
| 623 the search text. This is for backwards compatibility with Vi. | |
| 624 | |
| 625 *E434* *E435* | |
| 626 If the command is a normal search command (it starts and ends with "/" or | |
| 627 "?"), some special handling is done: | |
| 628 - Searching starts on line 1 of the file. | |
| 629 The direction of the search is forward for "/", backward for "?". | |
| 237 | 630 Note that 'wrapscan' does not matter, the whole file is always searched. (Vi |
| 631 does use 'wrapscan', which caused tags sometimes not be found.) {Vi starts | |
| 7 | 632 searching in line 2 of another file. It does not find a tag in line 1 of |
| 633 another file when 'wrapscan' is not set} | |
| 634 - If the search fails, another try is done ignoring case. If that fails too, | |
| 635 a search is done for: | |
| 636 "^tagname[ \t]*(" | |
| 637 (the tag with '^' prepended and "[ \t]*(" appended). When using function | |
| 638 names, this will find the function name when it is in column 0. This will | |
| 639 help when the arguments to the function have changed since the tags file was | |
| 640 made. If this search also fails another search is done with: | |
| 641 "^[#a-zA-Z_].*\<tagname[ \t]*(" | |
| 642 This means: A line starting with '#' or an identifier and containing the tag | |
| 643 followed by white space and a '('. This will find macro names and function | |
| 237 | 644 names with a type prepended. {the extra searches are not in Vi} |
| 7 | 645 |
| 646 ============================================================================== | |
| 647 6. Include file searches *include-search* *definition-search* | |
| 648 *E387* *E388* *E389* | |
| 649 | |
| 650 These commands look for a string in the current file and in all encountered | |
| 651 included files (recursively). This can be used to find the definition of a | |
| 652 variable, function or macro. If you only want to search in the current | |
| 653 buffer, use the commands listed at |pattern-searches|. | |
| 654 | |
| 655 These commands are not available when the |+find_in_path| feature was disabled | |
| 656 at compile time. | |
| 657 | |
| 658 When a line is encountered that includes another file, that file is searched | |
| 659 before continuing in the current buffer. Files included by included files are | |
| 660 also searched. When an include file could not be found it is silently | |
| 661 ignored. Use the |:checkpath| command to discover which files could not be | |
| 662 found, possibly your 'path' option is not set up correctly. Note: the | |
| 663 included file is searched, not a buffer that may be editing that file. Only | |
| 664 for the current file the lines in the buffer are used. | |
| 665 | |
| 666 The string can be any keyword or a defined macro. For the keyword any match | |
| 667 will be found. For defined macros only lines that match with the 'define' | |
| 668 option will be found. The default is "^#\s*define", which is for C programs. | |
| 669 For other languages you probably want to change this. See 'define' for an | |
| 670 example for C++. The string cannot contain an end-of-line, only matches | |
| 671 within a line are found. | |
| 672 | |
| 673 When a match is found for a defined macro, the displaying of lines continues | |
| 674 with the next line when a line ends in a backslash. | |
| 675 | |
| 676 The commands that start with "[" start searching from the start of the current | |
| 677 file. The commands that start with "]" start at the current cursor position. | |
| 678 | |
| 679 The 'include' option is used to define a line that includes another file. The | |
| 680 default is "\^#\s*include", which is for C programs. Note: Vim does not | |
| 681 recognize C syntax, if the 'include' option matches a line inside | |
| 682 "#ifdef/#endif" or inside a comment, it is searched anyway. The 'isfname' | |
| 683 option is used to recognize the file name that comes after the matched | |
| 684 pattern. | |
| 685 | |
| 686 The 'path' option is used to find the directory for the include files that | |
| 687 do not have an absolute path. | |
| 688 | |
| 689 The 'comments' option is used for the commands that display a single line or | |
| 690 jump to a line. It defines patterns that may start a comment. Those lines | |
| 691 are ignored for the search, unless [!] is used. One exception: When the line | |
| 692 matches the pattern "^# *define" it is not considered to be a comment. | |
| 693 | |
| 694 If you want to list matches, and then select one to jump to, you could use a | |
| 695 mapping to do that for you. Here is an example: > | |
| 696 | |
| 697 :map <F4> [I:let nr = input("Which one: ")<Bar>exe "normal " . nr ."[\t"<CR> | |
| 698 < | |
| 699 *[i* | |
| 700 [i Display the first line that contains the keyword | |
| 701 under the cursor. The search starts at the beginning | |
| 702 of the file. Lines that look like a comment are | |
| 703 ignored (see 'comments' option). If a count is given, | |
| 704 the count'th matching line is displayed, and comment | |
| 705 lines are not ignored. {not in Vi} | |
| 706 | |
| 707 *]i* | |
| 708 ]i like "[i", but start at the current cursor position. | |
| 709 {not in Vi} | |
| 710 | |
| 711 *:is* *:isearch* | |
| 712 :[range]is[earch][!] [count] [/]pattern[/] | |
| 713 Like "[i" and "]i", but search in [range] lines | |
| 714 (default: whole file). | |
| 715 See |:search-args| for [/] and [!]. {not in Vi} | |
| 716 | |
| 717 *[I* | |
| 718 [I Display all lines that contain the keyword under the | |
| 719 cursor. Filenames and line numbers are displayed | |
| 720 for the found lines. The search starts at the | |
| 721 beginning of the file. {not in Vi} | |
| 722 | |
| 723 *]I* | |
| 724 ]I like "[I", but start at the current cursor position. | |
| 725 {not in Vi} | |
| 726 | |
| 727 *:il* *:ilist* | |
| 728 :[range]il[ist][!] [/]pattern[/] | |
| 729 Like "[I" and "]I", but search in [range] lines | |
| 730 (default: whole file). | |
| 731 See |:search-args| for [/] and [!]. {not in Vi} | |
| 732 | |
| 733 *[_CTRL-I* | |
| 734 [ CTRL-I Jump to the first line that contains the keyword | |
| 735 under the cursor. The search starts at the beginning | |
| 736 of the file. Lines that look like a comment are | |
| 737 ignored (see 'comments' option). If a count is given, | |
| 738 the count'th matching line is jumped to, and comment | |
| 739 lines are not ignored. {not in Vi} | |
| 740 | |
| 741 *]_CTRL-I* | |
| 742 ] CTRL-I like "[ CTRL-I", but start at the current cursor | |
| 743 position. {not in Vi} | |
| 744 | |
| 745 *:ij* *:ijump* | |
| 746 :[range]ij[ump][!] [count] [/]pattern[/] | |
| 747 Like "[ CTRL-I" and "] CTRL-I", but search in | |
| 748 [range] lines (default: whole file). | |
| 749 See |:search-args| for [/] and [!]. {not in Vi} | |
| 750 | |
| 751 CTRL-W CTRL-I *CTRL-W_CTRL-I* *CTRL-W_i* | |
| 752 CTRL-W i Open a new window, with the cursor on the first line | |
| 753 that contains the keyword under the cursor. The | |
| 754 search starts at the beginning of the file. Lines | |
| 755 that look like a comment line are ignored (see | |
| 756 'comments' option). If a count is given, the count'th | |
| 757 matching line is jumped to, and comment lines are not | |
| 758 ignored. {not in Vi} | |
| 759 | |
| 760 *:isp* *:isplit* | |
| 761 :[range]isp[lit][!] [count] [/]pattern[/] | |
| 762 Like "CTRL-W i" and "CTRL-W i", but search in | |
| 763 [range] lines (default: whole file). | |
| 764 See |:search-args| for [/] and [!]. {not in Vi} | |
| 765 | |
| 766 *[d* | |
| 767 [d Display the first macro definition that contains the | |
| 768 macro under the cursor. The search starts from the | |
| 769 beginning of the file. If a count is given, the | |
| 770 count'th matching line is displayed. {not in Vi} | |
| 771 | |
| 772 *]d* | |
| 773 ]d like "[d", but start at the current cursor position. | |
| 774 {not in Vi} | |
| 775 | |
| 776 *:ds* *:dsearch* | |
| 777 :[range]ds[earch][!] [count] [/]string[/] | |
| 778 Like "[d" and "]d", but search in [range] lines | |
| 779 (default: whole file). | |
| 780 See |:search-args| for [/] and [!]. {not in Vi} | |
| 781 | |
| 782 *[D* | |
| 783 [D Display all macro definitions that contain the macro | |
| 784 under the cursor. Filenames and line numbers are | |
| 785 displayed for the found lines. The search starts | |
| 786 from the beginning of the file. {not in Vi} | |
| 787 | |
| 788 *]D* | |
| 789 ]D like "[D", but start at the current cursor position. | |
| 790 {not in Vi} | |
| 791 | |
| 169 | 792 *:dli* *:dlist* |
| 3224 | 793 :[range]dli[st][!] [/]string[/] |
| 5400 | 794 Like `[D` and `]D`, but search in [range] lines |
| 7 | 795 (default: whole file). |
| 796 See |:search-args| for [/] and [!]. {not in Vi} | |
| 5400 | 797 Note that `:dl` works like `:delete` with the "l" |
| 798 flag, not `:dlist`. | |
| 7 | 799 |
| 800 *[_CTRL-D* | |
| 801 [ CTRL-D Jump to the first macro definition that contains the | |
| 802 keyword under the cursor. The search starts from | |
| 803 the beginning of the file. If a count is given, the | |
| 804 count'th matching line is jumped to. {not in Vi} | |
| 805 | |
| 806 *]_CTRL-D* | |
| 807 ] CTRL-D like "[ CTRL-D", but start at the current cursor | |
| 808 position. {not in Vi} | |
| 809 | |
| 810 *:dj* *:djump* | |
| 811 :[range]dj[ump][!] [count] [/]string[/] | |
| 812 Like "[ CTRL-D" and "] CTRL-D", but search in | |
| 813 [range] lines (default: whole file). | |
| 814 See |:search-args| for [/] and [!]. {not in Vi} | |
| 815 | |
| 816 CTRL-W CTRL-D *CTRL-W_CTRL-D* *CTRL-W_d* | |
| 817 CTRL-W d Open a new window, with the cursor on the first | |
| 818 macro definition line that contains the keyword | |
| 819 under the cursor. The search starts from the | |
| 820 beginning of the file. If a count is given, the | |
| 821 count'th matching line is jumped to. {not in Vi} | |
| 822 | |
| 823 *:dsp* *:dsplit* | |
| 824 :[range]dsp[lit][!] [count] [/]string[/] | |
| 825 Like "CTRL-W d", but search in [range] lines | |
| 826 (default: whole file). | |
| 827 See |:search-args| for [/] and [!]. {not in Vi} | |
| 828 | |
| 829 *:che* *:checkpath* | |
| 830 :che[ckpath] List all the included files that could not be found. | |
| 831 {not in Vi} | |
| 832 | |
| 833 :che[ckpath]! List all the included files. {not in Vi} | |
| 834 | |
| 835 *:search-args* | |
| 836 Common arguments for the commands above: | |
|
9975
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
837 [!] When included, find matches in lines that are recognized as comments. |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
838 When excluded, a match is ignored when the line is recognized as a |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
839 comment (according to 'comments'), or the match is in a C comment |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
840 (after "//" or inside /* */). Note that a match may be missed if a |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
841 line is recognized as a comment, but the comment ends halfway the line. |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
842 And if the line is a comment, but it is not recognized (according to |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
843 'comments') a match may be found in it anyway. Example: > |
| 7 | 844 /* comment |
| 845 foobar */ | |
|
9975
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
846 < A match for "foobar" is found, because this line is not recognized as |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
847 a comment (even though syntax highlighting does recognize it). |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
848 Note: Since a macro definition mostly doesn't look like a comment, the |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
849 [!] makes no difference for ":dlist", ":dsearch" and ":djump". |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
850 [/] A pattern can be surrounded by '/'. Without '/' only whole words are |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
851 matched, using the pattern "\<pattern\>". Only after the second '/' a |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
852 next command can be appended with '|'. Example: > |
| 7 | 853 :isearch /string/ | echo "the last one" |
|
9975
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
854 < For a ":djump", ":dsplit", ":dlist" and ":dsearch" command the pattern |
|
03fa8a51e9dc
commit https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
Christian Brabandt <cb@256bit.org>
parents:
9913
diff
changeset
|
855 is used as a literal string, not as a search pattern. |
| 7 | 856 |
| 857 vim:tw=78:ts=8:ft=help:norl: |