Are there any constants I can give to the "type:" function?
I thought maybe I could use the built-in types but when I put the following strings in the Everything Search window, or use them in Everything_SetQuery(), I get peculiar results:
type:Everything gives nothing
type:Picture gives nothing
type:audio gives an incomplete mixture of audio and video files
The best one is
type:Executable ... which gives only .JAR files!
What's up?
Thanks!
- Vince
How does the "type:" function work?
Re: How does the "type:" function work?
Yep, type: is an odd one & I'm not sure just what is going on?
Typically you would think of type: being a files "extension", typically whatever follows the final "dot" (.) in a filename.
Yet type:abc returns odd results:
The duplicated names are OK, they're in different directories, but the Sym* entries...?
Typically you would think of type: being a files "extension", typically whatever follows the final "dot" (.) in a filename.
Yet type:abc returns odd results:
Code: Select all
prefs.js.abc
sessionstore.json.abc
sessionstore.json.abc
SymUIHlp.dll.29F27B3A_9E28_441B_ABC4_68298CAD2287
SymUIHlp.dll.29F27B3A_9E28_441B_ABC4_68298CAD2287
Re: How does the "type:" function work?
Type function - it's not about file extension, but such type: image, audio, document - with me or not until the end of this works is correct command
wait what David would say - more of a type function here
Code: Select all
type:audiowait what David would say - more of a type function here
Re: How does the "type:" function work?
Type: matches on the Type column, which appears to be the same as the Type column in Windows explorer (set by Windows as a description of the .xxx suffix of a file name).
Type: does a partial string match, so app will match "application" and "application extension" (.exe and .dll) where ext matches "application extension" (.dll)
Type: does a partial string match, so app will match "application" and "application extension" (.exe and .dll) where ext matches "application extension" (.dll)
Re: How does the "type:" function work?
Thanks! That seems to be consistent behavior.froggie wrote:Type: matches on the Type column, which appears to be the same as the Type column in Windows explorer (set by Windows as a description of the .xxx suffix of a file name).
And it explains how "type:Executable" turns into .JAR files. The default value in HKCR\jarfile has the data "Executable Jar File".
- Vince
Re: How does the "type:" function work?
(
So last night it hit me, that there exists the ext: function, so what I described above would not be correct.
> Type: matches on the Type column, which appears to be the same as the Type column in Windows explorer
Yes, that makes more sense.
(Not that I've ever paid any attention to the 'Type' column in Windows Explorer before
.)
)
So last night it hit me, that there exists the ext: function, so what I described above would not be correct.
> Type: matches on the Type column, which appears to be the same as the Type column in Windows explorer
Yes, that makes more sense.
(Not that I've ever paid any attention to the 'Type' column in Windows Explorer before
.))