home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dove!dove.nist.gov!przemek
- From: przemek@rrdstrad.nist.gov (Przemek Klosowski)
- Newsgroups: comp.sys.dec
- Subject: Re: DEC workstation user feedback
- Message-ID: <PRZEMEK.92Dec14082409@rrdstrad.nist.gov>
- Date: 14 Dec 92 13:24:09 GMT
- References: <PRZEMEK.92Dec12154829@rrdstrad.nist.gov> <11173347@zl2tnm.gen.nz>
- Sender: news@dove.nist.gov
- Organization: U. of Maryland/NIST
- Lines: 25
- In-reply-to: don@zl2tnm.gen.nz's message of 13 Dec 92 04:45:39 GMT
-
- In article <11173347@zl2tnm.gen.nz> don@zl2tnm.gen.nz (Don Stokes) writes:
-
-
- 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.
-
- But that is not what I meant!!! _Of course_ ESC cannot reliably be at
- the same time a command by itself and a command sequence prefix. But,
- if you have your way, escape may only prefix the keys that the vendor
- provided for you (arrow keys, keypad, whatever); why on earth should
- you disallow other commands that start with an escape key?
-
- I see that you mentioned vi, which indeed tries to use ESC in both
- capabilities. I say "dump vi, use emacs".
-
- --
- przemek klosowski (przemek@rrdstrad.nist.gov)
- Reactor Division (bldg. 235), E111
- National Institute of Standards and Technology
- Gaithersburg, MD 20899, USA
-
- (301) 975 6249
-