Global and Per-Instance Configs [Solved]

[postfreq]

I'm trying out a setup where I have several instances for specialized tasks with -instance and they all have different config files, which is great for options that differ, but not so much when I want to change something across all instances. Is there a way to configure for all instances and for specific instances as needed?

[therube]

(In the Mozilla world, that's called, user.js.)

[NotNull]

With Group Policies (part of Everything 1.5), you can force certain settings over all Everything instances.


Other than that, you could start (through shortcut or script) all instances with a comnmand similar to the following:
"c:\path to\everything64.exe" -instance "instance name" -add-config "X:\some folder\global.ini"

This would load all ini settings from global.ini each time this instance gets started.
Syntax of global.ini is the same as everything.ini, but just containing the global settings.

This also requires Everything 1.5.

[postfreq]

-add-config seems to be exactly what I was looking for, NotNull, thank you!

[therube]

With Group Policies

Oh, so that is real Group Policies.

-add-config <filename>
Load a configuration file from the specified filename.
Restarting "Everything" may be required to apply some settings.

-install-config <filename>
Loads additional settings from the specified ini file.
The specified ini file will override any existing settings and a new Everything.ini is saved to disk.

Explain the differences here, if you would.

And what -install- takes effect before Everything is loaded?
And -install- actually changes Everything.ini (rather then only apply those changes in RAM, leaving Everything.ini unchanged).

And what, -add- can work interactively (at least for some settings, without restart)?

[void]

Both do the following:

Load the settings from the specified file and overwrite your existing settings.



-install-config

Returns immediately.
Does not start a new instance of Everything.
Used by the installer.

Do not use if Everything is already running.
If Everything is already running, your newly added settings will be overwritten when the existing instance exits.



-add-config

If Everything was not running:
Start a new instance of Everything.
Add your settings before any UI is shown.
No restart is required.

If Everything was already running:
Send the -add-config command line option to the existing instance and return immediately.
The existing instance will add your settings and continue running.

Some settings will require a restart if Everything was already running:

Everything.exe -restart

And what -install- takes effect before Everything is loaded?

Yes.
Everything should not be running when using -install-config

And -install- actually changes Everything.ini (rather then only apply those changes in RAM, leaving Everything.ini unchanged).

Yes.
The changes are saved to your Everything.ini before the call returns.
-install-config will return immediately.

Technically, -add-config also flushes your changes to disk.
(this might happen after the -add-config call returns)

And what, -add- can work interactively (at least for some settings, without restart)?

Yes most settings will work interactively without a restart.