Re: SOLVED (long) Re: colorization difference between 1.4.x and 1.5.x
On Thu, Jun 03, 2004 at 21:59:38 -0400, Michael W. Oliver wrote:
> [pasting the patch inline in case someone looks for it one day]
OK, I had a look at that patch, and I simplified it and made an additional
option out of it:
--- mutt.h.orig Fri Jun 4 13:35:59 2004
+++ mutt.h Fri Jun 4 13:49:26 2004
@@ -350,6 +350,7 @@
OPTBEEPNEW,
OPTBOUNCEDELIVERED,
OPTCHECKNEW,
+ OPTCOLORAFTEREOL,
OPTCOLLAPSEUNREAD,
OPTCONFIRMAPPEND,
OPTCONFIRMCREATE,
--- init.h.orig Fri Jun 4 13:35:56 2004
+++ init.h Fri Jun 4 13:45:43 2004
@@ -315,6 +315,12 @@
** \fIcheck_new\fP is \fIunset\fP, no check for new mail is performed
** while the mailbox is open.
*/
+ { "color_after_eol", DT_BOOL, R_NONE, OPTCOLORAFTEREOL, 1 },
+ /*
+ ** .pp
+ ** When \fIset\fP, Mutt will color a line after the last character extending
+ ** to the end of the window.
+ */
{ "collapse_unread", DT_BOOL, R_NONE, OPTCOLLAPSEUNREAD, 1 },
/*
** .pp
--- pager.c.orig Fri Jun 4 13:35:59 2004
+++ pager.c Fri Jun 4 13:48:51 2004
@@ -1392,7 +1392,7 @@
* ncurses does an implicit clrtoeol() when you do addch('\n') so we have
* to make sure to reset the color *after* that
*/
- if (flags & M_SHOWCOLOR)
+ if (option (OPTCOLORAFTEREOL) && (flags & M_SHOWCOLOR))
{
m = ((*lineInfo)[n].continuation) ? ((*lineInfo)[n].syntax)[0].first : n;
if ((*lineInfo)[m].type == MT_COLOR_HEADER)
With that patch (which I will submit soon for inclusion into the FreeBSD ports
tree) you can switch to the old behaviour by having "set color_after_eol=no"
in your .muttrc.
(Unfortunately that doesn't work for slang and I haven't figured out why)
Best regards
--
Udo Schweigert, Siemens AG | Voice : +49 89 636 42170
CT IC CERT, Siemens CERT | Fax : +49 89 636 41166
D-81730 Muenchen / Germany | email : udo.schweigert@xxxxxxxxxxx