emenel/doomemacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

fix(lib): don't kill buffers visible in another frame

Browse source 
For Doom's kill-current-buffer advice.
This commit is contained in:
Henrik Lissner 2024-06-26 23:21:06 -04:00
parent 5718e4e96e
commit a24ff58a5a
No known key found for this signature in database
GPG key ID: B60957CA074D39A3
2 changed files with 7 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
lisp/doom-ui.el
View file

@ -225,7 +225,7 @@ windows, switch to `doom-fallback-buffer'. Otherwise, delegate to original
(when (or ;; if there aren't more real buffers than visible buffers,
;; then there are no real, non-visible buffers left.
(not (cl-set-difference (doom-real-buffer-list)
(doom-visible-buffers)))
(doom-visible-buffers nil t)))
;; if we end up back where we start (or previous-buffer
;; returns nil), we have nowhere left to go
(memq (switch-to-prev-buffer nil t) (list buf 'nil)))