It appears that tramp closes its ssh connection to a given host when
the last buffer connected with that host is killed. If I subsequently
open another file on that host, I must then wait through the login,
etc.
Is there a way to instead make tramp leave the connection open until I
close
On Mon, 09 Apr 2001, Tom Roche wrote:
It appears that tramp closes its ssh connection to a given host when
the last buffer connected with that host is killed.
I think Tramp never closes connections.
But Tramp could try to keep connections open, thwarting the idle
timeout imposed by ssh,
Enter your bug report in this message, including as much detail as you
possibly can about the problem, what you did to cause it and what the
local and remote machines are.
If you can give a simple set of instructions to make this bug happen
reliably, please include those. Thank you for helping
On Mon, 09 Apr 2001, Tom Roche wrote:
It appears that tramp closes its ssh connection to a given host
when the last buffer connected with that host is killed.
[EMAIL PROTECTED] 09 Apr 2001 21:52:09 +0200
I think Tramp never closes connections.
I agree: looking back, with what I know now, I
