[PATCH] change dired--find-possibly-alternative-file behaviour.

[Felix <felix.dick@web.de>]

[-- Attachment #1: Type: text/plain, Size: 995 bytes --]


I find dired--find-possibly-alternative-file a bit
confusing if dired-kill-when-opening-new-dired-buffer is set to t.

It's fine if the active window is the only window that shows that dired
buffer, but if there are multiple windows showing dired buffers, it's
likely that the user wanted to have those windows showing dired buffers.
If those buffers happen to show the same directory, opening another
directory with dired-find-file will kill the buffer, and change the
shown buffer in both windows.

Before dired-kill-when-opening-new-dired-buffer, to copy/move a file to
another directory, i could open a dired buffer, split the window, in
one of the windows (both showing the same dired buffer) navigate to
another directory and copy the file (with the dired-dwim-target).

In my personal configuration, i changed
dired--find-possibly-alternative-file to not kill the buffer if
it's shown in another window. I'm not shure if this would fit
every workflow, but for me it feels more logical.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: dired.patch --]
[-- Type: text/x-patch, Size: 570 bytes --]

diff --git a/lisp/dired.el b/lisp/dired.el
index 76499d0f520..620508bef4f 100644
--- a/lisp/dired.el
+++ b/lisp/dired.el
@@ -2728,7 +2728,8 @@ dired-find-file
 (defun dired--find-possibly-alternative-file (file)
   "Find FILE, but respect `dired-kill-when-opening-new-dired-buffer'."
   (if (and dired-kill-when-opening-new-dired-buffer
-           (file-directory-p file))
+           (file-directory-p file)
+           (= (length (get-buffer-window-list)) 1))
       (progn
         (set-buffer-modified-p nil)
         (dired--find-file #'find-alternate-file file))