home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   TUXPOWER      Advocacy for the Linux operating system      1,237 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 896 of 1,237   
   Nick Boel to Maurice Kinal   
   Re: the solution would be to eliminate a   
   06 Dec 24 18:11:19   
   
   TZUTC: -0600   
   MSGID: 239.tuxpower@1:154/700 2bb8c996   
   REPLY: 1:153/7001 67527061   
   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 Thu, Dec 05 2024 21:32:49 -0600, you wrote ..   
      
   > > For example, in nano, try "set fill 69" in conjunction with "set   
   > > justifytrim" which removes the whitespace at the end of the lines.   
      
   > > For example, in nano, try "set fill 69" in conjunction with "set    
   > > justifytrim" which removes the whitespace at the end of the lines.   
      
   > Even though they look the same they aren't.  Can you tell which is which?   
      
   Sure. The first one you trimmed the blanks at the end, and the second one   
   they're there.    
      
   Was the second one with fold or just "set trimblanks" disabled?   
      
   Maybe the difference is that fold does (or doesn't) include the blanks in it's   
   count, whereas nano does (or doesn't) if you have them enabled? Which one do   
   you think is doing it incorrectly?   
      
   > BTW I can't find "set justifytrim" so instead I enabled "set trimblanks"   
   which looks to be the same end result.   
      
   Ah, seems the .nanorc in my home directory is quite a bit outdated. You are   
   correct, they've removed 'justifytrim' at some point. :)   
      
   > :read !nano --version   
   >  GNU nano, version 8.2   
   >  (C) 2024 the Free Software Foundation and various contributors   
   >  Compiled options: --enable-utf8   
      
   Mine is the exact same, except my .nanorc is probably about as old as my last   
   contact with the developers for the feature I was looking for. I should   
   probably take a look at some of the new options I never knew about. :)   
      
   Regards,   
   Nick   
      
   ... He who laughs last, thinks slowest.   
   --- SBBSecho 3.23-Linux   
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)   
   SEEN-BY: 103/705 104/119 105/81 106/201 120/616 124/5016 128/187 153/757   
   SEEN-BY: 153/7001 7715 154/10 30 50 700 203/0 218/700 220/20 90 221/0   
   SEEN-BY: 221/6 226/18 30 44 50 227/114 229/110 114 206 300 317 400   
   SEEN-BY: 229/426 428 664 700 705 240/1120 5832 266/512 280/464 5003   
   SEEN-BY: 282/1038 291/111 292/8125 301/1 310/31 320/219 322/757 341/66   
   SEEN-BY: 341/234 342/200 396/45 460/58 467/888 633/267 280 384 410   
   SEEN-BY: 633/412 418 509 2744 712/848 770/1 902/26 2320/105 3634/12   
   SEEN-BY: 5020/400 5075/35   
   PATH: 154/700 10 280/464 633/280 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca