Jonathan Hayase

The switch to `cl-labels` appears correct. The reason I avoid requiring `flx` is due to lazy-loading. The warnings can be suppressed with `declare-function` instead, right?

You are correct `company-flx` does not currently work with any company backend that is not `company-capf`. I would need to manually advise each backend I want to support to include...

@proofit404, do you think this could be done easily by advising `company-anaconda` primitives?

Hi @proofit404, thanks for getting back to me! I was actually wondering if there was a way to add support _without_ modifying `company-anaconda` (but of course, if you're wiling to...

@proofit404 fuzzy _matching_ is probably going to be the more challenging of the two. In fact, I already have a company transformer that will sort the candidates already, so matching...

@proofit404 ideally, you would implement a way for me to supply (by setting a variable or overriding a function) my own matching predicate, which would take the user's "prefix" and...

Try `(setq company-minimum-prefix-length 2)`.

https://github.com/PythonNut/company-flx/blob/master/README.md#caveats :P > with `company-capf` How can you reproduce this, and are you sure `company-capf` is the backend being used for `go`?

@dgutov I took a pass at implementing this a few months ago. Do you have any insights about adding arbitrary highlighting to the candidates in a front-end agnostic way? Ideally,...

@dgutov > At the moment, arbitrar-ish highlighting is performed via the `match` backend command. It looks like the `match` command only reads text-properties? I don't see any highlighting being added....