Where are the CSV and DB files gone?

[NotNull]

When I start Everything with a command similar to the following:

Code: Select all

"c:\Program Files\Everything 1.5a\Everything64.exe" -instance "something" -config "t:\instance1\whatever.ini"

I can set Run Count for a file or create a filter or open a file, but after exiting, the CSV files that should contain this information are not on disk anywhere.
Same goes for the .db database file. Next time I run this instance, Everything has to start scanning from scratch.


The "whatever.ini" is saved in the indicated location though.

EDIT: v1307

[void]

Thank you for the issue report NotNull,

Everything is trying to write these CSV/DB files to C:\Program Files\Everything 1.5a
Everything will not have permission to write to this folder.



What is happening:

On Everything startup, Everything will load the following ini files (in order):
<same-location-as-your-Everything.exe>\Everything-<instance-name>.ini
<everything-settings-location>\Everything-<instance-name>.ini

<everything-settings-location> will be either:
C:\Program Files\Everything 1.5a
or
%APPDATA%\Everything

%APPDATA%\Everything is used if app_data=1 is in <same-location-as-your-Everything.exe>\Everything-<instance-name>.ini



Everything will not have permission when writing to c:\Program Files\Everything 1.5a
There is no "unable to write" warning because a custom config is used.

For this to work correctly, there needs to be a Everything-something.ini in the same location as your Everything.exe with app_data=1 set.

Everything-something.ini:

Code: Select all

[Everything]
app_data=1

The app_data setting in -config "t:\instance1\whatever.ini" is ignored.



What I will do for the next alpha update:

Change Everything to load the following ini files:
<same-location-as-your-Everything.exe>\Everything-1.5a.ini
<same-location-as-your-Everything.exe>\Everything-<instance-name>.ini
<everything-settings-location>\Everything-<instance-name>.ini

This way, if your Everything-<instance-name>.ini is missing, Everything will just use the default ini which will most likely have app_data=1 set.

[NotNull]

Change Everything to load the following ini files:
<same-location-as-your-Everything.exe>\Everything-1.5a.ini
<same-location-as-your-Everything.exe>\Everything-<instance-name>.ini
<everything-settings-location>\Everything-<instance-name>.ini

<same-location-as-your-Everything.exe>\Everything-1.5a.ini ...
.. or Everything.ini for non-alpha versions / when running the alpha without instance
(in the 0.1 percent chance you didn't think of it already )

BTW: I was just experimenting; no urgent need for changes on my end. A portable Everything makes much more sense in cases like this.

[void]

Everything 1.5.0.1310a improves loading config.

Everything will now load the following configuration files (in order):
<same-location-as-Everything.exe>\Everything-1.5a.ini (or Everything.ini if the alpha instance is disabled)
<same-location-as-Everything.exe>\Everything-<instance-name>.ini (only if a custom instance is used)
<settings-and-data-location>\Everything-<instance-name>.ini (if app-data is enabled)

[void]

Everything 1.5.0.1314a will no longer load the root Everything.ini without an instance name.

Everything will now load the following configuration files (in order):
<same-location-as-Everything.exe>\Everything-<instance-name>.ini (only if a custom instance is used)
<settings-and-data-location>\Everything-<instance-name>.ini (if app-data is enabled)

The loading of <same-location-as-Everything.exe>\Everything-1.5a.ini (or Everything.ini if the alpha instance is disabled) was causing unexpected results during testing.

I want to call Everything.exe -instance "fresh instance" and be certain that I get a fresh instance.