From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: implementing a heartbeat for tramp
Date: Thu, 30 Oct 2003 21:22:21 +0000 [thread overview]
Message-ID: <87r80umnea.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: 877k2vpqjz.fsf@killr.ath.cx
Matthew Kennedy <mkennedy@gentoo.org> writes:
> My idea was to create a timer, which walked all emacs buffers looking
> for tramp buffers. When it found one, it would (maybe)
> `tramp-send-command' to send a heart-beat (I guess some kind of null
> operation... touch /dev/null??? -- or maybe the command itself
> suffices)
I think "echo heart-beat" would do fine :-)
Or maybe "echo hello", that's used in Tramp for other purposes
already, I think.
But maybe someone can come up with a really KEWL command that goes
well with the name Tramp?
Are you going to contribute your code? That would be just great.
Hm. Hmmm... Isn't there a keep-alive option for ssh? Just a
thought.
Kai
next prev parent reply other threads:[~2003-10-30 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 21:57 implementing a heartbeat for tramp Matthew Kennedy
2003-10-24 3:20 ` Dan Anderson
2003-10-30 21:22 ` Kai Grossjohann [this message]
2003-11-01 3:03 ` Matthew Kennedy
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=87r80umnea.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.de \
/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.
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).