Using rcp.el when your .login asks questions

[Dale R Worley]

Success!  The magic formula is:

     ("scpx"   (rcp-connection-function  rcp-open-connection-rsh)
              (rcp-rsh-program          "ssh")
              (rcp-rcp-program          "scp")
              (rcp-rsh-args             ("-e" "none" "-t" "/bin/bash"))
              (rcp-rcp-args             nil)
              (rcp-rcp-keep-date-arg    "-p")
              (rcp-encoding-command     nil)
              (rcp-decoding-command     nil)
              (rcp-encoding-function    nil)
              (rcp-decoding-function    nil)
              (rcp-telnet-program       nil))

This causes the login to be done with "ssh -e none -t /bin/bash".
Since ssh is given a command, the remote shell is started in
"non-login" mode, which prevents it from processing the .login file.
Since -t is specified, sshd allocates a pty (which it otherwise
wouldn't do, since a command is given), and so /bin/bash and the
exec'd /bin/sh think they are interactive, and so product prompts.
(Needless to say, my .bashrc does not ask questions.)

Dale