-
Notifications
You must be signed in to change notification settings - Fork 103
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
disable applications startup (--no-start) when running tests #60
Comments
Hey @larshesel, if/when it gets merged, #58 will allow you to customize the options which are passed to (set-variable 'alchemist-mix-test-default-options
(add-to-list 'alchemist-mix-test-default-options "--no-start")) A drawback is that unless you make the variable local to the buffer, the change will be global within Emacs. Would this sort of solution work for you? |
I think that would be pretty cool. I think for me it would be fine that it's Emacs global. Maybe it would be even better to configure this behavior in mix itself. I'd actually want mix test to, by default, run with --no-start'. |
Yup, I agree that being able to configure mix or exunit itself would be excellent -- this would be a good project level config. The elixir-lang mailing list might be a good place to ask about that. Another possible change: if |
The magit interface is incredible for defining command options (things like |
Re the magit interface -- maybe setup a context menu for discover.el if it's installed. Looks pretty straightforward. |
I've asked about the mix configuration solution on the mailing list: https://groups.google.com/forum/#!topic/elixir-lang-talk/YCWfXQMRL1Y |
And José already solved the problem: https://groups.google.com/d/msg/elixir-lang-talk/YCWfXQMRL1Y/uWuu777cLO4J which is a really good solution for me (the right one IMHO) so I'll close this issue now. Thanks a lot guys! |
I would be fantastic if I could customize alchemist so it does not automatically start the application when running tests from the 'test-on-save' hook.
If this feature is already there, I apologize. I've been looking for a while now, but failed to find it.
The text was updated successfully, but these errors were encountered: