I think maybe the teminal handler is too smart for it's own good?. There
are 78 characters in the row, and 78 characters wide on the screen, so
when it gets to the end of the line it realizes it's at the end and will
autowrap to the next line--so no need for a carriage return. In fact a
carriage return would probably insert an extra unwanted line on the
display.
So, possibilities:
1. set your terminal width wider.
2. Use a different term type that doesn't support auto-wrap
3. Instead of executing with capture, print to a hold file, and then
process the hold file entry.

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett
> Sent: Wednesday, January 18, 2006 5:20 PM
> To: [email protected]
> Subject: [U2] [UD] list output when captured
> 
> I've got a simple scroll routine that parses the output from 
> a LIST or SORT command's "CAPTURING" variable of an EXECUTE 
> statement.  The routine tests for the 2nd empty line to 
> determine when the column heading ends and the data begins, 
> as all output with a heading puts a blank line between the 
> column heading and the data.
> 
> So, typical captured output would look like:
> 
> SCRATCH(1)=Dictionary of File: PERIPHERALS                    
>   16:05:08 Jan
> 18
> 2006^Dict Name...... Typ # Col-Heading.... Field-Def... 
> Conversion.. Formt Assoc
> ...^^@               Phr                   LPTRNO DEV_N^
> .
> .
> 
> The total width of the heading is 78 characters, while the 
> TERM width is 79. If I were to change the TERM width to 78 
> then rerun the above listing the extra line between the 
> column heading and the 1st row of data disappears (the first 
> of two attribute marks changes to a space).
> 
> SCRATCH(1)=Dictionary of File: PERIPHERALS                    
>   16:05:08 Jan
> 18
> 2006^Dict Name...... Typ # Col-Heading.... Field-Def... 
> Conversion.. Formt Assoc
> ... ^@               Phr                   LPTRNO DEV_N^
> .
> .
> 
> Is there a reason why this occurs (I've not seen this before) 
> or will I just have to be careful in the future?
> 
> As always, thanks.
> 
> Bill Haskett
> -------
> u2-users mailing list
> [email protected]
> To unsubscribe please visit http://listserver.u2ug.org/
> -------
> u2-users mailing list
> [email protected]
> To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to