Something like:
Code: Select all
Everything64.exe -instance "EXAMPLE" -config Test-config.ini -filters-file Test-filters.csv -bookmarks-file Test-Bookmarks.csv -plugins-file Test-Plugins.ini
Code: Select all
Everything64.exe -instance "EXAMPLE" -config Test-config.ini -filters-file Test-filters.csv -bookmarks-file Test-Bookmarks.csv -plugins-file Test-Plugins.ini
Everything will only save your filters/bookmarks if modified.is to keep Everything's standard behavior of saving the settings file on each window close. Correct?
Ah, that makes sense. And I see what you mean about sync between multiple instances. Either they are read-only or the user would have to be aware that modifying filters/bookmarks is akin to manually editing the respective files and requires restarting the other instances in order for the changes to apply(I presume that Everything is not monitoring those real-time). This didn't occur to me beacause, in my thinking, it was all combined with that read-only parameter I'm proposing in my other post. Perhaps I should have combined my two suggestions. Symlinks did occur to me, but they wouldn't help with what I'm trying to achieve, which is to create on-the-fly, read-only, temporary instances based on existing instance configs as templates.
Code: Select all
Everything64.exe -instance "TEMP" -add-config "Everything-music.ini" -add-filters "Filters-music.csv" -add-bookmarks "Bookmarks-music.csv"
Got it!void wrote: ↑Thu May 25, 2023 10:27 am Unfortunately, -add-filters and -add-bookmarks wouldn't work because Everything allows duplicated filter/bookmark names.
Everything automatically renames duplicated filter names.
-add-filters / -add-bookmarks would always append to your existing filters/bookmarks.
Never overwriting them which is expected.
I asked about -add-filters and -add-bookmarks in reference to the existing -add-config, but what I'm actually after is what -set/-copy would imply semantically. So those would be excellent. Thank you, Sir!