If I type aa, it's not the first item starting with aa that's selected, but the second item that starts with a.
Since I never use the repeatedly-typing-the-same-key-cycling feature I always expect it to select according to what I type, and when it selects something else I get quite annoyed.
It would be nice if cycling could be disabled completely with a setting. Or maybe it could be changed so that a correct find is prioritized over cycling?
Great work with the other type ahead refinements by the way.
Yet another type ahead find refinement (aa)
Re: Yet another type ahead find refinement (aa)
Heh. I use the 'aa' => second thing starting with 'a' way more than I use the standard find ahead (though I do use that too). Why it drove me crazy when I typed 'a' and got "no matching items" for ([the thing I had typed before, most likely some other single letter) + 'a'). Much nicer now that you can wipe the type ahead history with escape or an arrow key, but still - to each his own (always amuses me people asking for features or bugfixes in various tree-view components, as the first thing I do on a new computer is turn off anything tree-view-like.)
Anyway, I definitely expect aaa to find the third thing with 'a' in its name, even if the first thing in a directory happens to start with the string "aaa", so I vote for an option (but it would be a perfectly reasonable option.)
Anyway, I definitely expect aaa to find the third thing with 'a' in its name, even if the first thing in a directory happens to start with the string "aaa", so I vote for an option (but it would be a perfectly reasonable option.)
XYplorer Beta Club