alchemist-company prevents other company modes about alchemist.el HOT 5 CLOSED

I'm not very familiar with company myself (just switched after a long time with ac-mode) but I will try to take a look at this problem as soon as possible.

from alchemist.el.

@semanticart company-mode should continue to the next backend if the current backend doesn't return a match. So! something is broken. I don't know if it'll matter, but what value do you have alchemist-project-compile-when-needed set to?

Hey @rranelli -- I was playing with company-mode the other day and can look into this.

from alchemist.el.

Thanks, guys. I'm not setting that variable anywhere.

alchemist-project-compile-when-needed is a variable defined in alchemist-project.el'.
Its value is nil`

setting it to t does not appear to change anything

from alchemist.el.

Looking through the doc for the company-backends var (super useful), turns out I was wrong when I said company-mode should go to the next backend of the current backend doesn't return a match. It looks like company will only go to the next backend if the current backend returns nil as the completion prefix.

If it's in an elixir buffer, alchemist's company backend uses alchemist-help--exp-at-point to get the prefix, which will return whatever string is under the cursor. So, in an elixir buffer it won't move on to the next backend.

A simple solution: you can use the interactive command company-other-backend to skip the current backend. It's not as easy as company doing it for you, but if you bind it to a key it shouldn't be too bad.

Alternatively the alchemist backend's prefix command could have more logic for when to return nil, but unless it actually checks candidates (bad. would block.) it won't do what you want.

from alchemist.el.

Thanks @jtmoulia. I'll probably take the reverse approach and remove alchemist-company from the backend list and invoke it via keypress.

from alchemist.el.