From 9d192f30e896c57fba22b505d755ee6072307439 Mon Sep 17 00:00:00 2001
From: root
rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can -check and see if that is set. Note that several programs, JED, slrn, -Midnight Commander automatically check this variable to decide whether or -not to use color.
+The original rxvt and rxvt-unicode always export the variable ``COLORTERM'', +so you can check and see if that is set. Note that several programs, JED, +slrn, Midnight Commander automatically check this variable to decide +whether or not to use color.
When you --enable-everything
(which _is_ unfair, as this involves xft
+
When you --enable-everything
(which is unfair, as this involves xft
and full locale/XIM support which are quite bloaty inside libX11 and my
libc), the two diverge, but not unreasnobaly so.
@@ -483,8 +483,7 @@ including the murky brown that passes for low-intensity yellow: URxvt.color13: #FF00FF URxvt.color14: #00FFFF URxvt.color15: #FFFFFF-
And here is a more complete set of non-standard colors described (not by -me) as ``pretty girly''.
+And here is a more complete set of non-standard colors.
URxvt.cursorColor: #dc74d1 URxvt.pointerColor: #dc74d1 @@ -504,6 +503,7 @@ me) as ``pretty girly''. URxvt.color14: #73f7ff URxvt.color7: #e1dddd URxvt.color15: #e1dddd+
(They were described (not by me) as ``pretty girly'').
URxvt.termName: rxvt
If you don't plan to use rxvt (quite common...) you could also replace -the rxvt terminfo file with the rxvt-unicode one.
+the rxvt terminfo file with the rxvt-unicode one and useTERM=rxvt
.
tic
outputs some error when compiling the terminfo entry.
Col = <x> - SPACE
>
Row = <y> - SPACE
>