This repository was archived by the owner on Sep 6, 2021. It is now read-only.
Fix #971 (Find in Files treats \n, \r, etc. as regular expressions) #1033
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
…- Escape backslash too (and simplify escaping regexp to use char class instead of |).
ghost
assigned
|
@gruehle, since this is your code do you want to review? |
gruehle
added a commit
that referenced
this pull request
Jun 12, 2012
Fix #971 (Find in Files treats \n, \r, etc. as regular expressions)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fix #971 -- Escape backslash too (and simplify escaping regexp to use char class instead of
|)