Subj : Latest sources.. To : Vitaliy Aksyonov From : Nicholas Boel Date : Thu Feb 15 2024 13:16:42 On Thu, 15 Feb 2024 05:09:52 -0700, Vitaliy Aksyonov -> Nicholas Boel wrote: VA> Those warnings are "normal". In terms like they better be fixed, by they VA> are expected especially in new compiler. They mostly safe and you may VA> ignore them. Ok great! It just seemed like there were more warnings than normal, but that may just be because of a newer gcc version - I do believe it was upgraded recently as well. VA> Do you use following parameters when build it: VA> USE_NCURSES VA> WIDE_NCURSES VA> BUGGY_NCURSES USE_NCURSES is default on Linux, so I don't specify that. I have used WIDE_NCURSES in the past but not this time (doesn't really make any difference for me, it seems), and I have never used BUGGY_NCURSES. This time around, I just ran 'make' with no parameters. Sometimes I use BUILD=minimal, but I don't think that makes much difference in regards to how things look. VA> And which ncurses library version do you have? ncurses-6.4_20230520-1 is the package, so everything that comes with that. VA> That is interesting. It shall work totally fine without screen multiplexor. I did get it to show the message header, loading screen and arealist correctly now by checking "Enable VT100 line drawing even in UTF-8 mode" in my PuTTY configuration. So with that I can now drop the multiplexors. However, it doesn't change what the actual messages look like. VA> Would be interesting to understand how screen or tmux makes a difference. It wasn't much, it just displayed the above mentioned things correctly without any additional PuTTY settings. VA> BTW, what do you have for $TERM env variable? TERM="xterm" VA> My last commit rollback some change I made previously because it was found VA> to be buggy in some cases. So it could be some other change actually. VA> If you familiar with git, would be nice if you hunt down which commit makes VA> things worse in your setup. You may use git bisect for that. VA> https://git-scm.com/docs/git-bisect I will take a look at that and try the last few commits. I will let you know if I see any differences.  NB>> No. golded.log has been 0 bytes for quite some time now. Is that  NB>> normal? VA> It is very good actually. Golded writes errors in that file and if it empty VA> - it's a good sign. Good. I must have cleared it back on December 7 because of old errors, since that is the current date of the file. Nothing since then, though. VA> Moved to next line is OK. It's just for messages, which has lines longer VA> than your terminal width. Is there a way to change the line length in Golded? If it is set for something like 78 by default, maybe changing it to 79 would help as it could be one extra character that's causing it to wrap to the next line. Although, I don't know how replies and quotes coming from here would look on others' systems then.. I'd rather break things on my end, not others. :) VA> To use cp437 you need to change Putty config for sure. And I'd recommend VA> you to use one byte locale for golded if you don't need many different VA> encodings. That will solve many issues for you right away. Honestly, I have no interest in using CP437 in a terminal. I don't mind some irregularities, but this time there were just more than usual. I don't like things easy. For some reason I enjoy making things extremely difficult for myself. VA> Some people do experience issues like you. And would be really great to VA> find and fix root cause. I agree! Then again, if/when you get iconv working properly I think many of these issues will probably disappear since iconv > old crusty translation tables. VA> Could you also try to remove file goldxlat.gel? Golded will generate it on VA> start. I did, and it didn't change anything. I'll use 'git bisect' and see if I can figure out if a recent commit changes it back to the way it was. Regards, Nick .... "Take my advice, I don't use it anyway." --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10) .