"Tom Roche" <[EMAIL PROTECTED]> writes:
> | $ PS1='
> | > /////
> | > '; PS2=''; PS3=''
> |
> | /////
> | @
>
> with cursor at '@'. The empty fourth line _is_ there.
So you get the same that I get. So it should work for you. But it
doesn't. I'm mystified.
Does anybody out there have any idea what might be wrong?
Tom, can you step through the function to watch it execute? The
function is rcp-open-connection-setup-interactive-shell, and the
interesting part starts where it is sending `set +o history'. It then
sends `unset ...', and then comes the most interesting part, of
setting the prompt and then waiting for the new prompt.
I suggest that you position point in the function and say M-x
edebug-defun RET. Then, with the rcp.el buffer showing, you start
rcp.el. When it stops, open a new frame (or window), showing the
*rcp/foo* buffer. Use SPC to step through the function
rcp-open-connection-setup-interactive-shell.
What do you see? Where does it go wrong? In particular, after
sending the prompt-setting command, why does rcp-wait-for-output not
find the result?
Hm.
Another thing to try might be to increase the number of seconds that
it is waiting for output (currently 5 seconds twice).
Hm.
Everybody, could the problem be that the remote shell doesn't display
the prompt before rcp-wait-for-output is finished, for some reason or
other?
kai
--
I like BOTH kinds of music.
