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

Company Quickhelp and Alchemist #33

Closed
houli opened this issue Feb 15, 2016 · 6 comments
Closed

Company Quickhelp and Alchemist #33

houli opened this issue Feb 15, 2016 · 6 comments

Comments

@houli
Copy link

houli commented Feb 15, 2016

When using company quickhelp and Alchemist (Elixir completion server) often Emacs will hang and use 100% CPU. The only solution seems to be to restart Emacs by force-quitting it.
The author of Alchemist seems to think this is caused by an incompatibility between company quickhelp and the asynchronous way Alchemist returns documentation.

@expez
Copy link
Collaborator

expez commented Feb 16, 2016

Thanks for letting me know and creating an issue for others experiencing this problem to find.

However, if the Company backend is inefficient there's unfortunately nothing I can do. All this mode does is request that information and display it in a popup.

@tonini
Copy link

tonini commented Mar 8, 2016

Hi,

The problem is that Alchemist works async with with Alchemist-Server in the background. So we're using filters for our completion process request to the server in which we continues with the proper delivery to company-mode. So I guess quickhelp itself don't handle these kind of async processes at all and just expects the infos directly after it requests for the documentation.

@houli I recommend setting company-quickhelp-delay to nil when you're in an alchemist-mode.

@expez
Copy link
Collaborator

expez commented Mar 8, 2016

The problem is that Alchemist works async with with Alchemist-Server in the background.

This is not the problem. The CIDER backend (for Clojure development) is also something company talks to asynchronously and that works just fine.

So I guess quickhelp itself don't handle these kind of async processes at all and just expects the infos directly after it requests for the documentation.

All I do here is ask company for the doc string and then display it in a popup.

@tonini
Copy link

tonini commented Mar 8, 2016

This is not the problem. The CIDER backend (for Clojure development) is also something company talks to asynchronously and that works just fine.

This is actually great to hear, so I guess I'll have a look at the CIDER documentation backend first.

All I do here is ask company for the doc string and then display it in a popup.

Damn, so you're on the easy side and I do something wrong ;-)

@tonini
Copy link

tonini commented Mar 8, 2016

Ok, after testing it by myself I can't any issues or reproduce it. It works really nice for me.

So we need some help from @houli about this one, maybe he can reproduce it and have a look at the error outputs.

I guess the best place to talk about this in on the Alchemist repository itself, it's not company-quickhelps issue at all.

Thanks @expez

@tonini
Copy link

tonini commented Mar 8, 2016

@houli Please open an issue on the Alchemist repository were we could talk about this issue.

@expez expez closed this as completed Mar 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants