Closed Hi-Angel closed 5 years ago
flx
assigns a score to each candidate and then sorts based on that score. Usually, each candidate ends with a different score. In this context, your proposal is incompatible with how flx-ido
works.
@oscarfv okay, is there a way to disable that sorting then?
Cool, I just found in someone's blog post: turns out, that functional exists in vanilla ido
without any addons, just use:
(setq ido-enable-flex-matching t)
Closing then.
flex-matching
is a different method of selecting and sorting candidates. I'm glad it does what you want, though.
The place where I have the most trouble with this is imenu-anywhere
, which prioritizes matches in the current buffer over other buffers. flx-ido
unfortunately overrides this sort behavior, which means the function you're usually after is down the list. Would be great to have a configurable list of commands for flx-ido to preserve the sort order of.
The place where I have the most trouble with this is
imenu-anywhere
, which prioritizes matches in the current buffer over other buffers.flx-ido
unfortunately overrides this sort behavior, which means the function you're usually after is down the list. Would be great to have a configurable list of commands for flx-ido to preserve the sort order of.
flx-ido
is all about sorting. If you change the sorting, it is not flx
anymore. You can disable flx-ido
locally advising the function (i.e. imenu-everywhere
).
Original
ido-mode
has a nice feature: it shows most recently visited buffers first. I'd expect theflx-ido-mode
to just add a fuzzy match, but retain the original sorting. Unfortunately it doesn't, which often results in even more typing than withoutflx-ido-mode
.Steps to reproduce
main.rs.awesome
main.rs.way-cooler
*scratch*
buffermain.rs.way-cooler
as the first match).main
Expected
main.rs.way-cooler
should be the first match as it's the most recently visited.Actual
main.rs.awesome
becomes the first element in the list.