Persistent custom columns

[win32]

How can I add the following column by default to my home view?

Code: Select all

add-col:c c:=if($daterun:,$daterun:,$datemodified:)

If I add a persistent c column, it's empty by default, because there is no way to save the formula
Couldnt find a setting in the ini file.
Defining it at autoconf doesnt seem to work
/search command works, but I would rather the search field to be empty, also I columnC needs to be my sort column

Seems like there should be way I am somehow missing.
===========================
Parenthetically, I dont quite understand (surprised actually) how Everything does fast sort on compound columns like that. Ok both fields are indexed, a mergejoin is possible walking through the indexed fields, but Everything is also quite fast in a column like this add-col:c c:=eval($daterun:*$datemodified:) What sorcery is this?
If I do the same in a custom property, unsurprisingly querying is very slow unless I index it first.

[void]

How can I add the following column by default to my home view?

Everything isn't really designed to do this yet.
Custom columns are slow.
Custom columns are temporary in Everything 1.5.
I will consider more permanent custom columns for Everything 1.6 as they are proving to be rather useful.

One way to do this now is with filters.
Create a filter under Search -> Add to filters...
Set your filter search to add your custom column:

add-column:...

You can add this to your Everything filter or you can set your default filter under Tools -> Options -> Home -> Filter.

If I add a persistent c column, it's empty by default, because there is no way to save the formula
Couldnt find a setting in the ini file.
Defining it at autoconf doesnt seem to work
/search command works, but I would rather the search field to be empty, also I columnC needs to be my sort column

I will look into a simple ini option to set the default column formulas and labels.
Thank you for the suggestion.

[win32]

Thank you for the reply, I understand the performance issues.
The saner way would be, I thought in the OP, to create a custom property with the said column and index it. But I then noticed it's not possible to use any such syntax in custom properties, to create really custom properties. And It would need some datatype defintion anyway, so I was wrong.