Skip to content
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

Open
NintendoManiac64 opened this issue Jan 15, 2024 · 3 comments
Open

Find is unable to find \r nor \t #627

NintendoManiac64 opened this issue Jan 15, 2024 · 3 comments

Comments

@NintendoManiac64
Copy link

NintendoManiac64 commented Jan 15, 2024

 * Xed version 3.4.5
 * Mint 21.3 Xfce

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

  1. Open Xed
  2. Type \r or \t
  3. Go to SearchFind
  4. 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.

@tsharitt
Copy link

tsharitt commented Jan 27, 2024

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.

@NintendoManiac64
Copy link
Author

NintendoManiac64 commented Jan 27, 2024

Ex. \t for \t, \r for \r etc.

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)

@tsharitt
Copy link

Yes \\t for \t
Sorry about that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants