xplorer2 v6.208 BETA

[nikos]

Not many changes, it should be a bit faster inserting ES results (you will only see a difference if there are thousands of hits)
https://www.zabkat.com/test/xplorer2_se ... t_beta.exe

thanks for any feedback!

[Kilmatead]

it should be a bit faster inserting ES results (you will only see a difference if there are thousands of hits)

Curiously enough, I was playing with that while you were off scoring weed, and a simple scrap search of

es:ext:exe;dll !\windows

resulted in around 10,000 hits, which populated the frame in ~7 seconds. This version populates in ~5 seconds. Comparing apples to oranges, but dragging the same results from ES itself into the frame populates in about 2 seconds. Curious.

Since I'm the only one likely to ever use es: in scraps, I'd like to request that instead of results being cumulative for repetitive searches, it would be more practical if the frame was auto-cleared first - given the CLI nature of invoking searches, it's faster to append "extra searches" - or re-editing existing syntax - right in the CLI itself and start anew, clean. Just my few cents, as that's how the original behaves, and it's ergonomically consistent.

Also, ironically, since it CAN take more than a few seconds to populate, I'd expect to see the numerical count incrementing in the status bar (gives one a better sense that maybe the search got carried away with itself - your little "in progress" animation is not overly informational).

And yes, I'm aware of the irony in complaining that it's not fast enough while asking for a feature which would presumably slow it down. What can I say, I'm unbalanced that way (and, possibly, a few other ways).

(But if you're grumpy 'cause your weed-deal fell through, and are not so inclined toward my happiness, I will content myself with the 2-second gain and bubble my bong softly into the aether cursing you in a rather surprisingly relaxed and mellow manner, weeping and pining remembering Bob Weir sadly passed away just last month.)

[nikos]

your wish is my command

ps. inserting via drag-drop is faster than search because (a) x2 is pumping messages (b) it must parse each path returned by ES

[Kilmatead]

...because (a) x2 is pumping messages (b) it must parse each path returned by ES

Yeah, I know... I did say "comparing apples to oranges". I just thought it was an interesting metric.

For those in the audience who are thinking that if the whole point of using ES is meant to give "instant" results, and 5-seconds doesn't really sound instant, bear in mind that doing the same search using the old fashioned "choo-choo train method" over 5 drives (mixed SSD & spinning-rust) and a million files (give or take), takes 125.344 seconds, or a bit over 2 minutes.

So, while the search itself is indeed relatively instant, the extra 5 seconds of form-population-time (to render 10,000 results) is negligible, if slightly longer than strictly "instant". Smaller (and more practical) searches (of under 500 results) will appear instantly.

[nikos]

of course finding the correct query string to search for in Everything will take you a couple of minutes, then the search is "instant"

[Kilmatead]

And using a GUI to manoeuvre through layering a few AND/OR/NOT rules together (properly) doesn't take time?

It's like the satisfaction-quotient you get from researching and finally figuring out a decent regular-expression: Yes, it took you 10 minutes to piece it together and test it out on a regex site, but hey, you earned it in the end and the results feel, somehow, more "honest" for the effort invested.

I mean, sure, you kids and your fancy horseless-carriages and infernal flying contraptions may get there faster, but there's a lot to be said for the fertilising contributions of gracing the world with "miles and miles of little brown piles".