unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 13:02:24 +0300	[thread overview]
Message-ID: <83pm5aoclr.fsf@gnu.org> (raw)
In-Reply-To: <87fs66u0ox.fsf@gmx.de> (message from Michael Albinus on Sun, 02 Jul 2023 11:23:10 +0200)

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: tom@tomhunt.email,  64401@debbugs.gnu.org
> Date: Sun, 02 Jul 2023 11:23:10 +0200
> 
> What about
> 
> --8<---------------cut here---------------start------------->8---
> (defcustom remote-file-name-access-timeout 30
>   "Timeout (in seconds) for `access-file'.
> This timeout limits the time to check, whether a remote file is
> accessible.  `access-file' returns an error after that time.  If
> the value is nil, no timeout is used.
> 
> For slow connections, it might be useful to increase the value."
>   :group 'files
>   :version "30.1"
>   :type '(choice :tag "Timeout (seconds)" natnum (const nil)))
> --8<---------------cut here---------------end--------------->8---

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?

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

> 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?

Thanks.





  reply	other threads:[~2023-07-02 10:02 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 [this message]
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=83pm5aoclr.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).