saunders@batcomputer.TN.CORNELL.EDU (kevin eric saunders) (09/23/86)
In article <2866@sdcc6.ucsd.EDU> ir450@sdcc6.UUCP () writes: > >I have NEVER had ANY experience with vi removing text and doing the >wierd things that the previous posters have stated, even when I was a >beginner with vi. Methinks the folks complaining probably had a mismatch between their TERM setting and their terminal, or a corrupted termcap entry. This can result in some *very* confusing screen displays. The file, of course, is just fine; too bad you can't see what you're entering. The sad choice between aztec Z (30% of vi, but 300 cps is *slow*) and the mouse-based editors (faster display, but like plowing a field with a hoe) is one I resolve by using either Z or using my own multi-window editor, dumb virtue, soon to be shareware. (Unfortunately this program uses TE and is limited to 32K, bleah. Had I but known how much trouble TE would be when I started out, I might have tried writing my own TE.) As for Mac/UNIX: simplifying UNIX itself == bowdlerization. I think the graphics/human interface box should be functionally if not physically separate from your UNIX CPU/disk server; communications interfaces are getting fast enough to make this work real nice. Thus, you can write some nice visual interface code to hide the UNIX text world commands without modifying UNIX itself; for those who want unadorned (? overadorned ?) UNIX, it's lying in wait underneath. How regular was my expression, kevin -- kevin eric saunders ARPA: kevin@lasspvax or kevin%lasspvax.tn.gvax.edu@cu-arpa UUCP: {ihnp4, allegra,...}!gvax!lasspvax!kevin
tim@ism780c.UUCP (Tim Smith) (09/25/86)
In article <1066@batcomputer.TN.CORNELL.EDU> saunders@batcomputer.UUCP (kevin eric saunders) writes: >> >>I have NEVER had ANY experience with vi removing text and doing the >>wierd things that the previous posters have stated, even when I was a >>beginner with vi. > >Methinks the folks complaining probably had a mismatch between their >TERM setting and their terminal, or a corrupted termcap entry. This >can result in some *very* confusing screen displays. The file, of >course, is just fine; too bad you can't see what you're entering. > The ones I have seen are often caused by terminals that send sequences for function keys faster than the host can handle them. The host misses a character or two, and you end up with a random command. This can lead to a corrupt file. It is a good thing vi has an UNDO command! I have seen this happen on 68k unix boxes, and on a pc6300+. I am pretty sure I have also seen it on vaxes. -- What's the difference between a duck? Tim Smith USENET: sdcrdcf!ism780c!tim Compuserve: 72257,3706 Delphi or GEnie: mnementh