[vim/vim] Should fuzzy completion change the candidate list? (Issue #15294)

28 views
Skip to first unread message

Rocco Mao

unread,
Jul 18, 2024, 10:32:08 AM (4 days ago) Jul 18
to vim/vim, Subscribed

The issue was introduced by patch 9.1.0598

As #14912 (comment) and #15193 (comment) said, but currently fuzzy option of completeopt also 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 a fuzzycollect option to control whether to fuzzy collect candidates, as discussed in #14976 ? (now the fuzzycollect option has been deleted) Otherwise, the document may need to be revised to describe it more accurately.


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/15294@github.com>

techntools

unread,
Jul 20, 2024, 1:31:43 PM (2 days ago) Jul 20
to vim/vim, Subscribed

@roccomao I am using fuzzy like this to only filter the candidates

#15056 (comment)


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/15294/2241237813@github.com>

Rocco Mao

unread,
Jul 20, 2024, 9:49:23 PM (2 days ago) Jul 20
to vim/vim, Subscribed

@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?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/15294/2241376793@github.com>

Christian Brabandt

unread,
Jul 21, 2024, 3:29:57 AM (yesterday) Jul 21
to vim/vim, Subscribed

I would still think this makes sense.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/15294/2241509435@github.com>

techntools

unread,
Jul 21, 2024, 11:33:34 AM (21 hours ago) Jul 21
to vim/vim, Subscribed

@roccomao

That's why fuzzycollect was 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 fuzzycollect


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/15294/2241679727@github.com>

Rocco Mao

unread,
Jul 21, 2024, 1:03:32 PM (19 hours ago) Jul 21
to vim/vim, Subscribed

Maybe we can mention the author @glepnir, I don't know if it will be difficult to implement and what you are considering, but here are some ideas you can consider. In fact, this is also discussed in issue #15295, Sorry to bother you so that you can receive some information from this issue.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/15294/2241713655@github.com>

glepnir

unread,
2:03 AM (6 hours ago) 2:03 AM
to vim/vim, Subscribed

I want to continue to explain the idea I mentioned earlier. Adding fuzzy:number is the current working method when number is 0. All fuzzy scores > 0 will be added to pmenu. When it is not 0, for example fuzzy:4, then type cmpd cmp to 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


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/15294/2242153575@github.com>

Reply all
Reply to author
Forward
0 new messages