-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
CIDER-REPL prints entire buffer when symbol not found #1389
Comments
After executing
|
Reading through the code in |
@cichli Can you look into this? |
Anyway, I can replicate this. Looks like CIDER is sending a file's contents to eval instead of the filename. |
@scottdw ech, I see what you were referring to re: the connection with load-file:
|
This is fixed on nREPL master, |
Moving to |
Guess we need a stable release then. On Friday, 30 October 2015, Scott Douglas-Watson [email protected]
Best Regards, |
Percolating through hudson now. Expect |
Fantastic. I'm on a trip with a computer for the weekend, so someone else On Friday, 30 October 2015, Chas Emerick [email protected] wrote:
Best Regards, |
Without a computer On Friday, 30 October 2015, Bozhidar Batsov [email protected]
Best Regards, |
Eagerly waited until 0.2.12 was up, and it works beautifully! None of this problem anymore. Thanks (: |
I'll leave the closing of this issue to the devs, if you guys need to sort things out for CIDER or nREPL. |
I can merge and deploy those PRs by @scottdw once I get a confirmation that the release is up. |
[Fix clojure-emacs/cider#1389] Bump the nREPL dep to 0.2.12
[Fix #1389] Bump the required nREPL version to 0.2.12
Deployed. |
Ever since bumping tools.nrepl to 0.2.11, CIDER now prints my entire namespace buffer in the REPL if I refer to a symbol that doesn't exist in that namespace.
This wasn't happening before bumbing to that version of tools.nrepl.
I suspected that this was a compatibility issue with the new version tools.nrepl and CIDER, but upgrading to the latest version from the Melpa repo didn't fix it.
Actually, this also extends to errors such as "Can't take value of macro"
The text was updated successfully, but these errors were encountered: