repo: rxvt-unicode-sixel
action: commit
revision: 
path_from: 
revision_from: 1593ba8c04d68d377be99ceae0f308c168d34d7a:
path_to: 
revision_to: 

commit 1593ba8c04d68d377be99ceae0f308c168d34d7a
Author: Marc Lehmann 
Date:   Tue Jan 31 21:00:26 2006 +0000

    *** empty log message ***

diff --git a/doc/rxvt.7.html b/doc/rxvt.7.html

--- a/doc/rxvt.7.html
+++ b/doc/rxvt.7.html
@@ -106,7 +106,7 @@

 	

-	
RXVT TECHNICAL REFERENCE
+	
RXVT-UNICODE TECHNICAL REFERENCE
 	
DESCRIPTION
 	
Definitions
 	
Values
@@ -205,10 +205,10 @@ display, create the listening socket and then fork.

 

 
 
How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
-
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.
 

 
 
How do I set the correct, full IP address for the DISPLAY variable?
@@ -763,7 +763,7 @@ resource to set it:

 
    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 use TERM=rxvt.

 

 
 
tic outputs some error when compiling the terminfo entry.
@@ -1050,7 +1050,7 @@ to 8-bit encodings.

 

 
 

-
RXVT TECHNICAL REFERENCE
+
RXVT-UNICODE TECHNICAL REFERENCE
 

 
 

@@ -1958,7 +1958,7 @@ button was pressed and are added together (X11 mouse report only):

 4Shift
 8Meta
 16Control
-32Double Click (Rxvt extension)
+32Double Click (rxvt extension)
 
Col = <x> - SPACE >
 
Row = <y> - SPACE >
 
diff --git a/doc/rxvt.7.man.in b/doc/rxvt.7.man.in

--- 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?"
@@ -914,7 +914,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 +1266,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 +2128,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` \- SPACE\*(C'\fB\fR
diff --git a/doc/rxvt.7.pod b/doc/rxvt.7.pod

--- a/doc/rxvt.7.pod
+++ b/doc/rxvt.7.pod
@@ -77,10 +77,10 @@ display, create the listening socket and then fork.

 =head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.

-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.

 =head3 How do I set the correct, full IP address for the DISPLAY variable?

@@ -689,7 +689,7 @@ resource to set it:
    URxvt.termName: rxvt

 If you don't plan to use B (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 C.

 =head3 C outputs some error when compiling the terminfo entry.

@@ -1005,7 +1005,7 @@ At the time of this writing, cygwin didn't seem to support any multi-byte
 encodings (you might try C), so you are likely limited
 to 8-bit encodings.

-=head1 RXVT TECHNICAL REFERENCE
+=head1 RXVT-UNICODE TECHNICAL REFERENCE

 =head1 DESCRIPTION

@@ -1913,7 +1913,7 @@ button was pressed and are added together (X11 mouse report only):
 	4	Shift
 	8	Meta
 	16	Control
-	32	Double Click I<(Rxvt extension)>
+	32	Double Click I<(rxvt extension)>

 =end table

diff --git a/doc/rxvt.7.txt b/doc/rxvt.7.txt

--- a/doc/rxvt.7.txt
+++ b/doc/rxvt.7.txt
@@ -66,10 +66,10 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
     listening socket and then fork.

    How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
-    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.

    How do I set the correct, full IP address for the DISPLAY variable?
     If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
@@ -644,7 +644,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
        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 use "TERM=rxvt".

    "tic" outputs some error when compiling the terminfo entry.
     Most likely it's the empty definition for "enacs=". Just replace it by
@@ -936,7 +936,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
     multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
     likely limited to 8-bit encodings.

-RXVT TECHNICAL REFERENCE
+RXVT-UNICODE TECHNICAL REFERENCE
 DESCRIPTION
     The rest of this document describes various technical aspects of
     rxvt-unicode. First the description of supported command sequences,
@@ -1505,7 +1505,7 @@ Mouse Reporting
            4               Shift           
            8               Meta            
            16              Control         
-           32              Double Click (Rxvt extension) 
+           32              Double Click (rxvt extension) 

         Col = " - SPACE"

-----END OF PAGE-----