From: root Date: Tue, 31 Jan 2006 20:58:12 +0000 (+0000) Subject: *** empty log message *** X-Git-Url: http://git.openbox.org/?a=commitdiff_plain;h=d1f6f1b096697bbf781ad1dc02446a3187894ee7;p=dana%2Furxvt.git *** empty log message *** --- diff --git a/doc/rxvt.7.man.in b/doc/rxvt.7.man.in index 740b6f24..dee7cb87 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 -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. +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 \fIis\fR unfair, as this involves xft +When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (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. .PP @@ -573,7 +573,8 @@ 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. +And here is a more complete set of non-standard colors described (not by +me) as \*(L"pretty girly\*(R". .PP .Vb 18 \& URxvt.cursorColor: #dc74d1 @@ -596,7 +597,10 @@ And here is a more complete set of non-standard colors. \& URxvt.color15: #e1dddd .Ve .PP -(They were described (not by me) as \*(L"pretty girly\*(R"). +\fIWhy do some characters look so much different than others?\fR +.IX Subsection "Why do some characters look so much different than others?" +.PP +See next entry. .PP \fIHow does rxvt-unicode choose fonts?\fR .IX Subsection "How does rxvt-unicode choose fonts?" @@ -910,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 and use \f(CW\*(C`TERM=rxvt\*(C'\fR. +the rxvt terminfo file with the rxvt-unicode one. .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." @@ -1262,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-UNICODE TECHNICAL REFERENCE" -.IX Header "RXVT-UNICODE TECHNICAL REFERENCE" +.SH "RXVT TECHNICAL REFERENCE" +.IX Header "RXVT TECHNICAL REFERENCE" .SH "DESCRIPTION" .IX Header "DESCRIPTION" The rest of this document describes various technical aspects of @@ -2124,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