-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
eask analyze output is sent to stderr #276
Comments
This is actually a weird emacs thing: > emacs --batch --eval "(message \"hi\")" 1>/dev/null
hi
> emacs --batch --eval "(message \"hi\")" 2>/dev/null
# nothing From the man page
Same for the So is |
Hmmm… the same issue should have been solved a long while ago. See #124.
Eask is the wrapper for |
Ah sorry, I didn't search hard enough, now I found #123 My main problem was PS: a side-effect of the above observation about emacs' > eask eval '(message "hello")'
Warning (package): Package lacks a terminating comment
Warning (emacs): Unmatched dependency 'emacs'; add (emacs "VERSION") to package-file or consider removing it
Updating environment variables... done ✓
Exporting environment variables... done ✓
hello But then, if I want to hide the diagnostic messages: > eask eval '(message "hello")' 2>/dev/null
# no output All of the message output of |
Yeah, the analyze command only output to the stderr stream. See Line 113 in a4aa340
Line 120 in a4aa340
We can change to standard output instead. :)
Hmm... the Line 56 in a4aa340
|
Thanks for checking!
Sorry this was a little off-topic from the main issue. My point was that both emacs and eask write to standard error, so when using the I wonder if the |
No worries! I might have misunderstood your question! 😅
Do you mean the Node.js layer and Emacs outputs? Right now, there is no way to separate these outputs. We will have to change the command behavior. 🤔
Eask is hybrid (Node.js + Elisp), so it has to print something, or else it would have no outputs. 🤔 |
This means
eask analyze
does not play nicely in shell scripts.Specifically, I want to do
Some commands will separate output and error per #123
vs
The text was updated successfully, but these errors were encountered: