DI Maximilian Renkin [EMAIL PROTECTED] writes:
mxrenkin@kastanie:~ # Initializing remote shell
$ exec /bin/sh
# Waiting 30s for remote `/bin/sh' to come up...
exec /bin/sh^M
mxrenkin@kastanie:~ # Setting up remote shell environment
exec /bin/sh^M
mxrenkin@kastanie:~ stty -echo^M
Kai Großjohann wrote:
"Daniel Pittman" [EMAIL PROTECTED] writes:
My guess is that the coding system isn't right in the buffer.
Could it be that this is caused by the timeout bug? In other words,
has the bug gone away with the recent timeout fix?
Max, could you please try this, too?
Kai Großjohann wrote:
DI Maximilian Renkin [EMAIL PROTECTED] writes:
Signaling: (error "Cannot subtract two times")
I have tried to fix this bug. The function subtract-time is new in
Emacs 21... New version in CVS and on ftp server.
kai
--
Beware of flying birch trees.
Using
DI Maximilian Renkin [EMAIL PROTECTED] writes:
Using SuSE 6.4, Gnu Emacs 20.6.1, rcp-1.329 I get another error now. The
Backtrace is:
=
Signaling: (wrong-type-argument number-or-marker-p (0 0))
rcp-wait-for-regexp(#process *rcp/su
DI Maximilian Renkin [EMAIL PROTECTED] writes:
Signaling: (error "Cannot subtract two times")
Which version of Emacs have you got? On XEmacs, it might help to
(require 'itimer).
kai
--
Beware of flying birch trees.
On Mon, 15 May 2000, Kai Großjohann [EMAIL PROTECTED]
wrote:
DI Maximilian Renkin [EMAIL PROTECTED] writes:
mxrenkin@kastanie:~ # Initializing remote shell
$ exec /bin/sh
# Waiting 30s for remote `/bin/sh' to come up...
exec /bin/sh^M
mxrenkin@kastanie:~ # Setting up remote shell
DI Maximilian Renkin [EMAIL PROTECTED] writes:
mxrenkin@kastanie:~ # Initializing remote shell
$ exec /bin/sh
# Waiting 30s for remote `/bin/sh' to come up...
exec /bin/sh^M
mxrenkin@kastanie:~ # Setting up remote shell environment
exec /bin/sh^M
mxrenkin@kastanie:~ stty -echo^M
#
Kai Großjohann wrote:
DI Maximilian Renkin [EMAIL PROTECTED] writes:
mxrenkin@kastanie:~ # Initializing remote shell
$ exec /bin/sh
# Waiting 30s for remote `/bin/sh' to come up...
exec /bin/sh^M
mxrenkin@kastanie:~ # Setting up remote shell environment
exec /bin/sh^M
Okay. I'm quite confused now. It appears that rcp.el is correctly
frobbing the coding system -- before frobbing the coding system, ^M
appeared in the buffer, and after frobbing the coding system, it was
foo-dos.
Hm. You may be seeing the timeout bug. I think I should be doing
something about
"Daniel Pittman" [EMAIL PROTECTED] writes:
My guess is that the coding system isn't right in the buffer.
Could it be that this is caused by the timeout bug? In other words,
has the bug gone away with the recent timeout fix?
Max, could you please try this, too?
Many thanks,
kai
--
Beware of
"Daniel Pittman" [EMAIL PROTECTED] writes:
My guess is that the coding system isn't right in the buffer.
But I am trying to frob it! Why does that not work? Could some
XEmacs expert have a look at the relevant section in rcp.el to find
out what might be wrong?
The string to search for is
My guess is that the coding system isn't right in the buffer.
Daniel
unset MAIL MAILCHECK MAILPATH 1/dev/null 2/dev/null
set +o history 1/dev/null 2/dev/null
PS1='
/
'; PS2=''; PS3=''
$ stty -echo
$ $ $
/
# Opening connection for danielp@bradbury using scp...
#
12 matches
Mail list logo
