Fix error from reverting to nonexistent directories

[CeleritasCelery]

when a dired buffer exists for a directory that has been deleted, dired-async's callback will throw an error. This is a simple fix for that.

[thierryvolpiatto]

Troy Hinckley notifications@github.com writes:

when a dired buffer exists for a directory that has been deleted, dired-async's callback will throw an error. This is a simple fix for that.

• do (with-current-buffer b
• (when (file-exists-p default-directory)
• (revert-buffer nil t)))))

What about something like

(when (and (not (file-remote-p default-directory nil t))
           (file-exists-p default-directory))
  (revert-buffer nil t)))))

to avoid trigerring a new tramp connection to a possible remote default-directory?

-- Thierry

[CeleritasCelery]

Won’t revert-buffer trigger a new connection anyways?

[thierryvolpiatto]

Troy Hinckley notifications@github.com writes:

Won’t revert-buffer trigger a new connection anyways?

Yes, I think so, but file-directory-p triggers a connection too, so if the dired buffer results from an old connection, IMO it is not needed to reenable the connection in the back of user.

-- Thierry

[CeleritasCelery]

done

[thierryvolpiatto]

Thanks.