[MUD-Dev] (fwd) Re: Issues from the digests and Wout's list

Chris Gray cg at ami-cg.GraySage.Edmonton.AB.CA
Sat May 10 09:45:12 New Zealand Standard Time 1997


[Oliver:]
:> Yup, thus I currently have the <ENTER> abort any incompleat commands,
:> with a clear visual signal on the screen that there is an incompleat
:> command.
:
:You might want to avoid using enter for this. I use enter as a 'redraw my
:current state' no-op, for when my connection starts lagging or if the
:terminal emulation goes ape - I don't know if others also do this, but
:having (no real input) actually change the state of your connection seems
:a bit counter-intuitive to me. Systems that close connection if you hit
:enter at the login screen bug me for this reason.

Good point - I thought something bothered me about that. gdb will repeat
the previous command if you just hit <ENTER>, and that has blown a long
debugging session for me in a couple of instances. Bad choice, I think.
I got to the point of always typing a command like "print 1", so that
if I did just hit <ENTER>, nothing bad would happen!

--
Chris Gray   cg at ami-cg.GraySage.Edmonton.AB.CA



More information about the MUD-Dev mailing list