From: Andi C. S. <ski...@ya...> - 2012-12-16 15:14:00
|
Hello, > Oh, sorry. I understand. > But do they have something harmful ? > At least, I made a patch to add "--disable-use-tools" configure option > which disable them. > (I haven't merged it to hg head yet) They're not harmful, but they seem a little superfluous in case you don't want anything else built in. However, mlimgloader still builds, even though I didn't specify it (it seems to append itself to whatever parameter I give to --with-tools, including an empty string). By the way, could the mouse actions (menu and configurator) not be made hard-coded, but configurable as the keys are (possibly renaming the key file to something like bindings to reflect the change)? > I tried finch, but I couldn't reproduce this problem. > (U+2592 shows correctly.) > Will you start mlterm with --logseq option, use finch until the problem happens > and send me a ~/.mlterm/*.log file ? It seems to be caused by mlterm displaying those characters in a 16×8 cell, although they're actually 16×16 in size, thus sometimes displaying over the next character and sometimes pushing it to the right. Running mlterm with --logseq itself seems to trigger the former behaviour over the latter. See the two window dumps for comparison (display them with "xz -cd FILENAME | xwud"). Of course, it only happens with GNU Unifont, which has characters of both widths. I have set termtype to linux-m, since it uses the font's box drawing characters instead of those drawn by mlterm itself. Regards, Andi Șerbănescu |