unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tom@tomhunt.email, 64401@debbugs.gnu.org
Subject: bug#64401: 28.1; Desktop restoration
Date: Sun, 02 Jul 2023 12:36:36 +0200	[thread overview]
Message-ID: <87h6qm38i3.fsf@gmx.de> (raw)
In-Reply-To: <83pm5aoclr.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 02 Jul 2023 13:02:24 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

Hi Eli,

> Sounds good.  Regarding the default value: how long does it take for
> access-file to do its job with "normal" connections?  Maybe 30 is too
> long, and something like 10 will be better?

OK, let's start with this.

> Also, the implementation should probably "remember" the result and
> apply it to all the other files on the same volume?

Hmm, this will be harder. `access-file' could fail for different
reasons. And Tramp does not know whether two remote files belong to the
same volume. Well, there is `file-attribute-device-number', but this is
not trustworthy for all different kind of remote file systems.

I'll see whether I can implement a cache for different volumes on remote
hosts where it makes sense.

>> Implementation note: This would be the timeout if the connection is
>> already established. If there is no connection yet, Tramp would add that
>> initialization time. Establishing a new connection is always limited by
>> a reasonable timeout.
>
> You mean, we already have a timeout for new connections?  If so, why
> didn't the OP see its effect?

Don't know, I would need the traces. Tom, could you please start "emacs
--eval '(setq tramp-verbose 10)'" and reproduce the problem? There will
be a Tramp debug buffer, which you could show us.

> Thanks.

Best regards, Michael.





  reply	other threads:[~2023-07-02 10:36 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
2023-07-02  9:23           ` Michael Albinus
2023-07-02 10:02             ` Eli Zaretskii
2023-07-02 10:36               ` Michael Albinus [this message]
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=87h6qm38i3.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=64401@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).