Find Files and QS broken

Things you’d like to miss in the future...
Post Reply
autocart
Posts: 1246
Joined: 26 Sep 2013 15:22

Find Files and QS broken

Post by autocart »

create a file "New Text. File.txt"
search for it either with FF or QS -> no results

I assume it's because of the space after the (first) dot.

admin
Site Admin
Posts: 60357
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: Find Files and QS broken

Post by admin »

What search pattern did you use? Note that any spaces in a search pattern are treated as "Loose Boolean AND". To avoid that you have to quote the pattern:

Code: Select all

?"New Text. File.txt"

highend
Posts: 13274
Joined: 06 Feb 2011 00:33

Re: Find Files and QS broken

Post by highend »

Even while treating a non quoted space as a boolean AND, it should not fail when using the pattern

Code: Select all

new text.
in the gui search, or?
One of my scripts helped you out? Please donate via Paypal

admin
Site Admin
Posts: 60357
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: Find Files and QS broken

Post by admin »

I just was about to add this:

An additional aspect of this particular case is the rule that patterns ending with a dot only match filenames without extension.

Code: Select all

Query:  New Text. File.txt
Parsed: name:"*new*" AND name:"*text*" [no extension] AND name:"*file.txt*"
Hence a file "New Text. File.txt" is not found by this search.

autocart
Posts: 1246
Joined: 26 Sep 2013 15:22

Re: Find Files and QS broken

Post by autocart »

I understand.
Is this behaviour hard coded?

never mind. switching to real boolean mode (in the FF UI) is the solution [EDIT: actually it is not, see next post]
Last edited by autocart on 20 Oct 2017 07:49, edited 1 time in total.

autocart
Posts: 1246
Joined: 26 Sep 2013 15:22

Re: Find Files and QS broken

Post by autocart »

just for completeness:

the boolean mode also parses the string and interprets other chars in its own way, e.g. "(" to name just one.
therefore it might sometimes be best to quote the string, as Don suggested.

however, and here I come back to you, Don, if I quote, it seems that the algorithm compares only against the whole file name (including the extension) and not substrings of the file name.

therefore: are u in the mood, Don, to
1) give us the option in the UI to compare against either the whole file name as one whole string OR substings of it (whether quoted or not)?
2) add an option to the UI to auto-quote the string at least in the name field of the FF dialog (would make more sense if quoted strings compared against substings as well)?

Thx for reading.

Post Reply