Run History Help

[void]

What is Run History?
"Everything" "Run History" is a database of how many times you have run every file or folder from "Everything".

Every time you open a file or folder the run count for that file or folder is incremented by one.

Pressing Enter from the search edit will focus the file or folder result with the highest run count.

What are the requirements for Run History?
Requires "Everything" version 1.3.3.653b or later.

How do I see the run count for an item?
Right click the result list header and check the Run Count column.

-or-

• Right click the file or folder.
• Click Set Run Count... (Run history must be enabled).
• Press ESC to close the Set Run Count dialog.

How do I change the run count for an item?

• Right click the file or folder.
• Click Set Run Count....
• Enter in a new run count.

How do I disable Run History?

• In Everything, from the Tools menu, click Options.
• Click the History tab.
• Uncheck Enable run history.
• Click OK.

Where is the run history stored?
Everything stores run history in %APPDATA%\Everything\Run History.csv (or as Run History.csv in the same location as your Everything.exe for the portable version).

How do I search for files and folders with a specified run count?
Example, search for files and folders that have been run over 100 times:

Code: Select all

runcount:>100

Run once or more:

Code: Select all

runcount:

How do I make Everything sort by Run count by default?

• In Everything, from the Tools menu, click Options.
• Click the Home tab.
• Change sort to Run Count (Descending).
• Click OK.

[hualuogeng]

Run count is a great feature !
But there is a little problem bothering me. The run count will be set as zero when i modify the file content (not file name).
Is there a way to keep the run count ? I would like not "set run count" manually every time.

[void]

Fixed for the next release.

[galneon]

He's back :>

[randfee]

run history doesn't work for me when connected to an ETP server. Is this intentional? I don't see why the ETP would only provide the results and the local "run history.csv" could be updated at the same time... or, optional, the run counter updates would be communicated to the server.

regards
randfee