Update of /services/emacs-rcp/cvsroot/rcp/texi
In directory bonny:/tmp/cvs-serv18160
Modified Files:
rcp.texi
Log Message:
Some todo items, and an explanation what happens behind the scenes.
[EMAIL PROTECTED] (Kai Großjohann) writes:
Sadly, the life of rcp.el is not so simple.
I think I might have been overly protective and defensive when
replying to your message, Dale. Now that I've thought about it, `hard
to implement' is a pretty lame excuse. Please do not refrain from
I think that something needs to be done about the end-of-line
convention of the *rcp/foo* buffers. Right now, I try to just send
`stty -onlcr -echo' to the remote end and hope that this is doing the
right thing. But it isn't. So.
How about this: after I see the first shell prompt, I erase the
"Tom Roche" [EMAIL PROTECTED] writes:
[...] It'd be nice if the user could specify (perhaps even by
server) a sequence of preferred transports. E.g. for ssh.ncsu.edu I
want only to transfer via scp; for ftp.ncs.ncsu.edu I want to
transfer via scp but will transfer via ftp if that fails; for
Now that Kai has added connection chaining and ability to use su, the
benefit of rcp.el is increased by an order of magnitude.
From a single Emacs session on the localhost, I can edit files owned
by other users (such as root) on my local box or on boxes behind
firewalls across the 'net. The
Martin Pool [EMAIL PROTECTED] writes:
~$ stty -onlcr -echo 1/dev/null 2/dev/null ; unset MAIL ; set +o
history 1/de
v/null 2/dev/null ; PS1='
/
'; PS2=''; PS3=''
I think I know what is happening. Due to `stty -onlcr' not being in
effect yet, PS1 contains "\n\n/\n\n"
Dale R Worley [EMAIL PROTECTED] writes:
The documentation for the entries in rcp-methods seems to be a bit
weak. It does specify what you're specifying, but it doesn't really
tell what will be done once the programs are run.
Thanks for this report. I have written up the following section
Or maybe it is possible to ask Emacs to frob the EOL convention
appropriately but leave everything else alone?
I think it would be better to make the basic case of talking iso-8859-1
work properly by default, and to provide a means for people to hook into
it and override it if that's not what
