You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a nested mix project defines its own dependencies, mix tool keep them in deps/ in the root directory of the whole project. This is right and desired behavior. Unfortunately, this fools Alchemist which pops up:
== ALCHEMIST COMPLETION FAILED ==
== OUTPUT BEGIN:
Unchecked dependencies for environment dev:
* asn1ex (https://github.com/vicentfg/asn1ex.git)
the dependency is not available, run `mix deps.get`
** (Mix) Can't continue due to errors on dependencies
== OUTPUT END:
When I did deps.get immediately in the nested project, I get another error:
== ALCHEMIST COMPLETION FAILED ==
== OUTPUT BEGIN:
** (Mix) Could not start application lte_rrc: could not find application file: lte_rrc.app
== OUTPUT END:
I guess it can be related with the fact that in Emacs by default CWD is where a visited file resides, not where emacs process was started, a fortiori where root of a whole Elixir project is.
Obviously, whatever completions are provided by standard Elixir shell (iex -S mix) started in the root, works as expected, e.g. :lte_rrc.<TAB> list all exported functions.
The text was updated successfully, but these errors were encountered:
If a nested mix project defines its own dependencies, mix tool keep them in deps/ in the root directory of the whole project. This is right and desired behavior. Unfortunately, this fools Alchemist which pops up:
When I did deps.get immediately in the nested project, I get another error:
I guess it can be related with the fact that in Emacs by default CWD is where a visited file resides, not where emacs process was started, a fortiori where root of a whole Elixir project is.
Obviously, whatever completions are provided by standard Elixir shell (
iex -S mix
) started in the root, works as expected, e.g.:lte_rrc.<TAB>
list all exported functions.The text was updated successfully, but these errors were encountered: