Adding instance_name=test-%USERNAME% to Everything.ini gives you an expanded "Everything-test-<username>.ini" (test-JohnDoe.ini), but the database name is "Everything-test-%USERNAME%.db".
That might very well be intentional (why create multiple databases for basically the same INI file? (*) but maybe it's a little oversight (although Everything's/void's track record suggests otherwise). Just wondering/reporting here.
Extra question: what is the intended use for this instance_name= entry? First thing that came to mind is a corporate environment with locked down settings, but there are probably others. (a documentation-, help- and forum-search didn't give me much information on this subject)
(*) An Everything.ini that includes instance_name=test will create Everything-test.ini, which contents are that of Everything.ini (missing INI-entries will have their default value).
While that Everything instance running, one can change settings. After closing and restarting Everything all settings are back to their original state (i.e. like those in Everything.ini).
So basically you have a read-only Everything.ini.
Variable expansion in instance_name (INI entry)
Re: Variable expansion in instance_name (INI entry)
If you interactively change instance_name=, I suppose that acts as a File | Save as... like feature - for Everything-<newly named instance_name>.db, allowing you to save current settings under a new name, without affecting the initial .db.
Re: Variable expansion in instance_name (INI entry)
This is an oversight.Adding instance_name=test-%USERNAME% to Everything.ini gives you an expanded "Everything-test-<username>.ini" (test-JohnDoe.ini), but the database name is "Everything-test-%USERNAME%.db".
The ini setting "instance_name" needs updating. In Everything 1.3, the Everything.ini and Everything.db filenames did not change with different instance names.
Please use the -instance command line option.
This will expand the %USERNAME% variable on run.
It was just another way to set the instance name, as an alternative to the -instance command line option.Extra question: what is the intended use for this instance_name= entry? First thing that came to mind is a corporate environment with locked down settings, but there are probably others. (a documentation-, help- and forum-search didn't give me much information on this subject)
Shortcuts did not have to be modified, useful for other apps that may start Everything for IPC, instance name could be copied with copying the Everything.ini.
This is a bug, would should happen is Everything should load the correct Everything-test.ini after loading Everything.ini.(*) An Everything.ini that includes instance_name=test will create Everything-test.ini, which contents are that of Everything.ini (missing INI-entries will have their default value).
While that Everything instance running, one can change settings. After closing and restarting Everything all settings are back to their original state (i.e. like those in Everything.ini).
So basically you have a read-only Everything.ini.
I've added this to my "Things to fix" list.
Re: Variable expansion in instance_name (INI entry)
Thanks for explaining!
As far as I'm concerned: no hurries, no worries; I was just wandering around in the "darker" corners of Everything
As far as I'm concerned: no hurries, no worries; I was just wandering around in the "darker" corners of Everything