[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tramp-connection-timeout have no effect

From: Thierry Volpiatto
Subject: Re: tramp-connection-timeout have no effect
Date: Sat, 22 Mar 2014 13:53:53 +0100
User-agent: mu4e; emacs

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)
           (setq stimers (with-timeout-suspend))
           ad-do-it) ; => tramp-read-password
      (with-timeout-unsuspend stimers)

Get my Gnupg key:
gpg --keyserver --recv-keys 59F29997 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]