MSGID: 1:154/10 6604a036   
   REPLY: 2:280/464.112 6603d8e1   
   PID: Smapinntpd/Linux 2.3.0   
   CHRS: UTF-8 4   
   TZUTC: -0500   
   TID: hpt/lnx 1.9 2024-02-05   
   On Wed, 27 Mar 2024 14:13:20 +0100, Wilfred Van Velzen -> Nicholas Boel wrote:   
      
     NB>> fconfig seems to work fine so far.   
      
    WvV> Nice!   
      
    WvV> If I may ask, which linux distribution/version are you using? And which   
    WvV> termimal?   
      
   Archlinux, 6.8.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 16 Mar 2024 17:15:35   
   +0000 x86_64 GNU/Linux   
      
   I use PuTTY from a Windows 11 machine to connect to the VM via SSH (same as   
   how I access Golded, if you remember that conversation). Full UTF-8. I did   
   have to enable the "Enable VT100 line drawing even in UTF-8 mode" option in   
   Putty in order for it to display correctly. Otherwise I haven't found any   
   issues compiling or using it, or even saving.. besides what I've mentioned   
   below.   
      
     NB>> First, is it just me or does the custom tearline only allow 24   
     NB>> characters?   
      
    WvV> Yes, that is the maximum, because that is the room for it that is   
    WvV> reserved for it in the config file. I don't know why this is. I searched   
    WvV> the ftsc docs, but it doesn't mention a length limit for tear lines.   
      
   Is there an easy way to up that to 75? (this allows for the "--- ", so you   
   could go less if you also need to allow for the " (XXX/XXX:XXX.XXX)" so it   
   won't wrap to the next line. So around 55, I suppose?)   
      
   I don't even have it fully setup yet and I'm already requesting features. :)   
      
     NB>> Second, Am I not able to make JAM netmail areas? Or am I doing   
     NB>> something wrong?   
      
    WvV> They are not supported.   
      
   Ok. That's what I gathered when I couldn't name the JAM base.   
      
     NB>> Third, and last for now.. Is the backbone.na import format only for   
     NB>> file areas? I've made one with message areas with 168 lines of this   
     NB>> format:   
      
     NB>> ECHOTAG        
      
     NB>> And I get "0 descriptions imported".   
      
    WvV> I have to look into this. But it isn't for file areas, because fmail   
    WvV> doesn't do anything with file areas.   
      
   Ok. Let me know if you find something, or if I'm doing something wrong.   
   Permissions don't seem to be the issue. I'm running everything as the same   
   user/group (the only user/group on that VM, actually) that I compiled it with.   
      
    WvV> But there is always the description on the bottom line when you are on   
    WvV> an option. Or if you are desperate the doc file! ;-)   
      
   I've had to read most of them multiple times, and then sometimes look at the   
   doc file for a more detailed description. Even after that I'm still confused   
   on a few options that I've never used. Guessing leaving them default probably   
   won't hurt anything. :)   
      
   Regards,   
   Nick   
      
   ... "Take my advice, I don't use it anyway."   
   --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb   
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)   
   SEEN-BY: 1/19 15/0 16/0 19/37 90/1 105/81 106/201 120/302 123/10 130   
   SEEN-BY: 128/260 129/305 135/225 142/104 153/757 7715 154/10 30 40   
   SEEN-BY: 154/50 700 203/0 218/700 840 220/90 221/1 6 360 226/18 30   
   SEEN-BY: 227/114 229/110 112 113 206 307 310 317 426 428 470 550 664   
   SEEN-BY: 229/700 240/5832 266/512 280/464 5003 5555 282/1038 291/111   
   SEEN-BY: 292/854 301/1 320/119 219 319 2119 322/757 326/101 335/364   
   SEEN-BY: 341/66 234 342/200 396/45 423/81 460/58 633/280 712/848 2320/105   
   SEEN-BY: 3634/12 5058/104   
   PATH: 154/10 221/6 1 320/219 229/426