Subj : Re: Latest sources.. To : Nicholas Boel From : Vitaliy Aksyonov Date : Thu Feb 22 2024 10:11 pm Hi, Nicholas! 20 Feb 24 18:20, âë ¯¨á «( ) ¬­¥: VA>> Code 20 is a space. So wrapping caused by that. NB> I doubt it. It was just a guess. :) I'm trying to dig in all possible directions. VA>> Also check if you have DispMargin parameter in your config. If VA>> you do - comment it out or remove. Then GoldEd will use all VA>> window width. NB> Most likely whatever the default settings is, since I don't use it in NB> my config. Default is to use whole window. Then it's weird, that line is broken.  NB>>> I used checkout to get the specific commit you asked me to  NB>>> grab (372220588c6f17cd3f709dcb721a9144169d988c), and it is  NB>>> indeed exactly how the latest version is. So you were right. VA>> You said that before you started to experiment - all worked fine. VA>> Have you used same compiler? Now I suspect that issue caused by VA>> something in your setup. Because it's quite opposite from others VA>> have. NB> I said before that it has looked fine for quite some time. I didn't go NB> back to the version you asked me too until I got the answer to use NB> 'checkout' instead of 'bisect'. Now that I was able to go back that NB> far, I was able to give you a better answer. Great.  NB>>> It did not. Whatever first change you made actually kind of  NB>>> helped me, I suppose. Hopefully this helps narrow things down  NB>>> better and we can figure out what's going on. VA>> That's why would be interesting to use bisect from VA>> 372220588c6f17cd3f709dcb721a9144169d988c to master and find VA>> specific commit which made it bad in your specific case. NB> I did this, sort of. Instead of bisect, I used checkout and tried NB> every version after 372220588* until I got to the one that changed the NB> display. NB> 8e9f3518ac9b3b32676e7b7563e92cc44e7b5ba7 is the commit that changes NB> things for the better in my case. NB> It stayed that way until you reverted the commit in the latest NB> version. That's something. Thanks for doing that. NB> My only thoughts is that I am using PuTTY to connect with utf-8 NB> settings to a utf-8 linux terminal. I include NB> golded-plus/cfgs/config/charsets.cfg so I basically translate to and NB> from everything currently possible. Have you tried to run it in local terminal emulator? Do you have any GUI on that computer? Putty may be pain in the ass to configure correctly. NB> Maybe Wilfred had issues with this commit because he's not actually NB> using any xlat configuration? He had told me he's using some kind of NB> half and half utf-8/cp437 terminal and not using any xlat* settings in NB> his configuration. If he can view that stat screen I posted as well as NB> view Michiel's tearline and origin line over in the UTF-8 echo during NB> the same golded session and no configuration changes, I would be NB> surprised. NB> This is with 8e9f3518*: NB> https://pharcyde.org/golded-stats.png NB> https://pharcyde.org/golded-utf8.png NB> As you can see the only issue I seem to have with this version (and NB> everything up till the 20240206 release) is a few line wraps on the NB> stat screen that shouldn't be happening - and I don't have a very NB> extensive golded.conf where I could see anything in there that would NB> be causing that, except the translation tables themselves. Would be cool if you may share your config and message base with message containing pseudo-graphics for me to play with. If I reproduce it internally - then I may find the cause very quickly! By config I mean not only golded.cfg, but all included files, including charset tables. Best regards, Vitaliy Aksyonov. --- GoldED+/LNX 1.1.5-b20231030 * Origin: Aurora, Colorado (1:104/117) .