>>>>> "Edward" == Edward J Sabol <[EMAIL PROTECTED]> writes:
> My biggest concern with unleashing rcp.el on the masses is what I think is
> going to be a very common problem that people will encounter when using
> rcp.el. Specifically, rcp.el just doesn't work if you have a {setenv TERM
> `tset -I -Q - "?vt100"`} or similar command in your .login file. I don't know
> about your account, but I think that's pretty common. It's too bad ssh
> doesn't provide a way to acquire a non-login shell. One thing that might be
> able to help in regards to this problem is to send a few CRs through the
> connection if a command prompt doesn't show up after so many seconds when
> logging in. The only other thing that could help is ample documentation of
> the potential problem.
I really hope the code will not go through hoops to try and handle
those brain-dead cases. It would probably be good to detect those
situations and COMPLAIN LOUDLY, so that maybe 20 years from now,
standard .login files won't be as brain dead as they tend to be nowadays.
Stefan "who's never ever needed tset"
