TID: FMail-lnx64 2.3.0.1-B20240319   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: CP850 2   
   PID: GED+LNX 1.1.5-b20240306   
   MSGID: 2:280/464 66052e8c   
   REPLY: 1:154/10 6604a036   
   Hi Nicholas,   
      
   On 2024-03-27 17:39:50, you wrote to me:   
      
    WvV>> If I may ask, which linux distribution/version are you using? And   
    WvV>> which termimal?   
      
    NB> Archlinux, 6.8.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 16 Mar 2024 17:15:35   
    NB> +0000 x86_64 GNU/Linux   
      
   Nice to know! I can't test them all! ;-)   
      
    NB> I use PuTTY from a Windows 11 machine to connect to the VM via SSH   
    NB> (same as how I access Golded, if you remember that conversation). Full   
    NB> UTF-8. I did have to enable the "Enable VT100 line drawing even in   
    NB> UTF-8 mode" option in Putty in order for it to display correctly.   
    NB> Otherwise I haven't found any issues compiling or using it, or even   
    NB> saving.. besides what I've mentioned below.   
      
   And the discussion to get my terminals right for golded, continued until   
   yesterday! ;-)   
   But I now seem to have it as good as it can get.   
      
    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   
    WvV>> searched the ftsc docs, but it doesn't mention a length limit for   
    WvV>> tear lines.   
      
    NB> Is there an easy way to up that to 75? (this allows for the "--- ",   
      
   Not so easy. There is reserve space in the binary config file, but not   
   directly after the current field.   
   So you need code around it for compatibility to use the old or new field. But   
   I don't find this a very important new feature.   
   The tearline is mostly used for version info of the generating software, and   
   fmail already handles that very well.   
      
    NB> so you could go less if you also need to allow for the "   
    NB> (XXX/XXX:XXX.XXX)" so it won't wrap to the next line. So around 55, I   
    NB> suppose?)   
      
   I noticed you already noticed your mistake here. ;-)   
      
    NB> I don't even have it fully setup yet and I'm already requesting   
    NB> features. :)   
      
   Well it is good to have some fresh eyes on it, to suggest improvements for   
   fmail. So keep them comming! ;-)   
      
     NB>>> Third, and last for now.. Is the backbone.na import format only   
     NB>>> for file areas? I've made one with message areas with 168 lines of   
     NB>>> this 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.   
      
    NB> Ok. Let me know if you find something, or if I'm doing something wrong.   
      
   It crossed my mind you could test importing files with different line endings   
   (linux vs dos).   
      
    NB> Permissions don't seem to be the issue. I'm running everything as the   
    NB> same user/group (the only user/group on that VM, actually) that I   
    NB> compiled it with.   
      
   Ok, good you thought of this, because that is often an issue on linux systems.   
      
    WvV>> But there is always the description on the bottom line when you are   
    WvV>> on an option. Or if you are desperate the doc file! ;-)   
      
    NB> I've had to read most of them multiple times, and then sometimes look at   
   the   
    NB> doc file for a more detailed description. Even after that I'm still   
   confused   
    NB> on a few options that I've never used. Guessing leaving them default   
   probably   
    NB> won't hurt anything. :)   
      
   Probably... ;)   
      
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.3.0.1-B20240319   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 15/0 90/1 103/705 105/81 106/201 124/5016 128/260 129/305   
   SEEN-BY: 135/225 153/757 7715 154/10 30 203/0 218/700 221/0 226/30   
   SEEN-BY: 227/114 229/110 112 113 206 307 317 426 428 470 550 664 700   
   SEEN-BY: 240/1120 5832 266/512 280/464 5003 5555 282/1038 291/111   
   SEEN-BY: 292/854 8125 301/1 310/31 320/219 322/757 341/66 234 342/200   
   SEEN-BY: 396/45 423/120 460/58 256 1124 467/888 633/280 712/848 770/1   
   SEEN-BY: 5020/400 5054/30   
   PATH: 280/464 460/58 229/426