TZUTC: -0600
MSGID: 241.tuxpower@1:154/700 2bb8e710
REPLY: 1:153/7001 67539aa7
PID: Synchronet 3.20a-Linux master/6e166f09d Dec 02 202 GCC 14.2.1
TID: SBBSecho 3.23-Linux master/6e166f09d Dec 02 2024 13:11 GCC 14.2.1
BBSID: PHARCYDE
CHRS: ASCII 1
NOTE: slrn/pre1.0.4-9 (Linux)
Hello Maurice,

On Fri, Dec 06 2024 18:45:27 -0600, you wrote ..

> It was 'fold -s -w 69'.  The first is nano with "set trimblanks" and 
> "set fill 69".

I knew what the first one was, but there was two possibilities for the second.

> Neither, they are true to what they're called up to do.  Offhand I 
> suspect that fold is more DOSsie and it is usually one character shy 
> of how others define the length of a string.  For example FTN 
> standards list the subject field at 72 characters when it is really 
> 71.  The 72nd character is \0, which is ye' olde string delimiter and 
> in the case of MSGs it is a field delimiter.  Offhand I'd go with 
> fold's specifiers and have .nanorc "set fill 68" which is one less 
> than fold but produces the same end result as 'fold -s -w 69'.

Ok, I suppose if nothing is wrong, then we carry on like it never happened!

Ikiwa haijavunjwa, usiirekebishe! :)

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.23-Linux
 * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
SEEN-BY: 10/0 1 103/705 104/119 105/81 106/201 120/616 124/5016 128/187
SEEN-BY: 153/757 7001 7715 154/10 30 50 700 203/0 214/22 218/0 1 601
SEEN-BY: 218/700 840 850 860 870 880 930 940 220/20 90 221/0 6 226/18
SEEN-BY: 226/30 44 50 227/114 229/110 114 206 300 317 400 426 428
SEEN-BY: 229/664 700 705 240/1120 5832 266/512 280/464 5003 282/1038
SEEN-BY: 291/111 292/8125 301/1 310/31 320/219 322/757 341/66 234
SEEN-BY: 342/200 396/45 460/58 467/888 633/280 712/848 770/1 902/26
SEEN-BY: 2320/105 3634/12 5020/400 5075/35
PATH: 154/700 10 280/464 103/705 218/700 229/426