REPLY: 4:930/1 6748f2ce   
   MSGID: 2:280/2060 674962b0   
   CHRS: CP437 2   
   TZUTC: 0100   
      
   Hello David!   
      
   28 Nov 24 17:44, you wrote to Wilfred van Velzen:   
      
    DG> sbbs@bbs:~$ LANG=es_ES.ISO8859-1 luit -encoding 'ISO-8859-2' gedlnx   
    DG> -C/home/sbbs/ Command 'luit' not found, did you mean: command 'quit'   
    DG> from snap quit (1.0+git) command 'lfit' from deb fitsh   
      
   if luit cannot be found you have to install it   
   as far as I know luit is part of x11-utils   
      
   luit is not a standalone package in most modern Debian or Ubuntu   
   distributions. It is part of the X.Org project and typically included in the   
   x11-utils package.   
      
   apt install x11-utils   
      
   Hoever in my tests and in my terminal this was not a solution for your issue   
   to fix it I had to add (I use fidian with goldED, which is ran under tmux and   
   ttyd)   
   (as per example):   
      
   Environment=LC_CTYPE=en_US.UTF-8   
   Environment=LANG=en_US.UTF-8   
   Environment=LC_ALL=en_US.UTF-8   
      
   Without it a lot of things went wrong on display with my Debian .. with this   
   .. its working ok   
   btw . .sometimes you have to reboot and/or logout/login to make it work   
   correctly.   
      
   But in general above would even not solve the issue   
      
    DG>   X terminal emulator   
      
    DG> Whatever the error I'm making... I cannot seem to find it   
      
   It's difficult as a number of settings can cause golded not to function   
   properly with its display   
      
   if in your normal shell you still get the qqqqqq your standard encoding within   
   your shell is not ok   
   But .. you have to take care on the config   
      
   for instance I start my golded from a bin/bash script, but when I do not use   
      
      
       export TERM=screen.xterm-256color   
      
   this line .. I do not get the 'lines' but I get the qqqqqqq ..   
      
   so please first try to get it running correctly without Luit . .as that should   
   be possible   
   eliminate as much encoding/decoding stuff as that could cause issues ..   
      
   Try to make a bin/bash to make encoding sometimes easier rather than being   
   busy with .bashrc etc.   
   but I do not know how well experienced you are in linux. (On certain levels I   
   lack serious knowledge, so I try a lot of things and I also sometimes use   
   chatgpt or co-pilot to check what direction to go ..   
      
   not always direct an answer but it gives you guidelines/hints/tips you could   
   try.   
      
   Dennis   
      
      
   ... I don't troubleshoot; I blame the vendor.   
   --- GoldED+/LNX 1.1.5-b20240309   
    * Origin:  ---- BOFH: Problem solved, user deleted. (2:280/2060)   
   SEEN-BY: 18/200 103/705 105/81 106/201 124/5016 128/187 129/305 153/757   
   SEEN-BY: 153/7715 154/10 30 203/0 218/700 221/0 1 226/30 227/114 229/110   
   SEEN-BY: 229/114 206 300 317 400 426 428 470 664 700 240/1120 5832   
   SEEN-BY: 266/512 280/464 1208 2000 2040 2050 2060 5003 5006 5555 282/1038   
   SEEN-BY: 291/111 292/854 8125 301/1 310/31 320/219 322/757 341/66   
   SEEN-BY: 341/234 342/200 396/45 423/120 460/16 58 256 1124 5858 467/888   
   SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 1042 8912 5054/30   
   PATH: 280/2060 5003 464 460/58 229/426