TID: Mystic BBS 1.12 A48   
   REPLY: 2:280/2060 674419b2   
   MSGID: 4:930/1 674471c8   
   PID: GED+W32 1.1.5-b20180707   
   CHRS: CP437 2   
   TZUTC: -0500   
      
      Hello Dennis!   
      
   25 Nov 24 07:27, you wrote to me:   
      
      
    DS> Hello David!   
      
    DS> 24 Nov 24 17:42, you wrote to Angel Ripoll:   
      
    AR>>>     LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx   
    AR>>> -Cpath_to_cfg   
      
    DS> I believe that this line has no use as source and target encoding is   
    DS> the same for my installation (I use Fidian for GoldEd through ttyd and   
    DS> tmux), I have a export TERM=screen.xterm-256color   
      
   yes, that might be, my TERM is TERM=linux   
      
    DS> where you can start that like (in a bin/bash script like)   
    DS> TERM=screen.xterm-256color /usr/bin/golded -T600   
      
   I'm definitely going to try that as a bash startup script.   
      
    DS> without that I have similar like you. Ie, if you run it directly in a   
    DS> shell you possible have the incorrect encoding.   
      
    DS> The 'lining' does have have really (imho) something to do withe the   
    DS> encoding for the characters in messages ..   
      
   many thanks, I was thinking it was eitehr encoding or terminal type but it's   
   been a long time coming back to Linux.   
      
    DS> Dennis   
      
      
    DS> ... Why document it? I'll be here forever.   
    DS> --- GoldED+/LNX 1.1.5-b20240309   
    DS>  * Origin: Deputy Nodelist Police (2:280/2060)   
      
   David   
      
   SEEN-BY: 902/26 930/1 341/66 900/106 902/19 280/464 229/426 900/102 4/0 90/0   
   SEEN-BY: 900/0 902/0   
   PATH: 930/1 902/26