From: Philipp Haselwarter <philipp.haselwarter@gmx.de>
To: help-gnu-emacs@gnu.org
Subject: Re: edit a file over two linked ssh
Date: Sun, 20 Nov 2011 14:17:13 +0100 [thread overview]
Message-ID: <87r513hr1i.fsf@nzebook.haselwarter.org> (raw)
In-Reply-To: 8762ifujtt.fsf@gmx.de
On 2011-11-20 11:14 UT, Michael Albinus <michael.albinus@gmx.de> wrote:
---8<---[snipped 23 lines]---8<---
MA> If you take the recent Tramp sources from its CVS repository, you
MA> could use ad-hoc multi-hops:
MA> "/ssh:root@myfirstserver|ssh:root@mysecondserver:/var/www/myfile.txt"
MA> Best regards, Michael.
Neat! When's that getting merged into emacs?
--
Philipp Haselwarter
next prev parent reply other threads:[~2011-11-20 13:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-20 8:10 edit a file over two linked ssh mehran khajavi
2011-11-20 9:20 ` Peter Dyballa
2011-11-20 11:14 ` Michael Albinus
2011-11-20 13:17 ` Philipp Haselwarter [this message]
2011-11-20 13:30 ` Michael Albinus
2011-11-21 15:46 ` suvayu ali
2011-11-21 19:32 ` Michael Albinus
2011-11-21 23:03 ` suvayu ali
2011-11-22 5:33 ` Michael Albinus
2011-11-22 12:53 ` suvayu ali
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=87r513hr1i.fsf@nzebook.haselwarter.org \
--to=philipp.haselwarter@gmx.de \
--cc=help-gnu-emacs@gnu.org \
/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).