I just began using rcp.el a few days ago and I like where this is
headed.
A problem, though:
When I want open the following file,
/r@slm:user_other_than_me@other_machine:/file/there
I can see that rcp.el has logged me in, but it gives me the message:
Remote /bin/sh didn't come up. See buf
[EMAIL PROTECTED] (Mark A. Hershberger) writes:
> More regexps?
I wonder whether (a) the general error detection method worked and (b)
it is sufficient.
The general error detection method is that rcp.el should time out
waiting for the shell prompt (after 60 seconds¹) and say that it
couldn't fi
> 'sallright. If I you give me a pointer to something to read to
> understand how to single-step through the code, that'd be great.
If you use Xemacs there is an info node. GNU Emacs seems to lack such a
beast. That's annoying. There is still the keybinding stuff in debug
mode
On 19 Oct 1999, Mark A. Hershberger <[EMAIL PROTECTED]> wrote:
> I just began using rcp.el a few days ago and I like where this is
> headed.
>
> A problem, though:
[...]
> I can see that rcp.el has logged me in, but it gives me the message:
>
> Remote /bin/sh didn't come up. See buffer `*rcp
[forgot to CC list]
> "KG" == Kai Großjohann <[EMAIL PROTECTED]> writes:
KG> [EMAIL PROTECTED] (Mark A. Hershberger) writes:
KG> I'm quite reluctant to reduce the timeout because starting a
KG> remote shell might take quite some time. Do you think that
KG> more messages are
> "KG" == Kai Großjohann <[EMAIL PROTECTED]> writes:
KG> You said that rcp.el was hanging. Did it not time out at all?
Ok... You are right. It timed out.
Mark.
Mark A. Hershberger <[EMAIL PROTECTED]> writes:
> Daniel Pittman <[EMAIL PROTECTED]> writes:
> > Do you have enough elisp to breakpoint in 'rcp-open-connection-rlogin'
> > and single-step the code to see where it is losing it?
>
> If you can give me a pointer, I will.
I suggest putting point in
[EMAIL PROTECTED] (Mark A. Hershberger) writes:
> I just began using rcp.el a few days ago and I like where this is
> headed.
>
> A problem, though:
>
> When I want open the following file,
>
> /r@slm:user_other_than_me@other_machine:/file/there
>
> I can see that rcp.el has logged me in, bu
> Does it work if you modify rcp.el to say +onlcr rather than -onlcr?
Nope. I get "unknown mode: +onlcr" tried this manually.
The syntax should be "-onlcr" to turn it off, and "onlcr" to turn it on.
Daniel Pittman <[EMAIL PROTECTED]> writes:
> Do you have enough elisp to breakpoint in 'rcp-open-connection-rlogin'
> and single-step the code to see where it is losing it?
If you can give me a pointer, I will.
> That should give a debug buffer for the connection with all the output
> logged. D
On 19 Oct 1999, Mark A. Hershberger <[EMAIL PROTECTED]> wrote:
> Here is what I get from an manually slogging in and executing the
> commands:
>
> --- cut ---
> [other_machine:/]# exec /bin/sh
> [h:w]$ PS1=''; PS2=''; PS3=''
> stty -onlcr -echo
> hello
> //
> --- cut ---
>
> Seems to m
Hi all,
I have talked to Kai about my rcp.el phenomena, some similar stuff to
what was at the root of this thread, while trying to connect to an
ssh1 server. I thought this might be of interest.
Here is the output of the /r@slm buffer following an abortive attempt
to login with a current versio
> "KG" == Kai Großjohann <[EMAIL PROTECTED]> writes:
KG> I have now tried to add more (and hopefully useful) messages.
These work much better so far... Thanks.
Mark.
Here is what I get from an manually slogging in and executing the commands:
--- cut ---
[other_machine:/]# exec /bin/sh
[h:w]$ PS1=''; PS2=''; PS3=''
stty -onlcr -echo
hello
//
--- cut ---
Seems to me that it does what is expected (at least manually). If it
helps, other_machine is an
Kai Großjohann writes:
> Mark A. Hershberger <[EMAIL PROTECTED]> writes:
>
> > [EMAIL PROTECTED] (Kai Großjohann) writes:
> >
> > > Does it work if you modify rcp.el to say +onlcr rather than -onlcr?
> >
> > Nope. I get "unknown mode: +onlcr" tried this manually. Thanks,
> > though.
[EMAIL PROTECTED] (Mark A. Hershberger) writes:
> I don't see a "waiting ..." msg with rcp-verbose set to 10.
I have now tried to add more (and hopefully useful) messages.
kai
--
~/.signature: No such file or directory
Mark A. Hershberger <[EMAIL PROTECTED]> writes:
> --- cut ---
> [other_machine:/]# exec /bin/sh
> [h:w]$ PS1=''; PS2=''; PS3=''
> stty -onlcr -echo
> hello
> //
> --- cut ---
Does it work if you modify rcp.el to say +onlcr rather than -onlcr?
kai
--
Life is hard and then you die.
Mark A. Hershberger <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Kai Großjohann) writes:
>
> > Does it work if you modify rcp.el to say +onlcr rather than -onlcr?
>
> Nope. I get "unknown mode: +onlcr" tried this manually. Thanks,
> though.
Well, maybe that's the default. So another thi
On 20 Oct 1999, Mark A. Hershberger <[EMAIL PROTECTED]> wrote:
> Daniel Pittman <[EMAIL PROTECTED]> writes:
>> Do you have enough elisp to breakpoint in
>> 'rcp-open-connection-rlogin' and single-step the code to see where it
>> is losing it?
>
> If you can give me a pointer, I will.
Hmmm. Bein
[EMAIL PROTECTED] (Mark A. Hershberger) writes:
> > "KG" == Kai Großjohann <[EMAIL PROTECTED]> writes:
>
> KG> You said that rcp.el was hanging. Did it not time out at all?
>
> Ok... You are right. It timed out.
Very good. I take it that it also popped up the *rcp/foo* buffer with
a
> "KG" == Kai Großjohann <[EMAIL PROTECTED]> writes:
KG> Did you change anything? What?
It's been so long... and I'm working at a different company now. But
give me a sec...
Well, one reason it isn't a problem is because there is no longer an
slm method. I tried tm, and that works.
21 matches
Mail list logo
