Anomaly when searching Content: ????

[ChrisGreaves]

Untitled.png (70.11 KiB) Viewed 1764 times

Yes, I am still playing around with Content:
I had previously tried

Code: Select all

*.doc content:bayley

and thought to try with a content different from my own street address (15,134 objects).

I typed as far as

Code: Select all

*.doc content:

and Everything started out with its "Querying ..." quicker'n blink.

What can this mean?

Is Everything looking in every one of 15,293 DOCument files on my system, opening each one, while I stare out of my windows looking for inspiration?

I could understand it (almost) if by the time I reached

Code: Select all

*.doc content:t

and on recipt of the "t" following the colon, Everything hitched up is pants and said "Oh! NOW I have a job to do", but then, surely, once I got as far as

Code: Select all

*.doc content:te

Everything would have to backtrack and re-inspect those half dozen files that had satisfied

Code: Select all

*.doc content:t

(signed) "Puzzled Beginner" of Bonavista.

[void]

Everything searches as you type.

This means, as soon as you type: *.doc content:
Everything will start searching for your doc files that contain any content.

As soon as you type in the t in: *.doc content:t
Everything will stop the previous content search and start the new one.

The previously read content will still be in cache so this is typically quick without re-reading content from disk.



The STOPPED text shown in the status is the index update status.
Everything will not detect new file changes when updates are stopped.
To update your indexes:

• From the main Index menu by checking Update indexes.

[ChrisGreaves]

Everything searches as you type.

This sounds like Everything (sneakily) taking every opportunity to shave seconds of the production of Results List, and who cares if the laptop fan starts whirring again (grin)

As soon as you type in the t in: *.doc content:t Everything will stop the previous content search and start the new one.

same comment as above.
But also: (Curiousity value only) Does Everything open every file, or does it ignore file-size-bytes = zero?

The previously read content will still be in cache so this is typically quick without re-reading content from disk.

"cache" in this case being Windows "disk buffering" in RAM, correct?

The STOPPED text shown in the status is the index update status.
Everything will not detect new file changes when updates are stopped.

I shall ponder this. I have not yet mastered "Result List" and all its content. On my ToDo list.
I had thought that "STOPPED" meant that the user had interrupted the search.
I'm happy to say that I have much to learn.

Thanks, Chris.

[void]

This sounds like Everything (sneakily) taking every opportunity to shave seconds of the production of Results List, and who cares if the laptop fan starts whirring again (grin)

There is a quirky allow_open_quote ini setting.
When disabled, Everything will only search content when there's a starting and ending double quote (")

For example, you type in the following search:

*.doc content:
(this matches all *.doc files, content: is ignored)

*.doc content:"
(this matches all *.doc files, content:" is ignored)

*.doc content:"t
(this matches all *.doc files, content:"t is ignored)

*.doc content:"te
(this matches all *.doc files, content:"te is ignored)

*.doc content:"te"
(now, since there's an ending ", Everything will start your content search)

But also: (Curiousity value only) Does Everything open every file, or does it ignore file-size-bytes = zero?

Everything will open every file.
Zero bytes or not.

"cache" in this case being Windows "disk buffering" in RAM, correct?

Yes.

I had thought that "STOPPED" meant that the user had interrupted the search.

Please make sure Index -> Update Indexes is checked.

[ChrisGreaves]

But also: (Curiousity value only) Does Everything open every file, or does it ignore file-size-bytes = zero?

Everything will open every file.
Zero bytes or not.

I have the curiosity of a four year old, so to "Everything will open every file. Zero bytes or not." I respond "Why?"

On the surface I would think that a size of zero (bytes) means no content at all :scratchhead:

I had thought that "STOPPED" meant that the user had interrupted the search.

Please make sure Index -> Update Indexes is checked.

It is indeed (I started off looking in Tools, Options, Index ...) but I am glad that you asked.
I have been resurrected as "Administrator" and must go fix that again.(Later: Fixed!)
Thanks void
Chris

[void]

Zero bytes or not." I respond "Why?"

An iFilter might return content for zero bytes. (unlikely)

!content: will return files/folders with no content.


Loading the iFilter will have a small performance hit.
If you have many zero sized files, consider using size:
For example:
*.doc size: content:"te"
size: on its own will match any files/folders with a non-zero size.

[ChrisGreaves]

An iFilter might return content for zero bytes. (unlikely)

Beginner here: Is an IFilter something like this definition from WikiPedia, or is it a local-to-Everything Filter that makes use of exiting Indexes?

I read iFilter integration and checksum search too.

Thanks
Chris

[horst.epp]

An iFilter might return content for zero bytes. (unlikely)

Beginner here: Is an IFilter something like this definition from WikiPedia, or is it a local-to-Everything Filter that makes use of exiting Indexes?

I read iFilter integration and checksum search too.

Thanks
Chris

An iFilter is what the WikiPedia says.
Its installed on your OS and is not related with Everything.
You can query an existing Windows index by using the si: function in Everything.
Windows indexing makes use of the installed iFilters and should be used for large amount of content indexing.

[ChrisGreaves]

An iFilter is what the WikiPedia says.
Its installed on your OS and is not related with Everything.
You can query an existing Windows index by using the si: function in Everything.
Windows indexing makes use of the installed iFilters and should be used for large amount of content indexing.

Thanks Horst. My understanding has increased.
I now have the impression that
(a) Everything looks after Windows iFiltering so that I don't have to
(b) iFiltering affects the elapsed run time of searches and
(c) I might be responsible in asking Everything to make Use of iFilters, but that becomes a user option of some sort; a decision to ask Everything to bring in the heavy guns.
Cheers, Chris

[ChrisGreaves]

size: on its own will match any files/folders with a non-zero size.

Duly noted; thanks Void.