Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA1689 ; Tue, 23 Feb 93 14:53:43 EST Newsgroups: comp.os.386bsd.questions Path: sserve!manuel.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!mama!gary From: gary@mama.minmet.uq.oz (Gary Roberts) Subject: Re: patch to vi editor Message-ID: <gary.730202502@mama> Sender: news@bunyip.cc.uq.oz.au (USENET News System) Organization: Prentice Centre, University of Queensland References: <C2nKsx.9Mp@ux1.cso.uiuc.edu> <lo8q52INNgh@dimebox.cs.utexas.edu> <CGD.93Feb18210248@eden.CS.Berkeley.EDU> Date: Sat, 20 Feb 1993 10:01:42 GMT Lines: 51 cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes: >In article <lo8q52INNgh@dimebox.cs.utexas.edu> cloyce@cs.utexas.edu (Cloyce D. Spradling) writes: >>On a related note, has anyone but me experienced the problem of hitting 'dd' >>and having elvis erase the line *above* the one the cursor is on? >i've not seen this problem... however, sometimes it *appears* to have >deleted the line above the one w/the cursor, but hitting control-l >shows that it did, in fact delete the correct line... Sorry, there is a real problem here but my experience is a little different. I can reliably delete (with `dd') the line *below* the one the cursor is on. Here is a full description. 1. Start editing a file and arrow down to some line (say line 15). 2. Delete this line with `dd' -- no problem at this stage. 3. Undo deletion with `u' -- line 15 clearly reappears (with cursor on it). 4. Arrow up *just one* line (most important) and hit `dd'. 5. Cursor clearly on line 14 but line *15* is deleted (cursor still on 14). 6. Hit `u' and line 15 is restored with cursor still on line 14. The above behaviour happens every time as long as you only move up one line. Any more than one and the line the cursor is actually on will be deleted. Undoing the initial deletion before going up one line is also important. You might ask why I haven't reported this previously. I had seen it some time ago but was in a rush and didn't see the precise symptoms at the time. Cloyce's posting and your reply reminded me about it so I have just spent the last half hour rediscovering exactly what the symptoms are. I'm a BSD UNIX lover from way back but unfortunately not a programmer :-( I'm hoping some kind soul will know how to fix this -- seems it should be fairly simple :-) BTW: I'm using a stock standard distribution with just the 0.1 patchkit applied. I'm waiting for the dust to settle a bit before upgrading to the 0.2.? version :-). I'm very appreciative of the work that everyone is doing to bring patches out in a useable format. Keep up the good work. Hardware is 486DX-33 notebook with 16Meg, 320Meg IDE and 3Com ethernet. >chris >-- >Chris G. Demetriou cgd@cs.berkeley.edu > MENTALLY CONTAMINATED and proud of it! Cheers, Gary Roberts | Ph: +617-3654176 Mining & Met Engineering | Fax: +617-3654377 University of Queensland | Internet: gary@minmet.uq.oz.au Brisbane. 4072 AUSTRALIA |