Re: tramp-connection-timeout have no effect

[Thierry Volpiatto]

Thierry Volpiatto <address@hidden> writes:

> Thierry Volpiatto <address@hidden> writes:
>
>> Michael Albinus <address@hidden> writes:
>>
>>> And indeed, it is overwritten by another value for "sudo" in
>>> tramp-methods:
>>>
>>> --8<---------------cut here---------------start------------->8---
>>>  ("sudo"
>>>   (tramp-login-program "sudo")
>>>   (tramp-login-args
>>>    (("-u" "%u")
>>>     ("-s")
>>>     ("-H")
>>>     ("-p" "Password:")))
>>>   (tramp-remote-shell "/bin/sh")
>>>   (tramp-remote-shell-args
>>>    ("-c"))
>>>   (tramp-connection-timeout 10))
>>> --8<---------------cut here---------------end--------------->8---
>>
>> So what is the purpose of having a defcustom for `tramp-connection-timeout'?
>> (Setting it globally from here will have no effect on some methods)
>>
>> BTW 10s for sudo (and others) is far to low and annoying especially when
>> 2 passwd have to be entered (gpg+local).
>
> Wouldn't it make more sense to start the timeout _after_
> authentification, that is after having entered last password?

It is what I do now in helm:

  (let (stimers)
    (unwind-protect
         (progn
           (setq stimers (with-timeout-suspend))
           ad-do-it) ; => tramp-read-password
      (with-timeout-unsuspend stimers)

-- 
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997