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

Completion fails in nested project having its own dependencies #46

Closed
wrachwal opened this issue Feb 11, 2015 · 3 comments
Closed

Completion fails in nested project having its own dependencies #46

wrachwal opened this issue Feb 11, 2015 · 3 comments

Comments

@wrachwal
Copy link

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.

@tonini
Copy link
Owner

tonini commented Feb 23, 2015

@wrachwal Sorry for the late answer, I have a lot of work at the moment but I will have a look into it soon.

Cheers

Sam

@tonini
Copy link
Owner

tonini commented Jun 16, 2015

@wrachwal Alchemist v1.0 is released and this issue should be fixed with it. Could you please test this case and then close the issue?

@tonini
Copy link
Owner

tonini commented Jun 18, 2015

I close this issue because v1.0 is released and this kind of bugs can't happen anymore.

Thanks

@tonini tonini closed this as completed Jun 18, 2015
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

2 participants