-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find is unable to find \r nor \t #627
Comments
Instead of looking for the string, it's looking for the character represented i.e. \t is TAB, \r is return, and \n is newline. |
Amusingly, I think github removed your double backslash (assuming that is what you meant)...unless you just made a typo. I shall cheat by using full-width backslashes to convey what you presumably meant: \\t for \t Correct? (replacing the full-width backslashes with normal backslashes of course) |
Yes \\t for \t |
Issue
If your document includes
\r
or\t
then Find is unable to find either. This also applies to replace's "search for" text box.Steps to reproduce
\r
or\t
Search
▶Find
video.webm
Expected behaviour
Xed should be able to find text with
\r
or\t
Other information
Tested using the newly-released non-beta live ISO.
The main issue is that any checksum files created via wine applications (because there seem to be no native Linux checksum-creation programs with a GUI that can recursively hash subfolders & files) will use backslashes, and my go-to username begins with r which means that any paths for my home folder include
\r
Currently the only solution is for me to mass-replace any backslash with a normal slash since the software I use to read checksum files does not care if a backslash or a normal slash is used for a directory separator.
The text was updated successfully, but these errors were encountered: