You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Open Xed
Type \r or \t
Go to Search ▶ Find
in the "Search for" text box, type whatever you typed in the second step
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:
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.
Before I look at it, I'm not sure if it's intentional or just an oversight.
I did want to mention that you can search for those strings by escaping the slash
Ex. \\t for \t, \\r for \r etc.
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: