Updated patch for version 232 is attached. (Not sure why but the xtermCloseFont line, which is identical to that in the preceeding code block, now causes a BadFont error. So I commented it out.
-- see shy jo
diff -ur old/xterm-232/fontutils.c xterm-232/fontutils.c
--- old/xterm-232/fontutils.c 2008-01-27 09:44:07.000000000 -0500
+++ xterm-232/fontutils.c 2008-02-20 21:15:59.000000000 -0500
@@ -914,6 +914,12 @@
xtermCopyFontInfo(&fnts[fBold], &fnts[fNorm]);
}
+ if (!screen->bold_mode && &fnts[fBold] != &fnts[fNorm]) {
+ TRACE(("...ignoring bold font, as per boldMode\n"));
+ //xtermCloseFont(xw, &fnts[fBold]);
+ xtermCopyFontInfo(&fnts[fBold], &fnts[fNorm]);
+ }
+
if_OPT_WIDE_CHARS(screen, {
if (fnts[fWide].fs != 0
&& fnts[fWBold].fs != 0
signature.asc
Description: Digital signature
