unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Chris Withers <chris@simplistix.co.uk>
To: help-gnu-emacs@gnu.org
Subject: remote file editing over ssh with emacs 22.3.1 on Windows
Date: Thu, 07 May 2009 09:48:15 +0100	[thread overview]
Message-ID: <4A02A04F.6010307@simplistix.co.uk> (raw)

Hi All,

I'm trying to get remote editing working using ssh.

I've copied in the the relevant tramp stuff from 
http://www.redantigua.com/emacs-win.html
...to my ~/_emacs files, although I'm using the tramp that came with 
emacs 22.3.1, not a separately downloaded one.

The first problem I hit was that the remote machine's key was not in the 
registry, so tramp/plink stalled with the following in its buffer:

"""
The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's rsa2 key fingerprint is:
ssh-rsa 2048 cc:7f:79:8a:20:04:b7:39:6c:a7:3e:4f:ea:4f:b1:e3
If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n)
"""

How can I interact with this to say "yes"?

Anyway, I worked around that problem by connecting using plink.exe in a 
dos box and caching the key.

This gets further now, but takes an awful long time with the message:
'tramp: Setting up remote shell' showing before bombing. Here's the 
chunk from the Messages buffer:

tramp: Opening connection for cwithers@server1.simplistix.co.uk using nil...
tramp: Waiting for prompts from remote shell
tramp: Waiting 60s for prompt from remote shell
tramp: Found remote shell prompt.
tramp: Initializing remote shell
Loading time-date...done
tramp: Waiting 30s for remote `/bin/sh' to come up...
tramp: Setting up remote shell environment
apply: Couldn't `stty -inlcr -echo kill '^U'', see buffer `*tramp/plink 
cwithers@server1.simplistix.co.uk*'

The tramp/plink buffer contains:

stty -inlcr -echo kill '^U'
$ $

Can someone point me to what's gone wrong and how I can fix it?

cheers,

Chris

-- 
Simplistix - Content Management, Zope & Python Consulting
            - http://www.simplistix.co.uk




             reply	other threads:[~2009-05-07  8:48 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07  8:48 Chris Withers [this message]
2009-05-07 18:27 ` remote file editing over ssh with emacs 22.3.1 on Windows Eli Zaretskii
2009-05-07 18:48   ` Ian Eure
2009-05-08 21:18     ` Chris Withers
2009-05-08 21:19       ` Ian Eure
2009-05-08 21:23         ` Chris Withers
2009-05-09  7:05       ` Eli Zaretskii
2009-05-09  8:49         ` Chris Withers
2009-05-09  9:27           ` Eli Zaretskii
2009-05-09 17:41             ` Chris Withers
2009-05-09 19:09               ` Eli Zaretskii
2009-05-10  8:37                 ` Chris Withers
2009-05-10 17:29                   ` Eli Zaretskii
2009-05-10 18:23                   ` Peter Dyballa
2009-05-16 16:57                     ` Chris Withers
     [not found]                 ` <mailman.6949.1241969740.31690.help-gnu-emacs@gnu.org>
2009-05-11 21:18                   ` Anselm Helbig
2009-05-16 16:59                     ` Chris Withers
2009-05-23 20:02                       ` Michael Albinus
2009-05-25 15:40                         ` Chris Withers
2009-05-26 20:50                           ` Michael Albinus
2009-05-30 12:26                             ` remote file editing over ssh with emacs 22.3.1 on Windows/Mac Chris Withers
2009-05-30 12:35                               ` Michael Albinus
2009-06-08 12:06                               ` remote editing of unix files over ssh with emacs 22.3.1 from Windows Chris Withers
2009-06-08 12:39                                 ` Michael Albinus
2009-06-08 12:58                                   ` Chris Withers
2009-06-08 13:08                                     ` Michael Albinus
2009-06-12 15:38                                       ` Chris Withers
2009-06-08 12:51                                 ` Peter Dyballa
     [not found]                     ` <mailman.7269.1242493182.31690.help-gnu-emacs@gnu.org>
2009-05-16 18:21                       ` remote file editing over ssh with emacs 22.3.1 on Windows Anselm Helbig
2009-05-25 15:44                         ` Chris Withers
2009-05-09 18:04           ` Peter Dyballa
2009-05-09 18:05             ` Chris Withers
2009-05-09 19:40               ` Peter Dyballa
2009-05-16 17:01                 ` Chris Withers
2009-05-16 18:26                   ` Peter Dyballa
     [not found]                 ` <mailman.7270.1242493264.31690.help-gnu-emacs@gnu.org>
2009-05-17  1:59                   ` Tim X
2009-05-25 15:50                     ` Chris Withers
     [not found]             ` <mailman.6908.1241895850.31690.help-gnu-emacs@gnu.org>
2009-05-10  8:43               ` Anselm Helbig
2009-05-10  8:50                 ` Richard Riley
2009-05-16 17:03                 ` Chris Withers
     [not found]                 ` <mailman.7271.1242493390.31690.help-gnu-emacs@gnu.org>
2009-05-16 17:54                   ` Anselm Helbig
2009-05-10  7:28           ` Reiner Steib

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=4A02A04F.6010307@simplistix.co.uk \
    --to=chris@simplistix.co.uk \
    --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).