ext:xls should also list xlsx files, right?
ext:xls should also list xlsx files, right?
Hi,
When I type ext:xls, shouldn't the files with xlsx extension also be listed?
Because the xlsx extension has the word xls in it.
When I type ext:xls, shouldn't the files with xlsx extension also be listed?
Because the xlsx extension has the word xls in it.
Re: ext:xls should also list xlsx files, right?
Everything matches the whole extension with ext:
Please separate multiple extensions with a semicolon (;)
For example:
ext:xls;xlsx
Please try extension: for partial searches:
extension:xls
-or-
.xls
Please separate multiple extensions with a semicolon (;)
For example:
ext:xls;xlsx
Please try extension: for partial searches:
extension:xls
-or-
.xls
Re: ext:xls should also list xlsx files, right?
Thanks void,
The .xls option is also nice, but extension: met my needs directly.
The .xls option is also nice, but extension: met my needs directly.
Re: ext:xls should also list xlsx files, right?
Consider to replace:
ext: for partial searches
and
extension: for "matches the whole extension".
I too expected (intuitively) that ext: will make partial searches of extensions,
and to use ext:"xls" for escaping xlsx extension.
ext: for partial searches
and
extension: for "matches the whole extension".
I too expected (intuitively) that ext: will make partial searches of extensions,
and to use ext:"xls" for escaping xlsx extension.
I found that "extension:" doesn't support it (;) yet.Please separate multiple extensions with a semicolon (;)
Re: ext:xls should also list xlsx files, right?
ext: is designed to match the whole extension.
Users will not want ext:c to match cpp files.
I will consider swapping ext: and extension:
I will consider accepting semicolon (;) lists for these types of search functions, where a ; in the property text is uncommon.
(users could always escape a literal ; with ";")
Thanks for the suggestions.
For now, please consider subexpressions:
extension:<jpg|png>
Users will not want ext:c to match cpp files.
I will consider swapping ext: and extension:
Most search functions that take a single string parameter do not support ; lists.I found that "extension:" doesn't support it (;) yet.
I will consider accepting semicolon (;) lists for these types of search functions, where a ; in the property text is uncommon.
(users could always escape a literal ; with ";")
Thanks for the suggestions.
For now, please consider subexpressions:
extension:<jpg|png>
Re: ext:xls should also list xlsx files, right?
Why do you think so.
ext: can/should behave like the other "columnName:" search functions.
This reminds me that there is a column called "Extension", so that "extension:" should behave like a "columnName:" search function.
Maybe you can suggest a more intuitive syntax than wfn: to make ext:c match only c files. I suggested ext:"c", but maybe you can suggest something better.
Re: ext:xls should also list xlsx files, right?
Bro, there is nothing wrong with how ext: works. It is also a core component of how all other Everything features work, from Filters to Index Exclusions. ext: needs to be wholeword and not a partial substring match.
You have other options at your disposal, but most of your posts read as blatant and patent bellyaching for the past week. I do not understand why. This is a technical forum and the users of Everything are technically inclined, and where you find inconsistency you will also find necessity, context and obvious patterns of common use. Why are you fighting?
If you want ext: to behave like extension: then type the following macro definition command into your search bar and hit enter. But if your intent is to inflict this change upon me and everyone else... No. Just no.
/define ext=extension:
You have other options at your disposal, but most of your posts read as blatant and patent bellyaching for the past week. I do not understand why. This is a technical forum and the users of Everything are technically inclined, and where you find inconsistency you will also find necessity, context and obvious patterns of common use. Why are you fighting?
If you want ext: to behave like extension: then type the following macro definition command into your search bar and hit enter. But if your intent is to inflict this change upon me and everyone else... No. Just no.
/define ext=extension:
Re: ext:xls should also list xlsx files, right?
Take it easy. I'm just saying what I think is the right thing to do, based on what I see at that moment. This could be an initial view, and I could very well be wrong. No need to be angry about it.
How can I view and edit all these macros afterwards?/define ext=extension:
Re: ext:xls should also list xlsx files, right?
The searchbar command /define will briefly show the names of all defined macros in the statusbar.
The searchbar command about:ini will open an Explorer window to your Everything settings files, including Macros csv.
A search for macros csv will show your macros file(s) which can be previewed with Alt+P. A Macros GUI is on the to-do list.
The searchbar command /undef macroname will remove previously defined macro.
Re: ext:xls should also list xlsx files, right?
Everything 1.5.0.1331a adds semicolon (;) delimited list syntax support to all string search functions.
For example:
extension:jpg;png
name:notepad.exe;explorer.exe
artist:jane;john
Use double quotes to escape a literal ;
For example:
extension:";"
name:"file;name;with;semicolons.txt"
For example:
extension:jpg;png
name:notepad.exe;explorer.exe
artist:jane;john
Use double quotes to escape a literal ;
For example:
extension:";"
name:"file;name;with;semicolons.txt"
Re: ext:xls should also list xlsx files, right?
Thank you for this implementation!
However ...
However ...
Code: Select all
extension:jpg;png does not work - please check
ext:jpg;png works
ext:";" ) different search result -
extension:";" ) please check
Re: ext:xls should also list xlsx files, right?
@void, does this affect the following example as given on this post...
path:"C:\Path1\;C:\Path Two\;D:\Media\" .csv
Re: ext:xls should also list xlsx files, right?
Thank you for the issue report tuska,
Does the following search show the correct results:
::extension:jpg;png
::extension: will bypass any macros.
Could you please send debug logs when performing an extension: search:
These functions will handle ; on their own.
Functions that accept lists parameters:
childfilelist:"file1.txt";"file2.txt";"file3.txt";...
filelist:"file1.txt";"file2.txt";"file3.txt";...
fullpathlist:"file1.txt";"file2.txt";"file3.txt";...
ext:jpg;png
You can use ; or | with these functions.
These functions will eat the |
| doesn't need to be escaped with double quotes.
; or | is treated as OR.
These functions match the whole filename / extension.
I have deliberately made content search functions not support lists.
You will need to use subexpressions for content search functions, eg: content:<abc|123>
path: is a search modifier and is not needed in that search.
For example:
path:"c:\windows;c:\program files"
is the same as
"c:\windows;c:\program files"
Everything is smart enough to know ; followed by a absolute path should be treated as a separate path.
So in short, path:"C:\Path1\;C:\Path Two\;D:\Media\" will behave the same.
Maybe you have a macro that is overriding this search function?extension:jpg;png does not work - please check
Does the following search show the correct results:
::extension:jpg;png
::extension: will bypass any macros.
Could you please send debug logs when performing an extension: search:
- In Everything, please clear your search.
- From the Tools menu, under the Debug submenu, click Start Debug Logging.
- Copy and paste the following into your search box:
extension:jpg;png - From the Tools menu, under the Debug submenu, click Stop Debug Logging.
---this will open your %TEMP%\Everything Debug Log.txt in Notepad--- - Could you please send this file to support@voidtools.com
No, there's a few functions that take lists as parameters.@void, does this affect the following example as given on this post...
path:"C:\Path1\;C:\Path Two\;D:\Media\" .csv
These functions will handle ; on their own.
Functions that accept lists parameters:
childfilelist:"file1.txt";"file2.txt";"file3.txt";...
filelist:"file1.txt";"file2.txt";"file3.txt";...
fullpathlist:"file1.txt";"file2.txt";"file3.txt";...
ext:jpg;png
You can use ; or | with these functions.
These functions will eat the |
| doesn't need to be escaped with double quotes.
; or | is treated as OR.
These functions match the whole filename / extension.
I have deliberately made content search functions not support lists.
You will need to use subexpressions for content search functions, eg: content:<abc|123>
path: is a search modifier and is not needed in that search.
For example:
path:"c:\windows;c:\program files"
is the same as
"c:\windows;c:\program files"
Everything is smart enough to know ; followed by a absolute path should be treated as a separate path.
So in short, path:"C:\Path1\;C:\Path Two\;D:\Media\" will behave the same.
Re: ext:xls should also list xlsx files, right?
Yes, sorry!
I had a filter macro: extension.
I deleted this filter macro.
New search results:
Code: Select all
extension:jpg;png
Result: apng;jpg;png;png_e607ca23
wfn:extension:jpg;png
Result: jpg;png
Here are the results:
Code: Select all
extension:jpg;png
Result: apng;jpg;png;png_e607ca23
wfn:extension:jpg;png
Result: jpg;png
Last edited by tuska on Fri Dec 09, 2022 12:11 am, edited 1 time in total.
Re: ext:xls should also list xlsx files, right?
These appear to be the correct results.
Please let me know if anything is unexpected.
Use the exact: search modifier to match the whole extension.
Please let me know if anything is unexpected.
Use the exact: search modifier to match the whole extension.