From: Andi C. S. <ski...@ya...> - 2012-06-15 11:46:42
|
Hello, I've uncovered 2 minor glitches (still in version 3.1.2, although they have been around for some time): 1. Although I compiled without FreeBiDi support, I still get errors in .mlterm/msg.log such as: Jun 15 14:16:56[7142] *** ERROR HAPPEND *** BiDi: Could not load. 2. If some process outputs large quantities of text (e.g. compiling some software package) in a mlterm window, then hiding that window behind another one (this one can be anything, e.g. firefox) has the result of making parts of the output text that were initially below the second window appear ‘erased’ after scrolling upwards to the visible part of the terminal window. This happens regardless of any settings. It seems as though mlterm forgot to draw the text in question, but it's rendered visible by selecting it. You can try to reproduce it by hiding about half of a mlterm window beneath a browser window, then running ./configure && make on the mlterm source. You should see it ocasionally skipping about 1–3 rows of text. You may have to interrupt the process to investigate those suspicious lines (i.e. by selecting them), but some may appear towards the end. Regards, Andi Șerbănescu |