Subj : RE: Reliable way to get term size
To   : NuSkooler
From : echicken
Date : Tue Apr 06 2021 02:47 am

  Re: RE: Reliable way to get term size
  By: NuSkooler to echicken on Mon Apr 05 2021 16:29:37

 Nu> At one point I was using 255,255 for ENiG then switched it to 999,999 and
 Nu> I can't remember at all why. I _think_ I may have run into it with a full
 Nu> screen Linux telnet session where 255 wasn't big enough? 

I could've sworn I'd seen it specified somewhere that 255 was the max for those parameters, but now I'm unable to find that. 999 is better, if still a guess, and if it doesn't break anything.

I'm now imagining the "best" way to find width and height without relying on some hard-coded value. Send the cursor to 255;255, get a position report. If the row is reported as 255, tell the cursor to go down another 255 rows, and repeat until the reported row stops changing. Same goes for column.

All of this because "cursor home" is a thing but "cursor end" is not. :|
  
---  
echicken   
electronic chicken bbs - bbs.electronicchicken.com
 * Origin: electronic chicken bbs - bbs.electronicchicken.com (21:1/164)

.