Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

*cider-scratch* is killed on connection exit #2045

Closed
vspinu opened this issue Jul 15, 2017 · 2 comments
Closed

*cider-scratch* is killed on connection exit #2045

vspinu opened this issue Jul 15, 2017 · 2 comments

Comments

@vspinu
Copy link
Contributor

vspinu commented Jul 15, 2017

If this is by "design" it is a bad idea. You might have quite some code in scratch and want to restart connection for whatever reason, and then boom, everything is gone.

@bbatsov
Copy link
Member

bbatsov commented Jul 16, 2017

If this is by "design" it is a bad idea. You might have quite some code in scratch and want to restart connection for whatever reason, and then boom, everything is gone.

Yeah, it's by design. It's not treated the same way as buffers like help buffers. Guess we should rethink this behaviour.

@rcullito
Copy link
Contributor

definitely would further support the validity of this issue. this has happened to me several times and I've ended up recreating most of the work that I had in the old cider-scratch

vspinu added a commit to vspinu/cider that referenced this issue Jul 31, 2017
vspinu added a commit to vspinu/cider that referenced this issue Aug 26, 2017
vspinu added a commit to vspinu/cider that referenced this issue Aug 26, 2017
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants