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

Cider 0.7: different load behaviors that lead to error and test mode #703

Closed
fgiasson opened this issue Aug 6, 2014 · 5 comments
Closed

Comments

@fgiasson
Copy link

fgiasson commented Aug 6, 2014

Since yesterday, I am experiencing different things when I load Emacs and starts Cider. The behavior is different mostly every time I run Cider on a new Emacs instance. I am getting one of these three behaviors:

  1. Cider loads fine, and I am in the namespace of the current project
  2. Cider doesn't load at all, and return an error
  3. Cider load, but I am in the clojure.test.mode namespace

Here are the screenshots of these behaviors:

Cider is starting:

cider_0_7_starting

Then Cider load successfully:

cider_0_7_fully_working

Then I reload emacs, and restart Cider, and I get an error:

cider_0_7_error_starting

Here is the Messages buffer:

cider_0_7_message_buffer_start_error

So I restart Emac and Cider, and I am now in the clojure.test.mode namespace:

cider_0_7_test_mode

NOTE: I did uninstall the cider-test-mode module that I had installed with Cider 0.6. This is the reason why I think there is an issue there too.

@bbatsov
Copy link
Member

bbatsov commented Aug 6, 2014

  1. Haven't run into this. Without exact steps to reproduce (or some helpful stacktrace) an issue it's hard to fix it.
  2. There must be some leftovers from clojure-test-mode, otherwise it's impossible for this to happen. Perhaps you had several versions and didn't remove all of them.

@fgiasson
Copy link
Author

fgiasson commented Aug 6, 2014

@bbatsov

  1. I did an upgrade of leiningen using lein upgrade and it seems to be better. Maybe it was something with the older version I had that was sometimes causing issues (was using 2.3.2)
  2. You were right, there was another one that I didn't see. Appears to be fixed now.

@fgiasson fgiasson closed this as completed Aug 6, 2014
@fgiasson
Copy link
Author

fgiasson commented Aug 6, 2014

@bbatsov I experienced the "error in process filter" again. Is there a way to enable some debugging? That is the only error information I can see.

@scottdw
Copy link
Contributor

scottdw commented Aug 6, 2014

I believe the first issue (error in process filter: Quit) is the same as #671 so going to add some details there.

@fgiasson
Copy link
Author

fgiasson commented Aug 6, 2014

@scottdw yes that is right, thanks for making the link to it.

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

3 participants