It's great to see Everything now integrated with Opus, however I do have some issues in my admittedly non-standard use case.
Everything uses up a lot of RAM (450 MB minimum due to what I've chosen it to index) and so I do not keep it running in the background for the odd search I may make throughout the day. Instead, I use an AHK script to run it at will via a hotkey. With Everything (UI / indexing process) closed, only its service process remains running which only takes up ~3 MB of memory.
The disadvantage is that Everything must index for maybe 20 seconds before any results are returned (sometimes much less, depending on how many changes on disk have occurred since its last opening, but it's worth it for the extra half a gigabyte of RAM I can use for general system operation in my opinion).
That's all unrelated to Opus, but this is where the issue begins: With the Everything UI / indexing process not running, the option to search using Everything does not even show up in Opus' search field drop-down list. What if the visibility of this option was instead reliant on whether Everything is installed on the system or not? In my case, this may not even solve the issue as I have it installed portably via Scoop. I guess an Advanced preference could be added to define Everything's executable location should its default installation path not contain it.
In simple terms: I wish I could select to search using Everything via Opus and have Opus run Everything if it's not yet running. It does present a new problem: The Everything background process would not end after the search via Opus, defeating the point (in my case). Unless Opus would also terminate it after it had fetched its results... Another Advanced option?
The easiest solution is to buy more RAM. Or stick to non-Opus-integrated Everything searches via my hotkey. I do in fact have enough RAM. Even still, half a GB of memory constantly consumed by something I may or may not interact with on a given day for a handful of seconds at most doesn't sit right, hence running it on-demand.
Perhaps an Opus script could be part of the solution I'd like to see, but being unable to even select Everything as a search method likely can't overcome it.
It actually does detect it on-the-fly. A few moments after running it manually, Everything appears in the drop-down list. Also, the other Everything-related functions begin to work e.g. the - and + quick keys.
So no, it doesn't solve things really. I guess that's another compromise I could make, just always manually run it each time before I use it via Opus. I was hoping it could be automatic, i.e. when I try to interact with Everything via Opus, ideally in any way, run it if it's not running, return the results and quit. A search-once-and-quit type feature.
Although your documentation shows that Opus users should set Everything up to always run in the background, yes I would. That alone might be a small QoL improvement for anyone who hasn't or doesn't want it set up to run in the background by default, but the critical part of my wish is that after Everything results are returned, its process would also quit.
Interact with Everything via Opus -> Run Everything if it's not -> Wait for results -> Display results -> Quit Everything. (repeat)
That makes sense. Thanks for renaming the thread to clarify.
But... if it takes 20 seconds for Everything to become ready on your system each time, and you restart it for each query, wouldn't that usually defeat the point of using an indexed search? You could usually do the search normally in less time.
(500MB for the index to stay in memory also seems a good trade-off for something that's really useful, give how much RAM we have these days. My web browser's using that much and I only have two tabs open.)
It's a fair point. But I will say that if you do want Opus to search Everything, fetch the results, then quit Everything, running a second Everything search via Opus moments later will only take ~1 second since the index has not changed much. It's only the first search which may take 20 or so seconds (depending on how long it's been since I last used Everything).
For the first Everything search, perhaps (I've not used Opus' own search much to be fair, mostly FAYT). But consecutive Everything searches would probably be faster even when launching it, refreshing the minor index change, and returning the results (then exiting).
The main reason I use Everything is because of its speed, control over what gets indexed, and ability to use regex to find things across my entire system. Opus' search can do regex I think, but it only leverages Windows' search index I believe, which isn't as good. Maybe I should play around with Opus' search more.
I could even just stick to using Everything directly I guess, but being able to save the search offline you could say via Opus' stored queries goes quite nicely with this run-once workflow.
Finally, something which you may want to look into: The search bar greys out when in File Collections. It makes sense if it's not yet possible to search your collections, but if you want to perform A Global Everything search instead, there is no access to it in this particular scenario. I guess it will probably be resolved if / when collections can be searched in the future.
Apologies to all for my deeply offensive statement. I will now retreat to the caves and reflect upon what I have done. Sorry! I honestly didn't think of it like that. I just know I've never liked Windows' search so much.
I will have to look into that too. Thanks for pointing it out. There's a lot of Opus features I've noticed but not yet taken the time to learn, mostly because of no need or ignorance. Some, like this one, I've forgotten even existed.
Not quite the search-once-and-quit functionality I was looking for, but this is definitely a convenient addition in case I open and close Everything externally so it's no longer running. I will probably just let it continue to run in the background, or make some naive script to quit it every so often if the process' host is dopus.exe.
One minor issue(?) I just noticed is that if Everything isn't running and you have an "Everything search results for ..." tab open, pressing back on this tab to return to the folder which was searched also launches Everything, which doesn't seem to help in any way, although it would mean that Everything is already running and indexed before any new search, whenever that may occur. I just would've expected Opus to automatically launch Everything only when initiating a search. It probably makes sense for the vast majority of users that this is a non-issue. I guess I'll just get used to it.
