-
Notifications
You must be signed in to change notification settings - Fork 3
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
Use os:cmd instead of Erlang ports #22
Comments
Would also fix #16 |
I don't think the current implementation supports it, but I'd like to see commands expressed so: {check, ["make xref", "make dialyzer"]} % list of strings and also {test, "make test"} % single string in which case, a "quickfix" for #16 would be to use the new syntax (list of string). |
@paulo-ferraz-oliveira I like the first suggestion. but I still think we should change to os:cmd. |
Oh, I was intending on using it 😄. When I wrote "I don't think the current implementation supports it" I was referring to what I was going to expose below it. So:
{check, ["make xref", "make dialyzer"]} % list of strings while not breaking backward compatibility. |
yeah that's perfect |
With the previous implementation you could always recover the return code from the command, which won't be possible with Is this acceptable? |
Reading ref.: http://www.arv.io/articles/calling-shell-from-erlang. |
I ended up not implementing this syntax {check, ["make xref", "make dialyzer"]} % list of strings as several questions arose that would make its UX difficult. |
os:cmd handles many edge cases and in general is better.
The text was updated successfully, but these errors were encountered: