LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Nick Laflamme <[log in to unmask]>
Mon, 27 Aug 90 11:23:20 EST
text/plain (37 lines)
On Fri, 24 Aug 90 21:50:21 O Eric Thomas said:
>You have two types of messages on the console:
>
>1. The ones which are output via a straight SAY. These are split by REXX,
>   not my code.
 
( Second case deleted)
 
>Sorry, Eric
 
Stunned by Eric's blame for REXX, which I tend to consider perfect :-),
I started playing with this.  For better or worse, it looks like it's
CP, not REXX, which is to blame for this.  When a user does a DISC, the
TERM LINESIZE goes to 000, which is interesting but meaningless.  Even
when I had been logged on at a 132 column terminal, this seemed to act
as an 80 column terminal, which is consistent with what we'd seen so
far.
 
However, I then found that if I did a TERM LINESIZE 132 after the CP
DISC, Q TERM still showed LINESIZE as 000, but the output of SAY no
longer wrapped at 80 columns!  Something stuck internally in CP to let
output use more than 80 columns.  This looks vaguely like black magic,
or at least an internal setting which the user can't directly set or
query.
 
Eric, any chance of a user setting which would ask LISTSERV to do a CP
TERM LINESIZE nnn (nnn under user control) upon initiation?  I realize
lots of events later (logging on and disconnecting again, for one) could
negate this, but it'd be a partial improvement.
 
Thanks,
Nick
 
ps - I can't very well imbed the console traces into a mail file which
is restricted to 80 columns, but my console traces are available upon
request. :-)

ATOM RSS1 RSS2