From 8016470c2b6f49aed2587546b9c2585a58696ec9 Mon Sep 17 00:00:00 2001
From: root <root>
Date: Tue, 31 Jan 2006 21:04:14 +0000
Subject: [PATCH] *** empty log message ***

---
 doc/rxvt.7.man.in | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/doc/rxvt.7.man.in b/doc/rxvt.7.man.in
index dee7cb87..a59659f1 100644
--- a/doc/rxvt.7.man.in
+++ b/doc/rxvt.7.man.in
@@ -220,10 +220,10 @@ display, create the listening socket and then fork.
 \fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR
 .IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
 .PP
-rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can
-check and see if that is set. Note that several programs, \s-1JED\s0, 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 \*(L"\s-1COLORTERM\s0\*(R",
+so you can check and see if that is set. Note that several programs, \s-1JED\s0,
+slrn, Midnight Commander automatically check this variable to decide
+whether or not to use color.
 .PP
 \fIHow do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?\fR
 .IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?"
@@ -277,7 +277,7 @@ already in use in this mode.
 \&  188985    9048   66616   18222    1788 urxvt --disable-everything
 .Ve
 .PP
-When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft
+When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which \fIis\fR 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.
 .PP
@@ -573,8 +573,7 @@ including the murky brown that passes for low-intensity yellow:
 \&   URxvt.color15:  #FFFFFF
 .Ve
 .PP
-And here is a more complete set of non-standard colors described (not by
-me) as \*(L"pretty girly\*(R".
+And here is a more complete set of non-standard colors.
 .PP
 .Vb 18
 \&   URxvt.cursorColor:  #dc74d1
@@ -597,6 +596,8 @@ me) as \*(L"pretty girly\*(R".
 \&   URxvt.color15:      #e1dddd
 .Ve
 .PP
+(They were described (not by me) as \*(L"pretty girly\*(R").
+.PP
 \fIWhy do some characters look so much different than others?\fR
 .IX Subsection "Why do some characters look so much different than others?"
 .PP
@@ -914,7 +915,7 @@ resource to set it:
 .Ve
 .PP
 If you don't plan to use \fBrxvt\fR (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 use \f(CW\*(C`TERM=rxvt\*(C'\fR.
 .PP
 \fI\f(CI\*(C`tic\*(C'\fI outputs some error when compiling the terminfo entry.\fR
 .IX Subsection "tic outputs some error when compiling the terminfo entry."
@@ -1266,8 +1267,8 @@ old libW11 emulation.
 At the time of this writing, cygwin didn't seem to support any multi-byte
 encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited
 to 8\-bit encodings.
-.SH "RXVT TECHNICAL REFERENCE"
-.IX Header "RXVT TECHNICAL REFERENCE"
+.SH "RXVT-UNICODE TECHNICAL REFERENCE"
+.IX Header "RXVT-UNICODE TECHNICAL REFERENCE"
 .SH "DESCRIPTION"
 .IX Header "DESCRIPTION"
 The rest of this document describes various technical aspects of
@@ -2128,7 +2129,7 @@ l l .
 4	Shift
 8	Meta
 16	Control
-32	Double Click (Rxvt extension)
+32	Double Click (rxvt extension)
 .TE
 
 Col = \fB\f(CB\*(C`<x> \- SPACE\*(C'\fB\fR
-- 
2.34.1