From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: tom@tomhunt.email, 64401@debbugs.gnu.org
Subject: bug#64401: 28.1; Desktop restoration
Date: Sun, 02 Jul 2023 11:37:59 +0300 [thread overview]
Message-ID: <83sfa6ogig.fsf@gnu.org> (raw)
In-Reply-To: <87pm5au366.fsf@gmx.de> (message from Michael Albinus on Sun, 02 Jul 2023 10:29:37 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Tom Hunt <tom@tomhunt.email>, 64401@debbugs.gnu.org
> Date: Sun, 02 Jul 2023 10:29:37 +0200
>
> > Michael, does Tramp have optional behavior which would abandon attempt
> > to visit a file if it takes more than some predefined time?
>
> No, there isn't. And we cannot implement it for visiting files, because
> we don't know what would be an acceptable time period for visiting. There
> might be extremely huge files people try to visit over a slow connection.
>
> But what about extending the semantics of `access-file'? It should
> timeout after a given predefined time. The problem is how to find out
> this timeout value. For remote files, it depends on the quality of
> connection (and perhaps on the performance of the remote machine / file
> system), so we must make it configurable, with reasonable defaults.
Something like that would be useful, yes.
> This timeout might be even useful for local files. Think about hanging
> mount points and alike.
That could be trickier to implement, since AFAIR we call C APIs for
that.
next prev parent reply other threads:[~2023-07-02 8:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 17:52 bug#64401: 28.1; Desktop restoration Tom Hunt
2023-07-01 18:43 ` Eli Zaretskii
2023-07-01 18:46 ` Tom Hunt
2023-07-01 18:54 ` Eli Zaretskii
2023-07-02 8:29 ` Michael Albinus
2023-07-02 8:37 ` Eli Zaretskii [this message]
2023-07-02 9:23 ` Michael Albinus
2023-07-02 10:02 ` Eli Zaretskii
2023-07-02 10:36 ` Michael Albinus
2023-07-03 17:47 ` Michael Albinus
2023-07-04 13:30 ` Michael Albinus
2023-07-12 14:16 ` Michael Albinus
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=83sfa6ogig.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64401@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=tom@tomhunt.email \
/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).