voidtools forum

aviasd

Nice digging, Sherlock :) Can't help with taht; I can only guess that showing the tooltip shifts the focus back to Everything. I guess this mystery isn't solved yet... Tried resetting back to tooltips=1 to reproduce the issue before I posted this post, I could not reproduce it. Haven't changed anyt...

aviasd

Thank you for the feedback aviasd, To copy paths with double quotes: In Everything , from the Tools menu, click Options . Cilck the Results tab on the left. Check Double quote copy as path . Click OK . Yep, it was selected here, although it does not affect - Result list | Hot Item | Copy full path ...

aviasd

Hi When assigning a shortcut to Result list | Hot Item | Copy full path to clipboard : 1. Pressing the shortcut will copy the path without quotes while the equivalent context menu item copies with quotes. 2. Pressing the shortcut while on a folder will not copy anything to the clipboard, while the e...

aviasd

In the meantime I tested the "tot.bat-way" too (in a couple of ways). Here (Win10 1909, Everything 1254) it always makes TC the active application. I should know what might cause this under some conditions, but can't put my finger on it atm. Will chew on it ... What happens on your end if you creat...

aviasd

I think you guys (M/F) are on different wavelengths. As I see it, Horst is asking why you (@aviasd) use a tot.bat instead of c:\path to\totalcmd64.exe /parms Correct? FWIW: the second one starts TC and activates it. Didn't test the first ( .bat) one. Yes, running TC directly does activate it. I'm u...

aviasd

I have the context menu entries point to Total Commander and it is started and also activated. I don't see any need for a script here using 1.5.0.1254a It's more of a user preference IMO. In my case, I'd like to see the file in TC when I press enter or double click (overriding the default open comm...

aviasd

I'd like to point out another issue with 1.5.0.1254a and $exec. On 1.5.0.1253a (and older), the exec script would open the current file in total commander and activates total commander. On 1.5.0.1254a, with absolute path to the script, the script does run and total commander opens the file but the w...

aviasd

You can use relative paths. Those paths will be relative to the location of Everything.exe. Are you sure about that? on 1.5.0.1254a non of the variations of work ( relative or root of the drive) on 1.5.0.1253a- (%path% and root of drive work ) Everything 1.4 - all three variations work. ( %Path%, r...

aviasd

For example: $exec("C:\Everything\tot.bat" "%1") I'll look into improving 'virtual file' detection. Thanks for the quick reply. If improving 'virtual file' detection turns out to take time/has issues, please consider adding relative file paths as alternatives, as they also don't work right now. E.G...

aviasd

Hi, on version 1.5.0.1254a the custom exec option (for files and folders) seemed to have stopped working. I have this set for open files/folders (Tools->options->context menu): $exec("tot.bat" "%1") where tot.bat is a script to open total commander and %1 is the filename/folder selected. When double...

aviasd

In 1.5, you can set your search as wanted, first. Then, instead of using the sizedupe: function, you can right-click the Size (or some other) column (& select) the 'Find Size (or some other) Duplicates'. Doing that will search for dupes only based on your current search. Thanks for that :D . Missed...

aviasd

Hi When searching for duplicates, sometimes I don't want to find results of duplicates from a folder I have excluded. For example: sizedupe: !e:\backup Would still show files where their duplicate is residing in the exclude filter (e:\backup). The suggestion is to reevaluate duplicates search functi...

aviasd

Please note: although the filenames may be duplicated, the file contents may actually differ. Please use dupe: as a rough guide for duplicated files, as it doesn't actually check file contents. While not as useful as other programs that check file content, this should help you find a few large dupl...

aviasd

Everything 1.5.0.1253a fixes an issue with group expansion. Everything 1.5.0.1253a will no longer expand functions inside <> and space is no longer a valid group expansion operator (only | is accepted now). Confirmed Read dm:10m..5m as: date modified between 10-minutes-ago and 5-minutes-ago dm:10m....

aviasd

I've been using Fzf for fuzzy searching, which uses the Smith-Waterman Algorithm Matched results were quite good and performance was fast (<1s) on my file list (~5.5M files). Maybe it's worth checking out. The following code was used to test (Powershell): $export="FileList.txt" "Exporting" es -sort-...

aviasd

I use this (rough) function for quick cd in powershell:

Code: Select all

function cdf {
  param($dir)
  cd $(es folder:$dir | fzf)
}

it uses fzf for the selection

aviasd

void wrote: ↑
Tue Mar 30, 2021 1:21 am
Are the Match end of filename with dollar sign and Match start of filename with caret options useful enough to add to the Search options page?

+1
I would consider combining those to a single option though. Most who use ^ probably also use $.

aviasd

void wrote: ↑
Mon Apr 05, 2021 8:49 am
please try the parentname: search function with your scr macro:

scr: exact:parentname:utils

use the exact: modifier to match the whole name "utils"

Ahh,
That's the one, thanks!
It Isn't available in the Search syntax help, but available in the insert function menu.
Have some exploring to do..

aviasd

Hi, Everything 1.5 allows doing a search that wasn't previously available in 1.4 utils*\*.ps1 This translates to: Get me all .ps1 files that are direct descendants in folders whose name contains utils . How could I rewrite the query to give the same results for multiple filetypes? I.E: I have a macr...

aviasd

constant ranges do not though.. But that's cool. What happens? dm:very-short, dm:short, dm:medium, dm:long appear, dm:very-long to work ok here. Remember these expand to a range, eg: dm:short becomes dm:1min..5min (this does not include files modified in the last 1 minute) My mistake, I was treatin...

aviasd

Everything 1.5.0.1252 fixes the issue with using operators on 5mins. dm:5mins..10mins should work as expected now. dm:>5mins should work as expected now (read as greater than 5 mins ago) I've also added support for duration constants. For example: dm:short dm:medium Confirmed! constant ranges do no...

aviasd

Actually it does! Well, it doesn't, void's response is the correct solution. Too quick to type for my own good.. I'll look into support for dm:>5min dm:<10min Cool Currently, Everything will see dm:>5min as dm:>(5 minutes ago or later) This will actually look for a date after or later, which will n...

aviasd

NotNull wrote: ↑
Wed Mar 31, 2021 11:46 am

aviasd wrote: ↑
Wed Mar 31, 2021 11:32 am
It would be easier to query something like all files modified between 5 to 10 minutes ago like so:
dm:>5min dm:<10min
Does this work for you?
Code: Select all
dm:5m..10m

Actually it does!
I'm sure I've tested it at some point...Guess I didn't...
Thx

aviasd

On that note, would it be possible to add time to the date constants (and have the function comparisons respect them)? i.e min, hour It would be easier to query something like all files modified between 5 to 10 minutes ago like so: dm:>5min dm:<10min Instead of dm:>=14:05 dm:<=14:10 Or even dm:5min....

aviasd

Hi,
dm:5min and dm:short return very different results.
dm:5min shows the correct results and dm:short returns results for the whole day...
Am I missing something?

aviasd

The temporary excludes will have no search performance hit, no matter the number of filters or the complexity of your filters. Changing your temporary excludes will have a small performance hit. Great! :D Currently, my custom filter has some noticeable performance hit, it's great that temp excludes...

aviasd

Everything 1.5.0.1251a makes the following changes: Removed indexed_property_max_request -all indexed properties are requested. Use multiple threads for SSDs by default. Fixed an issue with the property indexing progress being lost after exiting. I will trial these settings, and if it hurts system ...

aviasd

void wrote: ↑
Wed Mar 24, 2021 9:46 am

This should be fixed in the Everything 1.5.0.1250a.

Confirmed

aviasd

Hi, I really like the new Temporary excludes feature. I've got a couple of suggested additions ( If possible to add to that already huge TODO list ): 1. Checkboxes for each line in the exclude list. when enabled the current line is applied, when not it is not applied. 2. Ability to use everything se...

aviasd

Another suggestion is: Pin the NameColumn +1 I didn't know everything had shift+mousescroll natively, I've been using this AutoHotkey script to have this functionality enabled for years ( as well as for some other apps ) - this version has a smoother scroll though. (not column-based) ScrollStength:...

aviasd

If you use 0 for indexed_property_max_request there is currently some oddness when you exit and restart Everything.. the property index progress will no longer be shown, although Everything will continue to index your properties. Hi In the new build, I'm not having the issue you are describing - "n...

aviasd

Th e new build does seem to improve somewhat Drives are queried concurrently while indexing properties, there seems to have a little effect though: Previous build indexing time:17:23 New build indexing time:15:50 After indexing from the faster drives everything is bottlenecked by the slower HDD at ~...

aviasd

My setup ( C,H are nvme's) Indexes are unique. Update : my mistake - disk device index is not unique for D and F , should it disable reading other drives concurrently with either F or D? NTFS Index Volume Name: \\?\Volume{} Path: C: Root: Include only: Drive Type: Fixed Label: Index number: 0 Out of...

aviasd

It seems /content_max_threads is responsible for the number of threads of reading props and content, not for the indexing part. seems /no_incur_seek_penalty_multithreaded=1 is a viable option for nvme's but not for hdd's, but thanks it does help on those. I'm unsure what's the ratio between time to ...

aviasd

Hi, I've tried testing property indexing Added indexing for videos - Length and total bitrate. It seemed to go in a sequential manner even though my videos are spread in separate drives. ( some ssds, some hdds) Took around 5 minutes for ~70k files Is there a flag to allow multi-threaded property ind...

aviasd

Thanks, @aviasd. Interesting. How would that try/catch/finally mechanism work if it isn't an error but an unwanted result? like: Action1: add 1+1 if result = 2 { action 2 etc. .... } else { return } The idea of exceptions is generally to stop the execution of the next statements if something went w...

aviasd

This is my method ( Developed by personal taste): try { ;Each of the actions could possibly throw an exception from it's code, on failure which is caught inside this try Action 1 Action 2 result = Action 3 return result } catch (MyException ex) { //Handle different cases - you may create a custom ex...

aviasd

Great new everything version! Are there any bug submission guidelines for the new 1.5 ? If there are I'd suggest they'd be put in a sticky post at the top. Also, for alpha, I'd suggest having debug logging enabled by default to some file to catch some hard to recreate crash cases ( Had one after 5 m...

aviasd

Amazing !
It's a good measure of a tool if you learn something new even after so many years of usage.

Next time: Read the tooltips much more carefully

aviasd

Worked great out of the box.
Attached is my current visual config.
I found it the most easy on the eyes and was working for me for the past 5 years.

: Untitled.png (383.62 KiB) Viewed 39572 times

aviasd

Still does not solve the problem of using macros for "aliasing" commands with argument support..
Am I wrong here or is it possible in some way ?

aviasd

It looks like it uses Everything for it's filename searches, as it includes Everything32.dll (from the SDK) to communicate with a running Everything. BUT: when I ran Everything in debug mode, I could not see any (IPC) activity from this AnyTXT. AnyTXT was not very mature at that moment, but it look...

aviasd

Yes, two delimiters will be supported. ; can be escaped with double quotes. doubles quotes can be escaped with quot: (or ": in future versions of Everything) | can be escaped with &verbar: in future versions of Everything. I see . I'm guessing you have your reasons of not escaping with the stan...

aviasd

+1
I do believe this could be a useful feature.
Currently I revert to using cli tools like ripgrep for content searching, which knows to skip binary files as well as respect .gitignore and git folders etc.
Supporting these features in everything could be great!

aviasd

Very cool

Could I request some dark versions with alternating row colors ? My eyesight is not what it used to be...

aviasd

Macro names are case-sensitive, so if you defined e: as a macro, you can still use E: to specify the files on your E:-drive. Another alternative: use "e:" (surrounded by "" ) That's a good point! Never realized that the macros were case sensitive. The problem is when trying to be "wise" you might m...

aviasd

aviasd

Hi, Just wanted to input a scenario that might need be addressed. When creating a one letter macro, for example: e: , the macro will override the drive path handler, effectively preventing specifying path that starts with e:\ . Encountered after having forgotten that I created the macro and could no...

aviasd

Hi,

This is just a minor issue, but grouping multiple extensions using ext:ext1;ext2 differs from the common way of grouping <file1|file2>

Imo, to retain consistency, the ext handler should support the common way as well..

Br,
Avi

Edit: Sorry, Please move to suggestions

aviasd

There are quite a few nice ideas in your script. Highlighting the file you selected (in Everything) and using the dialog's file extension to limit the search to that extension. Those stood out the most to me. EDIT: also worth mentioning: a routine for handling mouse-dragging. Thanks, I was just try...

Search found 77 matches