diff options
| author | Bozhidar Batsov <bozhidar@batsov.com> | 2015-08-23 16:42:39 +0300 |
|---|---|---|
| committer | Bozhidar Batsov <bozhidar@batsov.com> | 2015-08-23 16:42:39 +0300 |
| commit | 2495a4c57cb03c9bcedd3cecdd9a53eba359e7bc (patch) | |
| tree | ca394d18601754178df1a9d7c37f9c6e8480db3b /cider-debug.el | |
| parent | aa97ddb70937453d0ce92f77604de7606cf69d39 (diff) | |
[#1225] Move a bunch of connection management logic to CIDER itself
An nREPL client library shouldn't really handle connection multiplexing
and similar concerns. It should simply dispatch requests over a
specified connection - plain & simple. It's the responsibility of the
users to decide what kind of connection management they'd like to implement.
Diffstat (limited to 'cider-debug.el')
| -rw-r--r-- | cider-debug.el | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/cider-debug.el b/cider-debug.el index 62044882..b44195f9 100644 --- a/cider-debug.el +++ b/cider-debug.el @@ -329,7 +329,7 @@ In order to work properly, this mode must be activated by ;; cider-nrepl has a chance to send the next message, and so that the user ;; doesn't accidentally hit `n' between two messages (thus editing the code). (-when-let (proc (unless nrepl-ongoing-sync-request - (get-buffer-process (nrepl-default-connection-buffer)))) + (get-buffer-process (cider-default-connection)))) ;; This is for the `:done' sent in reply to the debug-input we provided. (when (accept-process-output proc 0.2) ;; This is for actually waiting for the next message. |