From: mert0407 AT sable DOT ox DOT ac DOT uk (George Foot) Newsgroups: comp.os.msdos.djgpp Subject: Re: RHIDE bug Date: 29 Apr 1997 13:00:03 GMT Organization: Oxford University, England Lines: 42 Message-ID: <5k4rcj$edf@news.ox.ac.uk> References: NNTP-Posting-Host: sable.ox.ac.uk To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Salvador Eduardo Tropea (SET) (salvador AT inti DOT edu DOT ar) wrote: : richard AT stardate DOT bc DOT ca (Richard Sanders) wrote: : > I have had a problem with the editor in RHIDE. Once in a while, the text : > (some of it) becomes mangled or rather, mixed up with very short lines. : > If you try and highlight a single line of text, you can't, 2-3 lines of text : > highlight. If you then copy and paste the highlighted text, it seems the : > pasted text comes out correctly, most of the time. This seems to occour when : > I am moving code around with copy/cut and paste. It also seems to appear only : > on the portion of the file that is in the edit window, but scrolling up/down : > does not "fix" the problem. I cannot re create the problem at will. : As I never saw that on 1.2 and as you don't provide a way to reproduce it I : can't do anything. If you determine when it happends I'll fix it. The machine I'm using right now doesn't have RHIDE so I can't verify this, but I had the same problem and IIRC it was connected with spaces on the ends of lines not being removed as they normally are. Something like moving the cursor past the end of a line, then selecting somewhere (I think it was downwards). It highlighted the blank space at the end of the line, and the next line up to the cursor position. Now (again IIRC) cutting the text will screw up the editor. I think a similar problem occurs if you copy the text then paste it somewhere else, too. Other symptoms are invisible text, garbage suddenly appearing when you start typing in the void area, incorrect syntax highlighting (particularly never-ending comments), and similar oddities. : > This has happened with 1.2 and 1.2a. I think I have 1.2a; again, this isn't my machine so I can't verify it. : Generally you can save the "mangled" file without risk, the best action to make : is save the file with a different name, close the window and reopen the file to : see if all is correct. IIRC all is correct on reopening the file (I actually close RHIDE out of habit, on the hunch that if it's lost track of its internal editor structure it may have corrupted something more important). -- George Foot Merton College, Oxford