🚀 go-pugleaf

przemek@rrdstrad.nist.gov (Przemek Klosowski) writes:
> Well, I am not sure if you are serious or joking. If you are serious, 
> I would just say that I want my work done; my understanding of ANSI
> escape sequences is that it is a standard for commands sent TO THE 
> CHARACTER-BASED TERMINALS. The usurpation of ESC for keystrokes send
> _from_ my Xterm is just unreasonable. What would be a reason for it,
> besides an overwhelming desire to literally obey?
> 
> A standard is just that: a standard way of doing things. As far as I
> know, only DEC insists on interpreting the ANSI standard for display
> commands as prohibiting the existence of an ESC keyboard key.

The VT100 keycodes are something of a de facto standard.  These (usually)
start with an ESC and follow the ANSI sequences.

Treating ESC as a keystroke is asking for trouble.  If an application 
receives an ESC, it can either treat it as one character or as a lead
in to a multiple character sequence.  IT CANNOT DO BOTH.  Instead, we 
have disgusting kludges like waiting a period of time for a following 
character and calling it a sequence if we get it or a bare ESC if we
don't.  Every time vi gets this wrong I want to go and KILL the STUPID
BLOODY FOOL who did this, and get the bad genes off the planet.

Death to the bare ESC, once and for all!

--
Don Stokes, ZL2TNM (DS555)                        don@zl2tnm.gen.nz (home)
Network Manager, Computing Services Centre            don@vuw.ac.nz (work)
Victoria University of Wellington, New Zealand              +64-4-495-5052