From: Phil Sainty <psainty@orcon.net.nz>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 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: Thu, 31 Mar 2022 00:43:23 +1300 [thread overview]
Message-ID: <b2b01423d17b33974169d1e6d2193003@webmail.orcon.net.nz> (raw)
In-Reply-To: <878rssaos4.fsf@gmx.de>
On 2022-03-30 02:09, Michael Albinus wrote:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>> Phil Sainty <psainty@orcon.net.nz> writes:
>>> 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.
>>
>> Hm. Would binding `non-essential' around that call fix the issue?
>
> That's my expectation. It's on my TODO to test, but I'm occupied yet.
> Hope to fix this later this week.
I've just tested with this, and it solves the immediate problem, but
it's slow. In my test case it's taking ~2s to switch between images,
whereas it takes only a fraction of a second when I'm ignoring remote
dired buffers by adding (not (file-remote-p default-directory)) to
the conditions.
I have 15 remote dired buffers (about half of which are using multi-
hops), which isn't a small number but also isn't big, so I think that
`non-essential' seems inadequate here (unless this is significantly
more efficient in newer versions).
-Phil
next prev parent reply other threads:[~2022-03-30 11:43 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
2022-03-29 13:09 ` Michael Albinus
2022-03-30 11:43 ` Phil Sainty [this message]
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=b2b01423d17b33974169d1e6d2193003@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=54606@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
/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).