From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: Michael Albinus <michael.albinus@gmx.de>, 54606@debbugs.gnu.org
Subject: bug#54606: 27.1; next/previous image command in image-mode triggers tramp connections for all remote dired buffers
Date: Tue, 29 Mar 2022 15:03:14 +0200 [thread overview]
Message-ID: <87v8vwap2l.fsf@gnus.org> (raw)
In-Reply-To: <3947f11808243544dcdd4e4d2fde4922@webmail.orcon.net.nz> (Phil Sainty's message of "Mon, 28 Mar 2022 23:13:14 +1300")
Phil Sainty <psainty@orcon.net.nz> writes:
> ;; Find a dired buffer.
> (dolist (buffer (buffer-list))
> (with-current-buffer buffer
> (when (and (derived-mode-p 'dired-mode)
> (equal (file-truename dir)
> (file-truename default-directory)))
>
> That call to (file-truename default-directory) for each dired
> buffer can cause tramp to spin up for closed connections for
> entirely irrelevant dired buffers.
>
> Can we put some guards in there to decide whether or not dir
> and default-directory are actually on the same host before
> comparing them via file-truename?
Hm. Would binding `non-essential' around that call fix the issue? (I've
added Michael to the CCs.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-03-29 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 10:13 bug#54606: 27.1; next/previous image command in image-mode triggers tramp connections for all remote dired buffers Phil Sainty
2022-03-29 13:03 ` Lars Ingebrigtsen [this message]
2022-03-29 13:09 ` Michael Albinus
2022-03-30 11:43 ` Phil Sainty
2022-03-30 11:51 ` Michael Albinus
2022-03-30 12:03 ` Lars Ingebrigtsen
2022-03-31 9:47 ` Michael Albinus
2022-03-31 11:41 ` Lars Ingebrigtsen
2022-03-31 18:09 ` Phil Sainty
2022-04-01 7:06 ` Michael Albinus
2022-04-02 13:02 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8vwap2l.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=54606@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=psainty@orcon.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).