RE: [UM1-coders] Ctl-S/Ctl-Q

[Adrian S. J. <AS...@pa...>]

> From: J.P. King [mailto:jp...@he...]
>=20
> > The trouble is that people will insist on using brain-dead clients
> > (MS Telnet is the obvious one) that wont do local line editing.
> > UM has had the line editing code for some considerable time now,
> > and it works as well as can be expected.
>=20
> Err, if people choose to use brain dead clients then they
> get what they deserve.  You cannot cater for everyone.

Please check our intended audience: Everyone.

> > The thing is that people have other needs (or desires), such as
> > Keith's avatar system, which would require some sort of session
> > management to remain sensible, otherwise we're going to have to
> > have a custom client, and then loose a large proportion of the
> > user base (or at least stop them from using the features).
>=20
> Umm, again, without having studied Keith's avatar system I am
> not sure why you would need to have a custom client interface
> thing for them.  you just do it a line at a time with prefixes
> on the lines to make it clear what is going on.

Yes, this was (briefly) discussed. It is messy, but workable.
However, how do you specify which avatar does the command you are
typing?

>  You don't want
> to make the system unusable for people who aren't using telnet,
> do you?
Please point me to where this would make it unusable.
Session capability need only be the equivalent of @swap (or similar)
that just changes your current avatar, and gives you the output that
you've missed (similar to using /world in tf).

<SNIP SSH & TELNET DISCUSSION>
>=20
> Again, I haven't given it much thought, but you'd have to put an
> obscene amount into UM1 in order to make it support clients, and
> even then this would tend to break things like TF and tush.

There is already a small amount of code that provides what we need.
We handle Telnet Options, use terminfo/termcap to get some of the
correct terminal options (we should really use it for the colours
as well, but since nobody is perfect...)

Has any of this broken TF or tush support? Have you noticed the
number of options available under 'set' (stupid name, should be
called something like setterm, probably at least an @ command).

So why not have a small amount of code for dealing with Ctl-S and
Ctl-Q, which are only going to be used by people not using tf and
tush (as they do local line editing for you).

> Julian

Adrian.