I've found that the bug has been happening since this change: http://invisible-island.net/ncurses/NEWS.html#t20151017
+ remove an early-return from _nc_do_color, which can interfere with
data needed by bkgd when ncurses is configured with extended colors
(patch by Denis Tikhomirov).
I've applied this patch (to undo it) and now mutt is working as before:
--------8<--------8<--------8<--------8<--------8<--------8<--------
diff -ru ncurses-6.0+20160319/ncurses/base/lib_color.c
ncurses-6.0+20160319.new/ncurses/base/lib_color.c
--- ncurses-6.0+20160319/ncurses/base/lib_color.c 2015-10-17
22:39:18.000000000 +0200
+++ ncurses-6.0+20160319.new/ncurses/base/lib_color.c 2016-06-07
18:21:35.366456528 +0200
@@ -858,6 +858,8 @@
}
} else {
reset_color_pair(NCURSES_SP_ARG);
+ if (old_pair < 0)
+ return;
}
#if NCURSES_EXT_FUNCS
--------8<--------8<--------8<--------8<--------8<--------8<--------
Other ncurses applications don't exhibit the same behaviour, so maybe something
is wrong with mutt (but it's not easy to follow due to the large amount of
calls to refresh() and endwin() present in its code).
--
Saludos de Javier <jcant...@escomposlinux.org>
signature.asc
Description: PGP signature
