feat: add literal (non-regex) search commands, search_literal and rsearch_literal
#14388
Conversation
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
Introduce `search_literal` and `rsearch_literal` commands for forward and reverse literal (non-regex) text search. This allows searching for text containing regex metacharacters without needing to escape them.
badranX
changed the title
search_literal and rsearch_literalsearch_literal and rsearch_literal
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is related to #4978
Adds
search_literalandrsearch_literal, which behave likesearch/rsearchbut match raw text instead of regex.Motivation: escaping common characters like
(,[,+is tedious.I didn't map them to any default key.