XYplorer Beta Club

highend wrote: ↑19 Aug 2021 13:00 Don't think that this will happen

I can live with it and your script
Btw using the SDK you don't need a Everything DLL
only the very first versions of TC integration had it.
TC just allows you to also submit raw Everything syntax and doesn't implement all of its many function in TC GUI.

OK, not now.

admin wrote: ↑19 Aug 2021 09:00 What do you mean by out of reach? Of course, I could emulate that script within the XY code. I already support External Copy Handlers.

The "wish" for something like "XYplorything" was just my way to praise my two most important daily Windows tools.

The integration provided by this script (and its ancestor) is perfect for me.

v0.8 was released

It has a nice icon and remembers search terms (with a drop-down field on the right side of the input box) as well

22.10.0005+ is required for that functionality^^

The script gets better which each version.
Thanks for updating it

Hi highend,

thanks for the update.

Initially I didn't see the icon, but removing the trailing "\" (<ctrl>+<p>) from EverythingPath fixed it.

line 100

$everythingPath = trim(resolvepath($everythingPath, "\", "R"));
---------------------------------------------------^

$everythingPath = trim(resolvepath($everythingPath), "\", "R");
---------------------------------------------^

Fixed and reuploaded

jaywalker32 wrote: ↑17 Aug 2021 11:32 Is there a way to call the Everything.exe ui via a script and get the search results on exit, and use THAT to create the paper folder?
Since on the UI you can modify the search query and fine tune the result set in real time.

This was already discussed in this thread and Highend even provided a working script using the Everything GUI.
I also said in this thread that you have the full Everything syntax and functions in the normal Everything script.
No real need for the Everything GUI.

v0.9 released

I've added two more content search types I normally need utf8content search myself...

highend wrote: ↑21 Aug 2021 13:40 v0.9 released
...

Users should be aware that using uc: or ac: without further modifiers like pathnames or filenames
they may get an hanging XY because Everyting will search all files for content which can take much to long.
Personaly I only use indexed content searches which is as fast as all Everything file searches.

I suggest to not add more specific options to the script.
Users should read the Everything help about search syntax, functions and modifiers to understand the dependencies.
They also can define macros to shorten long search commands.

That's a valid point. I personally only ever use utf8content: with e.g. ext:<some extension> so I don't suffer from that limitation
I've withdrawn that version...

But I've posted a new v0.9...

It adds the ability to show defined macros. See the screenshot in the first post.
By default that feature is set to false^^

I do not do any splitting into multiple lines if there are too many macros defined atm, though.

That new version 0.9 is much better.
There is one more enhancement I suggest:
You have not only filter macro names but also search macros in Everything 1.5.
This macros are stored in the file macros.csv and defined in the GUI.
See the following URL for details
https://www.voidtools.com/forum/viewtop ... 5397#macro
Very useful, I type tags:mytagname for example to search for my property indexed ADS tags.
This macros can also be used in your script.

One more comment about the usage of files like filters.csv, macros.csv and other config files of Everything.
Currently the script searches them in the path for es.exe.
This is true for me uising a portable Everything installation and also stored es.exe in this Everything dir.
Other users may use the installer of Everything which puts the files somewhere in appdata.
May be the script should have a config item "PathToFilters" with a default of the path to es.exe.

The problem with showing too much information is: space. Atm input() with style "s" can't be made larger...

I'll implement splitting of macros (for multiple lines if there are too many) first

v0.9.1 released

I've condensed the output for a moment and got rid of two additional lines in the input window...

Additional .ini settings: This leads to an (example) output like this: Filter macro(s) consists of generic macros (e.g. the default ones) and additional line(s) for user defined ones (with the {name}<{identifier}> schema)