Re: [Mlterm-dev-en] A few glitches.

[Andi C. S. <ski...@ya...>]

Hello,

I've tried compiling the latest (development) version and it fails somewhere. I got the following:

../xwindow/xlib/x_imagelib.c:86:14: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
make[1]: *** [x_imagelib.o] Error 1
make[1]: Leaving directory `/home/acs/mlterm/xwindow'
make: *** [all] Error 2

> Sorry, --disable-use-tools didn't work correctly by the bug of configure script.
> I fixed it, and pushed the fixes to hg head.

Thanks, it works now. Would it also be possible to compile out those things which presuppose that mlterm can load background images (e.g. options like brightness, contrast, gamma, image path and whatever else may do so) when that feature is disabled, as is the case with SSH?


> How about "conf_men_path_1" "conf_men_path_2" and "conf_men_path_3" options ?

Yes, I know about them, but the other way would be more flexible. Treating the mouse buttons as keys are would allow any button/modifier combination to be (re)bound to anything the keybindings currently support (or to be easily disabled).

My idea is to add an option to run any command string, which would implement the current behaviour by default. This would also prevent having disparate options for control plus all buttons, for button 3 alone and for the menu path.

> The glyph of U+2592 of GNU Unifont is full width, while mlterm
> (unless -ac 2 option is specified) and finch deal it as half width.
> It is impossible to fix this problem completely, but I pushed a
> few fixes which improve the situation to hg head.

> (Indeed urxvt seems to show it correctly, but I think that urxvt
> redraws characters more than necessary in using GNU Unifont and
> that it results in showing correctly by chance.)

Impacting performance would be indeed bad, but it displays correctly most of the time now (it only seems to be the case for core fonts, though). The only way to get rid of it would probably be to modify the font (is there any reason why block characters should be 16 pixels wide, anyway?).

And then there's also the issue of artefacts. Opening http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt with e.g. lynx and scrolling past the Ethiopian text would leave some of those behind.

Regards,
Andi Șerbănescu