🚀 go-pugleaf

In article <92345.101010KLASSEN@UVVM>
KLASSEN@UVVM.BITNET (Melvin Klassen) writes:
 
>BMahoney@LMSC.Lockheed.COM <6381710@LMSC5.IS.LMSC.LOCKHEED.COM> writes:
>>When I am editing a line at the bottom of the screen and that line 'wraps' so
>>that I cannot see more than the first 79 chars, as I use the Delete key the
>>characters to the right of my delete activity creep left toward my cursor as
>>the 'delete' eats up characters. Those characters that are wrapped and are not
>>on my screen when I start deleting do not creep back onto the screen at this
>>time and trailing blanks appear at the right end of the screen line. Okay- I
>>would simply expect to see the trailing characters that are off the screen
>>rejoin the text that I'm viewing when I press Enter or do some scrolling. But
>>in fact, when the wrapped line is redisplayed the rightmost characters stay
>>where they are and those blanks I saw on the screen are now actual spaces in
>>the text!!!!
>
>Since you must have used the 'SET VERIFY nn1 nn2' command to display only
>part of the logical record, XEDIT, by design(!), will only update those columns
>which you see on the screen.  If you use 'SET VERIFY 1 *', then XEDIT will
>wrap the logical line onto more than one physical line on your display,
>and the DELETE key does(!!!) cause text from the later physical lines to be
>pulled onto the first physical line, i.e., WYSIWYG editing.
 
This works for all but the last line on the screen.  If you "V 1 *",
and XEDIT cannot fit all of the last record on the screen, it displays
the amount that fits.  The DELETE key and ERASE EOF only affect the
portion on the screen, not the undisplayed portion.
 
Jim McMaster