From: Juri Linkov <juri@linkov.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Mikhail P <mikpom@fastmail.com>, 45256@debbugs.gnu.org
Subject: bug#45256: Viewing images over network using TRAMP (errors and unexpected prompts)
Date: Wed, 16 Dec 2020 22:52:05 +0200 [thread overview]
Message-ID: <87zh2djyc2.fsf@mail.linkov.net> (raw)
In-Reply-To: <87360615l3.fsf@gmx.de> (Michael Albinus's message of "Wed, 16 Dec 2020 10:08:08 +0100")
> That is, two calls of timer-event-handler([t 0 1 0 nil image-fit-to-window ...])
>
> image-fit-to-window calls remote file operations,
> verify-visited-file-modtime the first time, file-readable-p the second
> time. The first call of image-fit-to-window hasn't finished, when the
> second call of image-fit-to-window happens one second later. That is
> relevant, this situation happens only for slow remote connections (I had
> a hard time to reconstruct the scenario).
>
> From my pov, image-fit-to-window must be hardened in order to avoid this
> reentrant call. Maybe an internal lock at entry, which is honored by
> every next call until the lock is removed.
The simplest solution is just to increase the number of seconds
in the user option 'image-auto-resize-on-window-resize'
proportionally to network latency.
Locking could be implemented as well. How would be better to do this?
Maybe by using a buffer-local variable?
next prev parent reply other threads:[~2020-12-16 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 12:17 bug#45256: Viewing images over network using TRAMP (errors and unexpected prompts) Mikhail P
2020-12-16 9:08 ` Michael Albinus
2020-12-16 20:52 ` Juri Linkov [this message]
2020-12-17 8:44 ` Michael Albinus
2020-12-17 21:59 ` Juri Linkov
2020-12-18 8:05 ` Michael Albinus
2020-12-18 8:29 ` Juri Linkov
2020-12-18 9:58 ` Michael Albinus
2020-12-19 20:19 ` Juri Linkov
2020-12-22 14:49 ` Mikhail Pomaznoy
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=87zh2djyc2.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=45256@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=mikpom@fastmail.com \
/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).