Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support fuzzy matching #24

Open
PythonNut opened this issue Jan 12, 2017 · 6 comments
Open

Support fuzzy matching #24

PythonNut opened this issue Jan 12, 2017 · 6 comments

Comments

@PythonNut
Copy link

Followup from PythonNut/company-flx#17.

One way this could be done is to expose some configuration variable company-anaconda-fuzzy-match which would allow tpe to match TypeError. That list of candidates would be handed off to company-flx for sorting.

@proofit404
Copy link
Contributor

Hello. Thanks for investigation this issue! Can you provide PR? I can't figure out requirements for patch from this description, sorry.

@PythonNut
Copy link
Author

Ah I see. I'd need to PR against jedi as well. Changes to the anaconda RPC server would be required as well.

@proofit404
Copy link
Contributor

Can you describe in details what exact changes is necessary to anaconda_mode server and rpc client?

By the way I don't use jedi.el internally if this is what you are speaking about.

@PythonNut
Copy link
Author

PythonNut commented Jan 12, 2017

@proofit404 anaconda-mode would support a configuration flag like anaconda-mode-fuzzy-match, which if non-nil, would pass an extra argument to jedi here, which would tell jedi to produce fuzzy-matched completions.

@proofit404
Copy link
Contributor

But this method doesn't have such argument in its signature jedi master

@PythonNut
Copy link
Author

PythonNut commented Jan 12, 2017

@proofit404 indeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants