You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched for a bit but didn't see anything related, apologies if this is a dupe.
I noticed that when using :o to open files, tab completion does not prefer exact/closest match, which means more tabbing/typing is required than should be necessary. If I had to guess it's because file extension is not being treated differently from filename (or at least, as a match boundary).
For example, assume I have the following tree:
./
foo.bar
foo_baz.bat
If I :o foo (but do not hit enter), foo_baz.bat is the first item in the list, whereas I would expect foo.bar to be first as it is a closer match.
This is also the case outside of extensions, for example:
./
foo/
...
foo-bar/
...
If I :o foo again here, foo-bar will be first in the list. This case is worse IMO as we're preferring a non-exact match to an exact match.
Is there a setting I'm not seeing that controls this? If not, would it be possible to adjust sorting to prefer closer/exact matches?
The text was updated successfully, but these errors were encountered:
I searched for a bit but didn't see anything related, apologies if this is a dupe.
I noticed that when using
:o
to open files, tab completion does not prefer exact/closest match, which means more tabbing/typing is required than should be necessary. If I had to guess it's because file extension is not being treated differently from filename (or at least, as a match boundary).For example, assume I have the following tree:
If I
:o foo
(but do not hit enter),foo_baz.bat
is the first item in the list, whereas I would expectfoo.bar
to be first as it is a closer match.This is also the case outside of extensions, for example:
If I
:o foo
again here,foo-bar
will be first in the list. This case is worse IMO as we're preferring a non-exact match to an exact match.Is there a setting I'm not seeing that controls this? If not, would it be possible to adjust sorting to prefer closer/exact matches?
The text was updated successfully, but these errors were encountered: