Fla$her wrote: 2024-08-27, 21:35 UTC
2
AGlezB
I'm not really against it, but I think the feature of filtering is to search for something when you don't want to spend time typing and remembering a whole name, adding arrow navigation to quickly get focus. Therefore, it's absolutely normal to observe a decrease in the number of matching list items during the filtering process. And in the case of filtering by an whole name at the time of typing, everything will disappear, and only one single name will appear if there is a complete match.
It seems to me that it is more logical to use the hotkey with the 'cd' command and the '?' parameter. Only here remains a problem with opening the matching folder, which could be solved by implementing
my 3) suggestion.
It's a matter of how quickly and easy I can do what I need to do, in particular when I have to do it a bunch of times.
My current configuration supports what I do the most: type the first few letter of a directory or file and have TC position the cursor over it. For that to work matching needs to start at the biginning of the name. For example let's say I have these folders:
- ..
- Blueprints
- Manuals
- ObsoleteBlueprints
- ObsoleteManuals
- ObsoleteSoftware
- Software
If i want to go to Blueprints, Manuals or Software I just have to type the first letter.
Now what happens if I want to see only the Sofware folders? I have to press CTRL+S and type "*so".
In my use case every type I press CTRL+S is because I want to filter and not by the beginning of the word because the file list is already sorted by name so I don't need to filter from the beginning of the name. That means every single time I press CTRL+S I also have to add an asterisk and the only reason I have to do it is because there is a single configuration for both features so both will always behave the same.
Also, the example above is a very simplified view of the folder structure I have to deal with. The actual folder where I have to do most of the work looks like this with CTRL+Q:
Code: Select all
Total space occupied:
131,838,455,144 bytes in 375,722 file(s),
in 56,834 directories
(= 128,748,491k, 125,730M, 122G)
Actual space used (considering cluster size)
on source drive: 132,606,210,048 Bytes
And it's 15 levels deep in some places. I can't really show it because that resides in servers we don't own so while I can deploy a portable version of TC to help me with my work and can't really do much else. Oh, and they had a cryptolocker incident a while back and now they're paranoid with their security so I can't even use the autotype suggestion above which would actually solve my problem.
