NotNull wrote: Tue May 23, 2023 9:13 pm
I think that what you (@GSD) try to accomplish should be very well doable with IndexThis as a base.
Some pointres:
- Don't put the ini file in %temp%, but in the IndexThis folder.
- Check if an TEMPINDEX instance already exists. If not: "build" the needed ini-file (=current code). If not: same run commandline with added add-folder / -add-ntfs-volumes command-line option
That way one TEMPINDEX instance can contain multiple folders/drives. But only on Everything 1.5.
(and probably without a need for a -filters-file or -bookmark-file command line option)
Yes, this is 100% doable with some powershell, but i feel that the revised "-add-filters"/"-add-bookmarks"(rather than "-filters-file"/"-bookmark-file"), plus the "-ro" read-only option, could be good additions and may facilitate other use cases.
That beeing said, I like your suggestion, but if I'm going to do the powershell dance, might as well do it all the way and not mix folders in the same DB. The way I have it architected in my head is, using a dedicated "TEMPINDEX" folder containing a symlink to everything64.exe:
- delete all files in "TEMPINDEX", except said symlink
- generate random short string $string
- copy appropriate Everyhting.ini, Filters.csv etc. to TEMPINDEX\Everyhting-$string.ini, Filters-$string.csv etc.
- run TEMPINDEX\Everyhting64.exe -no-db -instance "$string" -folders ...
So it's not that I can't achieve my end result, it's that I think temporary, read-only instances templated from existing configs would be a much more elegant solution, and I'm sure smarter people would find better uses for them
Thank you for taking a look!