Syntax "content:" kills the application

[ae_2020]

Hi,
just wanted to share with all of you this behavoir on Everything 1.5.0.1400a (x64).
When I type the key 'content:something', the search starts but immediately freezes, then the application closes.
This didn’t happen in the previous versions.

Any suggestion to fix it?
Thanks!

[therube]

As written, content: will start looking for content within all your files.

content:redandblue

So enter a filter before entering your content: content.

pic: feb 2025 content:redandblue

Further, you can cancel the content: search.
A search progress bar opens on the (Everything) taskbar. You can right-click that & choose, Cancel Content Search.
(Now, if you're doing a global search, it might not be that apparent that the progress bar is there, but it is.)

[horst.epp]

Searching for content is working best
if content indexing is configured for certain dirs and extensions.

[void]

Try narrowing down the file causing the issue.

For example:

*.pdf content:

*.pdf dm:thisyear content:

*.pdf dm:thisyear \downloads content:

[ChrisGreaves]

Try narrowing down the file causing the issue.

I'd like to suggest a really low-priority setting, that
... when the syntax analyzer, examining the search string, detects a 'Content:' atom, it inhibits execution of that atom (perhaps puts its addition to the parsed string in abeyance) until a primary filter such as 'name' or 'ext' or 'path' or 'dm' and so on is detected.

rephrased: 'Content:' shall NOT be the first parsed item placed in the search string.

This is almost a command to be nice to our computer drives!
Cheers, Chris

[therube]

This is almost a command to be nice to our computer drives!

There already is. It's called, nice .

[ChrisGreaves]

This is almost a command to be nice to our computer drives!

There already is. It's called, nice .

Thanks, TheRube. Nice find Cheers, Chris