View Single Post
Old 03-28-2020, 03:00 AM   #14
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
I'm not sure what "fuzzy" search you are going to use, or why it would help. The problem I have with the change to the "normal" search, is that when I use it, I expect it to only find exact matches for the search term. That is how it works in every editor I have ever used. Now, if there is any white space involved, it probably won't be an exact match. Any leading or trailing white space is being removed. And white space in the middle is being reduced to "one or more".

For example, if I search for:

Code:
 abc  def
(space at the start and end, two spaces in the middle)

It will match, "xyzabc defghi", which is not the string I am looking for.

The problem in the first post is because the last character in the search term is the line-end character and is removed with the current search. Changing to a regex using a $ to get the end of the line won't help as that doesn't include the line-end character in the match, so it won't get replaced.
davidfor is offline   Reply With Quote