Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Custom key for filtering (matcher_key)

See original GitHub issue

Hi. I’d like to give ncm2 a try, but it appears that I’m stuck with deoplete because of its very convenient matcher_key feature that I use in some of my sources: issue: https://github.com/Shougo/deoplete.nvim/issues/759 implementation: https://github.com/Shougo/deoplete.nvim/commit/1cacfeb561fc65c3301c9771480c89064fcb8940 sample usage: https://gist.github.com/balta2ar/2f06ae40f8d7addf0bd501dd0a2411d9

Is possible to implemented similar functionality here? Thank you.

Issue Analytics

State:
Created 5 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

roxmacommented, Jul 13, 2018

hmm… This doesn’t seem convenient to me.

I’m going to change the matcher interface…

0reactions

roxmacommented, Jul 17, 2018

. Would it be possible to add even more fuzzier matcher here,

It is possible.

But I havent’ look into others implementations.

There’s used to be a fuzzy matcher in old ncm. I didn’t like it. I often got matches I don’t want.

Current abbrfuzzy is almost perfect for me.

I’ll probably need fuzzy search for my URL source that completes URLs from browser tabs.

In case abbr based fuzzy match doesn’t work so well, you could also try a combination of substr matcher, enabled by this PR: https://github.com/ncm2/ncm2/pull/23