-
-
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
[Fix #2045] *cider-scratch* is no longer an ancillary buffer #2067
Conversation
One test failed for unrelated reason. |
Seems to me after this they won't also be killed on |
I think scratch buffer should never be killed. It's up to the user to decide what to do with that buffer. Just like with emacs'
Which are those? You mean all those buffers now called "ancillary"? |
But in Emacs this buffer will always be working. On complete CIDER quit we should not leave anything around I think.
I meant scratch buffers - IMO if we don't kill them they should be treated similarly to REPL buffers and get "reconnected" (or something like this). In general I don't like it that we don't explicitly link scratch buffers to some project and REPL type and things with them become quickly confusing for some people. |
You can quit all connections and restart them later and be willing to re-use the scratch buffer. For me scratch buffers are just like ordinary files with a mode providing some extra evaluation functionality. It's entirely up to the user what to do with it. I don't see it as part of the CIDER connection ecosystem per se, more like an ordinary clojure buffer.
They are loosely connected in the sense that they will send code to the most recent connection. I think people using scratch buffers expect precisely this semantics.
I think this is a more general issue with cider connection management. There must be a more user friendly way to associated buffers, directories and entire projects to connections. I hope to provide a PR on this in the following weeks, so we can discuss this in more concrete terms. As far as scratch buffer is concerned, if scratches are allowed to be associated with projects, their implementation would inevitably become more complex. At least, one should be able to create multiple scratch-buffers. |
Uff, I accidentally deleted this branch. Restoring. |
Based on some tickets filed by users I'm not quite certain that's true. 😃
Looking forward to it. As for this PR - let's just kill the buffer on |
I am afraid this one has to wait a bit till #2069 is sorted out. |
I have reabased this one for 0.15.1. As per your suggestion, killing the scratch on quit-all but with obligatory user's consent. |
Also documenting here my recent changes to cider-nrepl to avoid changelog conflicts. I asume you will be pulling clojure-emacs/cider-nrepl#435 for 0.15.1. With this, I have completed my part for 0.15.1. |
👍 |
AFAICS the only function of ancillary buffers right now is to be killed on
cider-quit
, so this simple change seems to be just what's needed.