I use Type Ahead Find probably 20000 times a day, and many many times it fails to find what I'm searching for. Most often I search for a 2-3 word phrase, and that is where the problem arises.
If the filename has underscores, dashes, etc, it wont find a match. So if I search for "My File", it wont find "My_File". I figured I could use a ? or * as wildcard for spaces in the phrase, or a regex by prefixing with > but it didnt work. An tweak to allow spaces to match anything would be great.
Type ahead find wildcards
Re: Type ahead find wildcards
Have you considered using the Live Filter Box instead?
Running on Windows 10 Pro 64-bit quad-core ASUS G752-VY notebook with 64 GB RAM, over 26 external USB3 drives attached via multiple powered hubs with letters and mount points, totaling 120+ TB.
Re: Type ahead find wildcards
The LFB encomasses many more keystrokes for consecutive searches
When quickly looking for matches, type-ahead is lightning efficient because you dont have to focus the filter box, focus the pane, or clear the filter to get the list back, plus the match is already selected. They only keystrokes needed are a hotkey for "next match" or Ctrl-V for pasting the keyword(s) from clipboard. I do use the visual filter when I expect a plentiful match, and sometimes selection filter (both which also suffer the same ability to do keyword based search).
What I need to find is cloudy-day, cloudy_day, cloudy day, cloudy2day, etc without always having to wildcard the spaces or enable regex mode, which makes pasting from clipboard useless.
I would have to a search of *cloudy*day* or do a regex >cloudy.*day. Sure there's a workaround of you're an autohotkey poweruser and make a script to workaround this but it seems like much to do
if there was an option for Type Ahead find that translates a space into a wildcard (a more keyword based search) it would make it 10 times more useful - and even better would be matches out of order (day cloudy, day2day2cloudy)
When quickly looking for matches, type-ahead is lightning efficient because you dont have to focus the filter box, focus the pane, or clear the filter to get the list back, plus the match is already selected. They only keystrokes needed are a hotkey for "next match" or Ctrl-V for pasting the keyword(s) from clipboard. I do use the visual filter when I expect a plentiful match, and sometimes selection filter (both which also suffer the same ability to do keyword based search).
What I need to find is cloudy-day, cloudy_day, cloudy day, cloudy2day, etc without always having to wildcard the spaces or enable regex mode, which makes pasting from clipboard useless.
I would have to a search of *cloudy*day* or do a regex >cloudy.*day. Sure there's a workaround of you're an autohotkey poweruser and make a script to workaround this but it seems like much to do
if there was an option for Type Ahead find that translates a space into a wildcard (a more keyword based search) it would make it 10 times more useful - and even better would be matches out of order (day cloudy, day2day2cloudy)
Re: Type ahead find wildcards
I used to use the Type-Ahead a lot myself, and the next/prev shortcuts, but when the long-awaited LFB came around, I switched. But I do see your point. What about if Don provided an option that puts you immediately into the LFB upon typing, instead of invoking Type-Ahead? I think I would like that a lot, actually. It IS a bit cumbersome to switch between the LFB box and the list. I am always filtering.
Running on Windows 10 Pro 64-bit quad-core ASUS G752-VY notebook with 64 GB RAM, over 26 external USB3 drives attached via multiple powered hubs with letters and mount points, totaling 120+ TB.
Re: Type ahead find wildcards
+1. Could also use this to filter on part of a filename and extension. Would be very handy.Millzey wrote:The LFB encomasses many more keystrokes for consecutive searches
When quickly looking for matches, type-ahead is lightning efficient because you dont have to focus the filter box, focus the pane, or clear the filter to get the list back, plus the match is already selected. They only keystrokes needed are a hotkey for "next match" or Ctrl-V for pasting the keyword(s) from clipboard. I do use the visual filter when I expect a plentiful match, and sometimes selection filter (both which also suffer the same ability to do keyword based search).
What I need to find is cloudy-day, cloudy_day, cloudy day, cloudy2day, etc without always having to wildcard the spaces or enable regex mode, which makes pasting from clipboard useless.
I would have to a search of *cloudy*day* or do a regex >cloudy.*day. Sure there's a workaround of you're an autohotkey poweruser and make a script to workaround this but it seems like much to do
if there was an option for Type Ahead find that translates a space into a wildcard (a more keyword based search) it would make it 10 times more useful - and even better would be matches out of order (day cloudy, day2day2cloudy)
Kyle Alons
https://www.kinook.com
https://www.kinook.com
-
- Site Admin
- Posts: 60558
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Type ahead find wildcards
I made some experiments but it turned out too hairy. The related code is already very complex. This addition would make it explode.
FAQ | XY News RSS | XY Twitter