From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: tramp questions
Date: Sun, 29 Feb 2004 18:48:56 +0100 [thread overview]
Message-ID: <87n0713hfb.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: c1qrju01i6j@enews3.newsguy.com
For ssh, you can fake it by adding an entry to ~/.ssh/config:
Host somealias
HostName the.real.host.name
User user@host
After this, check from the command line that "ssh somealias" logs you
in as user "user@host" on the real host. When this works, you can do
C-x C-f /ssh:somealias:/some/file RET.
Does this work?
Kai
next prev parent reply other threads:[~2004-02-29 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 19:53 tramp questions Michael Powe
2004-02-29 17:48 ` Kai Grossjohann [this message]
2004-03-01 15:40 ` Peter Lee
2004-03-01 15:57 ` Kai Grossjohann
2004-03-06 14:18 ` Michael Powe
-- strict thread matches above, loose matches on Subject: below --
2006-09-30 23:30 Ajit Mylavarapu
2006-10-01 16:25 ` Tim Heaney
2006-10-07 10:04 ` William Xu
[not found] <9d50c8be-46a0-436e-b02e-466d04ce6d54@t20g2000yqa.googlegroups.com>
2010-12-01 10:08 ` Tramp questions michael.albinus
2010-12-01 13:46 ` Gary
2010-12-01 23:51 ` Michael Albinus
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=87n0713hfb.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).