Fix tagorder when the argument contains a pattern#21
Open
pjkack wants to merge 1 commit into
Open
Conversation
If the argument does not start with '/' then always treat it as a word
literal by escaping it properly for taglist. This behaviour is
consistent with ":tag" and ":stag", meaning that the jump will actually go
to the correct tag location. To get the best performance it is important
that the pattern taglist starts with exactly '^', else the binary search
seems to be skipped.
When argument is a pattern starting with '/', don't add the exact match
match anchors '^' and '$'.
:help taglist
taglist({expr}) Returns a list of tags matching the regular expression
{expr}
:help tag-regexp
The ":tag" and ":tselect" commands accept a regular expression argument.
When the argument starts with '/', it is used as a pattern. If the argument
does not start with '/', it is taken literally, as a full tag name.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If the argument does not start with '/' then always treat it as a word
literal by escaping it properly for taglist. This behaviour is
consistent with ":tag" and ":stag", meaning that the jump will actually go
to the correct tag location. To get the best performance it is important
that the pattern taglist starts with exactly '^', else the binary search
seems to be skipped.
When argument is a pattern starting with '/', don't add the exact match
match anchors '^' and '$'.
:help taglist
taglist({expr}) Returns a list of tags matching the regular expression
{expr}
:help tag-regexp
The ":tag" and ":tselect" commands accept a regular expression argument.
When the argument starts with '/', it is used as a pattern. If the argument
does not start with '/', it is taken literally, as a full tag name.