Quote:
Originally Posted by KevinH
So to expand on this more by thinking out loud (so to speak):
We would store the number of replacements made for every replace all invoked by a "RunSavedSearchReplaceAll" command.
...
Is this enough logic to do what you want?
Should the two new commands also set the number of last search replacements made if run?
|
That would be perfect for my requirements assuming that if the second search is not run, the number of results is not reset to zero. One example of how I use this would when removing a lot of the crud from Vellum created ebooks. I have a basic find/replace set that is specific to cleaning up an azw3 to epub extraction. If that set does not find/replace anything, a second find/replace set is run that is specific to Vellum cleanup on an epub original. If either of those two searches makes a replacement, a third set is run to finish the cleanup removing common items.
Currently, I run saved search 1, look at the results and if 0, run saved search 2. If both 1 and 2 make no changes, search 3 is not run otherwise it is run.
I have a few other search sets that I use in a similar fashion. Rather idiosyncratic and I'm still not sure how many other people would make use of this capability.
Another suggestion would be to have the Automation List preference also remove the Quick Launch icons when disabled.