while searching for something else, I came across this email and decided
to reply.
On 11/1/99, Kai Gro�johann wrote:
>
> Jeffrey Juliano <[EMAIL PROTECTED]> writes:
>
> > I think the problem lies in a text/binary mode thing. ssh requires
> > cygwin be in the mode where it expects not to see ^M's at the end of
> > lines. ssh (as compiled) doesn't run if you don't put cygwin in this
> > mode. However, I suspect that emacs is piping into it dos-style EOL
> > characters.
>
> Hm. There is a variable rcp-rsh-end-of-line which is used. The
> default value is "\n" which led me into thinking that Unix-style EOLs
> would be used at all times.
>
> But of course, that was a foolish thing to do: I had completely
> forgotten about the automatic eol conversion done by Emacs. Does it
> help if you frob the process coding system of the SSH process? The
> function set-process-coding-system does this.
haven't had a chance to try this yet. I will after exams and projects
are over.
> If you find that changing the process coding system helps, I suggest
> that you set process-coding-system-alist such that the right coding
> system is used for SSH.
>
> However, I must admit that I had been restricting myself to Unixish
> systems when developing rcp.el -- I thought it wouldn't be possible to
> connect any other system via rsh (or telnet, or the like) anyway. But
> I had completely forgotten about the client side!
FYI, you can run sshd on a windowsNT/2000 machine. Many people do
this. The ssh sourcecode has been ported for use under cygwin,
http://sourceware.cygnus.com/cygwin and http://www.cygnus.com/cygwin.
inetutils are also available.
-jeff
