Re: Obsolence of rlogin.el

[Michael Albinus]

Kalman Reti <address@hidden> writes:

Hi Kalman,

> I build and test a single set of sources on a dozen different
> platforms; each platform copies its sources from a 'master' sandbox
> (so I am certain all have the exact same sources).
>
> I have elisp code that generates a dozen rlogin buffers (to all the
> platforms) and other functions which send commands to all of them and
> analyze what comes back, e.g. build or test failures. If I have to
> make changes, I make them to files in the 'master' sandbox which
> resides on a shared filesystem (either nfs or samba, depending upon
> whether my emacs is running on linux or windows) that is local as far
> as emacs is concerned. The hierarchy of files in the sandboxes on the
> various machines mirrors the hierarchy of that master sandbox, so I
> m-x cd the corresponding master patch to each rlogin buffer, so
> opening a source file opens the corresponding master source file, not
> the one in the remote sandbox. Tab completion of common files works
> because I only do relative cd'ing inside each of the shells. If I need
> to look at a generated file on the remote machine, I explicitly
> provide the host name, but that's fairly rare. It is important to me
> that if I open a file while the current buufer is any of the remote
> rlogin buffers, I get the canonical file from the master sandbox
> (which may already have been open previously). I don't know how to get
> this effect using tramp and/or remote shell buffers.

Sounds to me like you need shadowfile.el. With this package, you could
define clusters, which implement a similar feature as you apply, keeping
several files in sync on different hosts, once one of the files is
changed.

Unfortunately, shadowfile.el lacks the same problem as rlogin.el does:
it is based on ange-ftp. So it must be adapted to Tramp. I've started
this rewrite a while ago, but it is half-baken only. Maybe I shall
continue this work, with pressure from you :-)

For the time being, we could try to solve your other problem, that you
couldn't use Tramp due to your special ssh client. Do you like to send
me the details, that we could find out how to configure Tramp to
support you?

Best regards, Michael.