Re: Obsolence of rlogin.el

[Michael Albinus]

Kalman Reti <address@hidden> writes:

Hi Kalman,

First of all let me say, that I don't intend to damage anybody's
workflow. That's why I have asked here.

> I use it every day with rlogin-program set to a non-default ssh client
> (which isn't suitable for other ssh uses, e.g. in tramp), so I would
> be sad if it went away.

That's not completely true. It isn't documented in Tramp how to use an
alternative ssh client, but it's possible. So pls give me some
information how this ssh client is invoked, and we'll find out how to
configure this in Tramp. (And I should document this finally,
long-lasting point from my TODO.)

> Using shell with the default directory couples the remote execution
> with remote file access which I find undesirable.

That I don't understand. Which kind of remote file access do you have in
mind? We're speaking 'bout rlogin, which opens a remote shell, and let
you enter shell commands.

> It is not very performant in the environments I use to access remote
> files via tramp. Using rlogin, I can do m-x cd to set the default
> directory for the rlogin buffer to a local (i.e. on the machine
> running emacs) path of the same filesystem I am using on the remote
> machine. In this case tracking of directory changes works correctly
> but I also have fast (local) tab completion and file opening.

But in this case I fail to understand what rlogin is good for you. If
you access local files, you don't need this.

Maybe you could give me a short scenario how you work with rlogin?

Best regards, Michael.