How can I display properties for not content indexed files?

[aflawt]

So; normally if a property is not indexed at all, Everything reads the data from the disk for the results on the screen.

However if I index a property only for files in a specific folder (so that I can quickly sort/search in that folder), I can no longer see that property for any files outside of that folder.

Is there any way to make Everything use the index database for the available files then fill the missing ones by reading from the disk at the search time?

[NotNull]

Use the from-disk: modifier or one of it's aliases

no-indexed:
non-indexed:
not-indexed:
from-disk:
indexed:

Search properties and content on disk (not from the index) or search properties from the index.

For example:
notindexed:length:>5m

Default: Search indexed properties only. If the property is not included in the index, search the property from disk.

no-indexed:

[aflawt]

I can search but length column still stays empty. I want to display the value.

[aflawt]

Use the from-disk: modifier or one of it's aliases

For example:
notindexed:length:>5m

I can find this file by its length but I can't actually see the value. It also acts like zero when sorting.
All three results are the same file on different disks. Disk M has not indexed while other 2 have.

length.PNG

[NotNull]

Is your M:-drive online? Or said mp4 file accessible? Everything will not be able to read from disk if not.

Check - for exampe - using the following search:

Code: Select all

root:  online:

Or add online: to your search query:

Code: Select all

online:   notindexed:length:30m22

[aflawt]

Yes it is online. Otherwise, Everything wouldn't even be able to find the file by length since its properties are not indexed.

[NotNull]

Good point!

Just set up my Everything to try to reproduce this issue and indeed: same behaviour.
I have no explanation for it, nor was I able to find a workaround to display these proprties anyway.


Tested with version 1.5.0.1340a (x64) @ Win11 22H2

[aflawt]

void, can you confirm whether this is a bug or intended behavior?

[horst.epp]

If I remember correctly, that is a known problem reported by user raccoon.
I'm to lazy to find the reference.
If you index only certain files you can't read the properties of any non-indexed file.

[atiovalo]

I have this issue too with version 1.5.0.1423b.
It's a little frustrating because I've indexed a few important properties, but not on every drive, so the experience on the other drives has worsened.
I wonder if there's any fix or workaround for this issue.

[Herkules97]

Just chiming in to say I too want this. It makes it impossible to quickly add a column or to at least read from a file list not normally looked at nor indexed with the properties.
If you just want to do something small but not have to do an entire rebuild to add the files that you don't want perma-indexed anyway.
This is even more helpful if you have x files and y files where x are indexed..But you want to export all of them together with the same properties.

Now I don't remember exactly how it works, but I think there might be a way to force properties to be read..Like either CTRL+F5 or "Read Extended Information". It's not as good as the nothing-is-indexed version where the column simply loads whatever is missing as long as the column is visible.

BUT if either of those work, then that could ensure all properties are read..As you might need all columns you don't index everywhere to be visible. It could save the trouble of setting the columns up to all be visible.
Someone that already has a setup for doing both of them should test and report results, I don't currently have anything setup. I might bother trying if no one else does within a few days.