Repository navigation
Should fuzzy completion change the candidate list? #15294
Description
Activity
@roccomao I am using fuzzy like this to only filter the candidates
@techntools Thanks for sharing, this is really useful. Back to the issue, do you also think that separating the fuzzy collection and fuzzy filtering options will give us more configuration space and convenience?
I would still think this makes sense.
That's why
fuzzycollectwas introduced. For whatever reason author decided to revert it, its upto to maintainers and author to reinstate the option.Ease of maintainance may trump the convenience of configuration
For my #15056 (comment), I made arrangements with/without
fuzzycollectI want to continue to explain the idea I mentioned earlier. Adding
fuzzy:numberis the current working method when number is 0. All fuzzy scores > 0 will be added to pmenu. When it is not 0, for examplefuzzy:4, then typecmpdcmpto collect all words d for fuzzy filter. fuzzycollect also sounds reasonable. But adding new options has a cost. Let's try to make some slight changes to the current basis to satisfy everyone. If not, then we will consider fuzzycollect- added a commit that references this issue
on Mar 6, 2025 - added 9 commits that reference this issue
on Mar 7, 2025 - added 6 commits that reference this issue
on Mar 21, 2025
The issue was introduced by patch 9.1.0598
As #14912 (comment) and #15193 (comment) said, but currently
fuzzyoption ofcompleteoptalso affects how candidates are collected. Should fuzzy completion change the candidate list? I don't have enough reasons to say whether this should or should not be (Because I won't actually implement it). I don't know if it's difficult to implement. If it is easy to implement, can we add afuzzycollectoption to control whether to fuzzy collect candidates, as discussed in #14976 ? (now thefuzzycollectoption has been deleted) Otherwise, the document may need to be revised to describe it more accurately.