Mercurial > vim

comparison runtime/doc/tagsrch.txt @ 19055:8645b73b3645 v8.2.0088

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.2.0088: insufficient tests for tags; bug in using extra tag field Commit: https://github.com/vim/vim/commit/830c1afc9d2cd5819a05c71d4e0b1f748a8c0519 Author: Bram Moolenaar <Bram@vim.org> Date: Sun Jan 5 20:35:44 2020 +0100 patch 8.2.0088: insufficient tests for tags; bug in using extra tag field Problem: Insufficient tests for tags; bug in using extra tag field when using an ex command to position the cursor. Solution: Fix the bug, add more tests. (Yegappan Lakshmanan, closes #5439)
author Bram Moolenaar <Bram@vim.org>
date Sun, 05 Jan 2020 20:45:05 +0100
parents d20ed2e5a776
children 51bc26d4a393
comparison
equal deleted inserted replaced
19054:ebee9e4dac40 19055:8645b73b3645
342 342
343 *static-tag* 343 *static-tag*
344 A static tag is a tag that is defined for a specific file. In a C program 344 A static tag is a tag that is defined for a specific file. In a C program
345 this could be a static function. 345 this could be a static function.
346 346
347 In Vi jumping to a tag sets the current search pattern. This means that 347 In Vi jumping to a tag sets the current search pattern. This means that the
348 the "n" command after jumping to a tag does not search for the same pattern 348 "n" command after jumping to a tag does not search for the same pattern that
349 that it did before jumping to the tag. Vim does not do this as we consider it 349 it did before jumping to the tag. Vim does not do this as we consider it to
350 to be a bug. You can still find the tag search pattern in the search history. 350 be a bug. If you really want the old Vi behavior, set the 't' flag in
351 If you really want the old Vi behavior, set the 't' flag in 'cpoptions'. 351 'cpoptions'.
352 352
353 *tag-binary-search* 353 *tag-binary-search*
354 Vim uses binary searching in the tags file to find the desired tag quickly 354 Vim uses binary searching in the tags file to find the desired tag quickly
355 (when enabled at compile time |+tag_binary|). But this only works if the 355 (when enabled at compile time |+tag_binary|). But this only works if the
356 tags file was sorted on ASCII byte value. Therefore, if no match was found, 356 tags file was sorted on ASCII byte value. Therefore, if no match was found,
424 would otherwise go unnoticed. Example: > 424 would otherwise go unnoticed. Example: >
425 :$d|/tag-function-name/ 425 :$d|/tag-function-name/
426 426
427 In Vi the ":tag" command sets the last search pattern when the tag is searched 427 In Vi the ":tag" command sets the last search pattern when the tag is searched
428 for. In Vim this is not done, the previous search pattern is still remembered, 428 for. In Vim this is not done, the previous search pattern is still remembered,
429 unless the 't' flag is present in 'cpoptions'. The search pattern is always 429 unless the 't' flag is present in 'cpoptions'.
430 put in the search history, so you can modify it if searching fails.
431 430
432 *emacs-tags* *emacs_tags* *E430* 431 *emacs-tags* *emacs_tags* *E430*
433 Emacs style tag files are only supported if Vim was compiled with the 432 Emacs style tag files are only supported if Vim was compiled with the
434 |+emacs_tags| feature enabled. Sorry, there is no explanation about Emacs tag 433 |+emacs_tags| feature enabled. Sorry, there is no explanation about Emacs tag
435 files here, it is only supported for backwards compatibility :-). 434 files here, it is only supported for backwards compatibility :-).