Steve Acheson <[EMAIL PROTECTED]> writes:
[ About an lsh command mode ]
> I think this would be useful too, but what the original ssh purpose was,
> and I think lsh should at least be aware of, is to be compatible with the
> Berkeley R* commands (rsh, rcp, rlogin). This is where the /n~ comes
> from.
rsh (and ssh) use \n~x to perform certain actions (x=.
disconnects, x = ^Z stops the process, and a few more). I think that a
command mode could be attached to, say, x=\n, without breaking the
existing actions. This is a little different from telnet, which drops
you to the command prompt immediately when you press the escape
character, by default ^]. I haven't used kermit for a few years, but I
seem to remember that it is more like telnet than rsh in this respect.
> If you turn this into a "command" mode requiring additional
> keys (ala Kermit?) you will break lots of existing scripts that might
> depend on this capability (I've only ever once done such a thing, and
> would never do it again, esp with perl available).
Are you saying that you used the escape character from scripts? To me,
the escape character looks like a feature designed for interactive use
only. When doing, for instance, tar cf - | ?sh ..., I think the
escape feature *should* be disabled by default, but I haven't tested
what rsh and ssh do when used non-interactively. Otherwise, bad things
may happen if the tar file happens to contain the string \n~.
I think that the Right Thing is to enable the escape character by
default iff stdin is connected to a tty.
/Niels
