Geek asks and answers

Dired-x: How to install "Kill the buffer ... too?" to yes without confirmation?

If you delete the file fooin dired-x, you will be asked Kill buffer of foo, too?. How can I skip this question and always answer it with yes?

+5
source share
2 answers

Just override the dired-clean-up-after-deleting function in dired-x.el.

;; redefine the definition in dired-x.el, so that we are not prompted
;; to remove buffers that were associated with deleted
;; files/directories

(eval-after-load  "dired-x" '(defun dired-clean-up-after-deletion (fn)
  "My. Clean up after a deleted file or directory FN.
Remove expanded subdir of deleted dir, if any."
  (save-excursion (and (cdr dired-subdir-alist)
                       (dired-goto-subdir fn)
                       (dired-kill-subdir)))

  ;; Offer to kill buffer of deleted file FN.
  (if dired-clean-up-buffers-too
      (progn
        (let ((buf (get-file-buffer fn)))
          (and buf
               (save-excursion ; you never know where kill-buffer leaves you
                 (kill-buffer buf))))
        (let ((buf-list (dired-buffers-for-dir (expand-file-name fn)))
              (buf nil))
          (and buf-list
               (while buf-list
                 (save-excursion (kill-buffer (car buf-list)))
                 (setq buf-list (cdr buf-list)))))))
  ;; Anything else?
  ))
+5
source

You can recommend a function dired-delete-entryso that all file buffers are closed before deletion:

(defadvice dired-delete-entry (before force-clean-up-buffers (file) activate)
  (kill-buffer (get-file-buffer file)))

The Elisp manual describes it as “cleaner than redefining an entire function,” and is less likely to break if the definition of a function changes in the future.

+8
source

More articles:


All Articles