Merge pull request #2449 from seanfarley/detach-rename

[ux bug] mu4e: create random name for newly detached views
This commit is contained in:
Dirk-Jan C. Binnema 2023-04-05 23:20:00 +03:00 committed by GitHub
commit f2a193b4fd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 3 deletions

View File

@ -327,11 +327,14 @@ Add this function to `mu4e-view-mode-hook' to enable this feature."
(unless mu4e-linked-headers-buffer
(mu4e-error "This view buffer is already detached."))
(mu4e-message "Detached view buffer from %s"
(prog1 mu4e-linked-headers-buffer
(progn mu4e-linked-headers-buffer
(with-current-buffer mu4e-linked-headers-buffer
(when (eq (selected-window) mu4e~headers-view-win)
(setq mu4e~headers-view-win nil)))
(setq mu4e-linked-headers-buffer nil))))
(setq mu4e-linked-headers-buffer nil)
;; automatically rename mu4e-view-article buffer when
;; detaching; will get renamed back when reattaching
(rename-buffer (make-temp-name (buffer-name)) t))))
(defun mu4e-view-attach (headers-buffer)
"Attaches a view buffer to a headers buffer."

View File

@ -1504,7 +1504,7 @@ messages. You can reattach a buffer to an live headers buffer by
typing @key{Z}.
You can freely rename a message view buffer -- such as with @key{C-x x
r} -- if you want multiple, open messages.
r} -- if you want a custom, non-randomized name.
Detached messages are often useful for workflows involving lots of
simultaneous messages.