"Rohit Verma" <[EMAIL PROTECTED]> writes: > Is there any way to enable remote editing of files on Xemacs/Win32 > using scp? In the following message, you find a description for NT Emacs; apparently one has to frob ssh a bit, and then one needs to patch rcp.el. See the message for details. I'll try to incorporate the rcp.el related changes into the distribution, but I've got to find time, first. kai -- A large number of young women don't trust men with beards. (BFBS Radio)
>* Does emacs-rcp work with NT Emacs? I'm currently using GNU Emacs > 20.4.1 (i386-*-nt4.0.1381) of Thu Jul 15 1999 on gridlock Yes. I Have been revving up to announce this for a week or two, but the end of term etc. has got in the way. I have got rcp.el to work with NTemacs 20.4 and ssh/scp. The version of the latter tools I started from is the one in http://sunsite.org.uk/packages/ssh/contrib/ssh-1.2.22-Win32-Beta1.zip http://sunsite.org.uk/packages/ssh/contrib/ssh-1_2_22-Win32-Beta1-src.zip for the binary and sources respectively (also available in many mirrors elsewhere). I had to tweak ssh.c, scp.c and rcp.el a little, as described below. I believe my changes to rcp.el do not break things that worked already, so I hope they can be incorporated in the standard version -- but of course that's up to Kai. Changes to ssh.c * to allow it to run interactively when connected to emacs (i.e. when not connected to a terminal window), by letting it honour the -t command option in such circumstances; * to treat ssh.exe etc. as program names rather than host names Changes to scp.c * to ensure that it opens its files in binary mode (otherwise the byte counts go all wrong); * to treat a single letter and a colon at the start of a file name as a local volume letter rather than a remote host name; Changes to rcp.el * to remove various assumptions that the local system is the same OS as the remote one (the remote one is assumed to be a Unix); * to revise the auto-save arrangements a little (see separate message); * to allow empty components in rcp filenames; * to be a little more picky than Unix about the characters allowed when inventing filenames. I've parked the things I've changed in ftp://ftp.comlab.ox.ac.uk/tmp/Joe.Stoy/ for the time being, together with diff files. I'll try to put a README file there soon, with a word or two of explanation; but email me if you need help more urgently. To generate keys, etc. you'll need to get the rest of the ssh distribution from a site such as that given above; and you'll need some stuff from CYGWIN's usertools.exe . >Increasingly offtopic: > >* I've been meaning for a while to install cygwin to get its scp, > among other things. How good is its scp? I don't think it has one. But the version I've been using needs the cygwin library and (on NT systems) an /etc/passwd file created by a cygwin utility (to mirror the information in NT's registry). >* Does anyone know of a graphical scp client for NT? The best solution > I've found is port-forwarding WS-FTP through TeraTerm, but I'm I've got that to work too (with ftp in passive mode). But notice that although that sends the control channel down the ssh tunnel (so that passwords are sent encrypted), the data stream goes down a separate channel, outside the tunnel, in clear. Some people say that's no problem, since any information that's the least bit sensitive should have been encrypted already, before it got anywhere near a file system; but not all users thrill to that approach ... >TIA, [EMAIL PROTECTED] Best wishes joe stoy
