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

Pod *err* doesn't get redirected to cider #544

Closed
bhagany opened this issue Dec 18, 2016 · 3 comments
Closed

Pod *err* doesn't get redirected to cider #544

bhagany opened this issue Dec 18, 2016 · 3 comments

Comments

@bhagany
Copy link
Contributor

bhagany commented Dec 18, 2016

I noticed that calls to boot.util/info from inside a pod do not print in a cider repl. Further investigation revealed that if you boot repl from a command line and cider-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.

@bhagany
Copy link
Contributor Author

bhagany commented Dec 18, 2016

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

@bhagany bhagany changed the title Pod *out* doesn't get redirected to cider Pod *err* doesn't get redirected to cider Dec 28, 2016
@bhagany
Copy link
Contributor Author

bhagany commented Jan 1, 2017

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.

@bhagany
Copy link
Contributor Author

bhagany commented Jan 2, 2017

It got merged - closing.

@bhagany bhagany closed this as completed Jan 2, 2017
arichiardi added a commit that referenced this issue Jan 9, 2018
There was a problem when parsing things like SYM:VER=PATH, which split
arguments by using different separators.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant