REPLY: 1:154/10 65ce72cc   
   MSGID: 1:104/117 65ceb5ce   
   CHRS: CP866 2   
   TZUTC: -0700   
   TID: hpt/lnx 1.9 2022-07-03   
   �ਢ¥â, Nicholas!   
      
   15 Feb 24 14:23, âë ¯¨á «( ) ¬­¥:   
      
    VA>> My last commit rollback some change I made previously because it   
    VA>> was found to be buggy in some cases. So it could be some other   
    VA>> change actually.   
      
    VA>> If you familiar with git, would be nice if you hunt down which   
    VA>> commit makes things worse in your setup. You may use git bisect   
    VA>> for that.   
      
    VA>> https://git-scm.com/docs/git-bisect   
      
    NB> I'm not very familiar with it, but I was able to figure it out with   
    NB> the link you provided. Thank you!   
      
    NB> $ git bisect start   
    NB> $ git bisect bad   
    NB> $ git bisect good f7be1e97e251ee2be20f63abdcf2a18f93c880b9   
      
    NB> I chose this commit because it was just prior to the 'revert "zero   
    NB> conversion" workaround', where things were definitely looking more   
    NB> towards 'normal'.   
      
   For bisect you better chose wider range. Like a year or so. With bisect you   
   only need ln(N) tries to find broken commit. It could be broken earlier   
   actually.   
      
    NB> $ make BUILD=minimal (this compiled version 20231112 for some reason I   
    NB> don't yet understand)   
      
   Minimal build disables some stuff like spellchecker. It shall not affect   
   version. That's strange. Also cleaning previous build results may help.   
      
    NB> It was back to normal with this compile.   
      
    NB> $ git bisect good   
    NB> $ make BUILD=minimal (this compiled version 20240206)   
      
    NB> It was still good.   
      
    NB> $ git bisect good   
      
    NB> https://pharcyde.org/git-bisect-result.png   
      
    NB> It seems as though I'm back to the way it was in version GoldED+/LNX   
    NB> 1.1.5-b20240206. Here is an example:   
      
    NB> https://pharcyde.org/golded-20240206.png   
      
    NB> $ git bisect reset (to go back to the master branch 20240209)   
    NB> $ make BUILD=minimal   
      
    NB> https://pharcyde.org/golded-20240209.png   
      
    NB> Same configuration in golded.conf:   
      
    NB> [ start paste ]   
      
    NB> # Character translation path   
    NB> xlatpath /home/axisd/src/golded-plus/cfgs/charset   
    NB> include /home/axisd/src/golded-plus/cfgs/config/charsets.cfg   
      
    NB> # UTF-8 Configuration   
    NB> #   
    NB> xlatcharset     utf-8           utf-8           utf_utf.chs   
      
    NB> xlatimport      cp437   
    NB> xlatexport      utf-8   
    NB> xlatlocalset    utf-8   
      
    NB> [ end paste ]   
      
   You have xlatimport cp437.   
      
   Does that message with broken pseudo-graphics have CHRS kludge? If not - is it   
   really in cp437 encoding? Pseudo-graphics characters located in second half of   
   charset table and it's different for different charsets.   
      
   Best regards,   
   Vitaliy Aksyonov.   
      
   --- GoldED+/LNX 1.1.5-b20231030   
    * Origin: Aurora, Colorado (1:104/117)   
   SEEN-BY: 15/0 18/200 50/109 90/1 103/705 104/117 105/81 106/201 124/5016   
   SEEN-BY: 128/260 129/305 135/225 153/757 7715 154/10 30 203/0 218/700   
   SEEN-BY: 221/0 226/30 227/114 229/110 112 113 206 307 317 400 426   
   SEEN-BY: 229/428 470 664 700 240/1120 5832 266/512 280/464 5003 5555   
   SEEN-BY: 282/1038 291/111 292/854 8125 301/1 310/31 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/16 58 256 1124 5858   
   SEEN-BY: 463/68 467/888 633/267 280 410 412 418 420 509 2744 712/848   
   SEEN-BY: 770/1 3634/12 5000/111 5001/100 5005/49 5015/46 5020/400   
   SEEN-BY: 5020/828 846 1042 4441 5030/49 5054/8 30 5061/133 5075/128   
   SEEN-BY: 5083/444 5090/958   
   PATH: 104/117 5020/1042 460/58 280/464 633/280 229/426