-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Pod *err*
doesn't get redirected to cider
#544
Comments
Hmm, I just discovered that pod output does make it to emacs, but it ends up in the server buffer, instead of the repl buffer. Not sure what to make of that yet, but it might be fixed along with this issue: clojure-emacs/cider#1588 |
*out*
doesn't get redirected to cider*err*
doesn't get redirected to cider
clojure-emacs/cider-nrepl#387 fixes this issue. I'd normally close now, but it could also be fixed on the boot side, so I'd like to keep this open until cider merges the fix. I'll close if/when that happens. |
It got merged - closing. |
There was a problem when parsing things like SYM:VER=PATH, which split arguments by using different separators.
I noticed that calls to
boot.util/info
from inside a pod do not print in a cider repl. Further investigation revealed that if youboot repl
from a command line andcider-connect
to it, then pod output goes to the command line, and non-pod output goes to cider. I'm hoping there's some way to redirect pod output so that it goes to the same place.The text was updated successfully, but these errors were encountered: