-
-
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
Bugfix/fix cider selector problem #2711
Merged
bbatsov
merged 5 commits into
clojure-emacs:master
from
ahungry:bugfix/Fix-cider-selector-problem
Sep 21, 2019
Merged
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
cd6ef9d
Add note about the problem
ahungry e8ab9e7
Adjusts cider-selector handling with the following benefits:
ahungry 7b2966e
Further tuning of the selector handling
ahungry 7e4de5c
Update docstring
ahungry 9bc6c89
Merge branch 'master' into bugfix/Fix-cider-selector-problem
bbatsov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -49,17 +49,23 @@ DESCRIPTION is a one-line description of what the key selects.") | |
Not meant to be set by users. It's used internally | ||
by `cider-selector'.") | ||
|
||
(defun cider-selector--recently-visited-buffer (mode) | ||
(defun cider-selector--recently-visited-buffer (mode &optional consider-visible-p) | ||
"Return the most recently visited buffer, deriving its `major-mode' from MODE. | ||
Only considers buffers that are not already visible." | ||
CONSIDER-VISIBLE-P will allow handling of visible windows as well. | ||
First pass only considers buffers that are not already visible. | ||
Second pass will attempt one of visible ones for scenarios where the window | ||
is visible, but not focused." | ||
(cl-loop for buffer in (buffer-list) | ||
when (and (with-current-buffer buffer | ||
(derived-mode-p mode)) | ||
;; names starting with space are considered hidden by Emacs | ||
(not (string-match-p "^ " (buffer-name buffer))) | ||
(null (get-buffer-window buffer 'visible))) | ||
(or consider-visible-p | ||
(null (get-buffer-window buffer 'visible)))) | ||
return buffer | ||
finally (error "Can't find unshown buffer in %S" mode))) | ||
finally (if consider-visible-p | ||
(error "Can't find unshown buffer in %S" mode) | ||
(cider-selector--recently-visited-buffer mode t)))) | ||
|
||
;;;###autoload | ||
(defun cider-selector (&optional other-window) | ||
|
@@ -97,7 +103,7 @@ is chosen. The returned buffer is selected with | |
`switch-to-buffer'." | ||
(let ((method `(lambda () | ||
(let ((buffer (progn ,@body))) | ||
(cond ((not (get-buffer buffer)) | ||
(cond ((not (and buffer (get-buffer buffer))) | ||
(message "No such buffer: %S" buffer) | ||
(ding)) | ||
((get-buffer-window buffer) | ||
|
@@ -138,8 +144,10 @@ is chosen. The returned buffer is selected with | |
(top-level)) | ||
|
||
(def-cider-selector-method ?r | ||
"Current REPL buffer." | ||
(cider-current-repl)) | ||
"Current REPL buffer or as a fallback, the most recently | ||
visited cider-repl-mode buffer." | ||
(or (cider-current-repl) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The docstring probably needs to be adjusted, as now this does something different. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. updated |
||
(cider-selector--recently-visited-buffer 'cider-repl-mode))) | ||
|
||
(def-cider-selector-method ?m | ||
"Current connection's *nrepl-messages* buffer." | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can probably simplify the logic and consider all buffers right away. I've mostly copied this code from SLIME back in the day and I didn't think much about it. Treating differently hidden/visible buffers seems weird to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had thought about that, and on one of the commits actually implemented as such, but that had a side-effect of removing the ability to use cider-selector to flip-flop between the latest 2 buffers of the same type (to change from a clojure-mode buffer to the last visited but not shown clojure-mode buffer - not using the second pass would change this operation into a noop essentially).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it. Well, I guess it really depends on what do we consider the purpose of this command to be - for me it was always to jump to a source buffer from some special buffer and vice versa. Of course, there's also the question of how people are actually using something and what do they consider useful. :D
That's why I was thinking we should extend the documentation of
cider-selector
in general so people would know how it's supposed to be used.