Well, I upgraded 222-1 today, and this bug is back for me. I tried applying the xterm-boldmode-2.patch, and with some updates to work with changed variables in the new version, it works! I've attached an updated version of the patch.
Please consider applying this.. -- see shy jo
diff -ur old/xterm-222/fontutils.c xterm-222/fontutils.c --- old/xterm-222/fontutils.c 2006-09-10 15:55:28.000000000 -0400 +++ xterm-222/fontutils.c 2006-11-09 19:49:50.000000000 -0500 @@ -886,6 +886,12 @@ fnts[fBold] = fnts[fNorm]; } + if (!screen->bold_mode && fnts[fBold] != fnts[fNorm]) { + TRACE(("...ignoring bold font, as per boldMode\n")); + XFreeFont(screen->display, fnts[fBold]); + fnts[fBold] = fnts[fNorm]; + } + if_OPT_WIDE_CHARS(screen, { if (fnts[fWide] != 0 && fnts[fWBold] != 0
signature.asc
Description: Digital signature