--- rxvt-unicode/doc/rxvt.7.man.in 2006/01/31 21:04:14 1.66 +++ rxvt-unicode/doc/rxvt.7.man.in 2006/02/02 18:04:45 1.72 @@ -129,7 +129,7 @@ .\" ======================================================================== .\" .IX Title "rxvt 7" -.TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE" +.TH rxvt 7 "2006-02-02" "7.5" "RXVT-UNICODE" .SH "NAME" RXVT REFERENCE \- FAQ, command sequences and other background information .SH "SYNOPSIS" @@ -217,6 +217,26 @@ Try \f(CW\*(C`@@URXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@URXVT_NAME@@d to open the display, create the listening socket and then fork. .PP +\fIHow can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?\fR +.IX Subsection "How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?" +.PP +If you want to start @@URXVT_NAME@@d automatically whenever you run +@@URXVT_NAME@@c and the daemon isn't running yet, use this script: +.PP +.Vb 6 +\& #!/bin/sh +\& @@URXVT_NAME@@c "$@" +\& if [ $? -eq 2 ]; then +\& @@URXVT_NAME@@d -q -o -f +\& @@URXVT_NAME@@c "$@" +\& fi +.Ve +.PP +This tries to create a new terminal, and if fails with exit status 2, +meaning it couldn't connect to the daemon, it will start the daemon and +re-run the command. Subsequent invocations of the script will re-use the +existing daemon. +.PP \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 @@ -403,31 +423,6 @@ by other values to change the degree of opacity. If it doesn't work and your server crashes, you got to keep the pieces. .PP -\fIWhy do some chinese characters look so different than others?\fR -.IX Subsection "Why do some chinese characters look so different than others?" -.PP -This is because there is a difference between script and language \*(-- -rxvt-unicode does not know which language the text that is output is, -as it only knows the unicode character codes. If rxvt-unicode first -sees a japanese/chinese character, it might choose a japanese font for -display. Subsequent japanese characters will use that font. Now, many -chinese characters aren't represented in japanese fonts, so when the first -non-japanese character comes up, rxvt-unicode will look for a chinese font -\&\*(-- unfortunately at this point, it will still use the japanese font for -chinese characters that are also in the japanese font. -.PP -The workaround is easy: just tag a chinese font at the end of your font -list (see the previous question). The key is to view the font list as -a preference list: If you expect more japanese, list a japanese font -first. If you expect more chinese, put a chinese font first. -.PP -In the future it might be possible to switch language preferences at -runtime (the internal data structure has no problem with using different -fonts for the same character at the same time, but no interface for this -has been designed yet). -.PP -Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document). -.PP \fIWhy does rxvt-unicode sometimes leave pixel droppings?\fR .IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?" .PP @@ -596,7 +591,7 @@ \& URxvt.color15: #e1dddd .Ve .PP -(They were described (not by me) as \*(L"pretty girly\*(R"). +They have been 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?" @@ -633,6 +628,31 @@ The only limitation is that none of the fonts may be larger than the base font, as the base font defines the terminal character cell size, which must be the same due to the way terminals work. +.PP +\fIWhy do some chinese characters look so different than others?\fR +.IX Subsection "Why do some chinese characters look so different than others?" +.PP +This is because there is a difference between script and language \*(-- +rxvt-unicode does not know which language the text that is output is, +as it only knows the unicode character codes. If rxvt-unicode first +sees a japanese/chinese character, it might choose a japanese font for +display. Subsequent japanese characters will use that font. Now, many +chinese characters aren't represented in japanese fonts, so when the first +non-japanese character comes up, rxvt-unicode will look for a chinese font +\&\*(-- unfortunately at this point, it will still use the japanese font for +chinese characters that are also in the japanese font. +.PP +The workaround is easy: just tag a chinese font at the end of your font +list (see the previous question). The key is to view the font list as +a preference list: If you expect more japanese, list a japanese font +first. If you expect more chinese, put a chinese font first. +.PP +In the future it might be possible to switch language preferences at +runtime (the internal data structure has no problem with using different +fonts for the same character at the same time, but no interface for this +has been designed yet). +.PP +Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document). .Sh "Keyboard, Mouse & User Interaction" .IX Subsection "Keyboard, Mouse & User Interaction" \fIThe new selection selects pieces that are too big, how can I select single words?\fR @@ -1120,6 +1140,35 @@ for some locales where character width differs between program\- and rxvt\-unicode\-locales. .PP +\fII have problems getting my input method working.\fR +.IX Subsection "I have problems getting my input method working." +.PP +Try a search engine, as this is slightly different for every input method server. +.PP +Here is a checklist: +.IP "\- Make sure your locale \fIand\fR the imLocale are supported on your \s-1OS\s0." 4 +.IX Item "- Make sure your locale and the imLocale are supported on your OS." +Try \f(CW\*(C`locale \-a\*(C'\fR or check the documentation for your \s-1OS\s0. +.IP "\- Make sure your locale or imLocale matches a locale supported by your \s-1XIM\s0." 4 +.IX Item "- Make sure your locale or imLocale matches a locale supported by your XIM." +For example, \fBkinput2\fR does not support \s-1UTF\-8\s0 locales, you should use +\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR or equivalent. +.IP "\- Make sure your \s-1XIM\s0 server is actually running." 4 +.IX Item "- Make sure your XIM server is actually running." +.PD 0 +.ie n .IP "\- Make sure the ""XMODIFIERS""\fR environment variable is set correctly when \fIstarting rxvt\-unicode." 4 +.el .IP "\- Make sure the \f(CWXMODIFIERS\fR environment variable is set correctly when \fIstarting\fR rxvt\-unicode." 4 +.IX Item "- Make sure the XMODIFIERS environment variable is set correctly when starting rxvt-unicode." +.PD +When you want to use e.g. \fBkinput2\fR, it must be set to +\&\f(CW\*(C`@im=kinput2\*(C'\fR. For \fBscim\fR, use \f(CW\*(C`@im=SCIM\*(C'\fR. Youc an see what input +method servers are running with this command: +.Sp +.Vb 1 +\& xprop -root XIM_SERVERS +.Ve +.IP "*" 4 +.PP \fIMy input method wants but I want \s-1UTF\-8\s0, what can I do?\fR .IX Subsection "My input method wants but I want UTF-8, what can I do?" .PP @@ -1131,9 +1180,9 @@ .Ve .PP Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still -use your input method. Please note, however, that you will not be able to -input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input -method limits you. +use your input method. Please note, however, that, depending on your Xlib +version, you may not be able to input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a +normal way then, as your input method limits you. .PP \fIRxvt-unicode crashes when the X Input Method changes or exits.\fR .IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits." @@ -1269,14 +1318,12 @@ to 8\-bit encodings. .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 \&\fBrxvt-unicode\fR. First the description of supported command sequences, followed by pixmap support and last by a description of all features selectable at \f(CW\*(C`configure\*(C'\fR time. -.SH "Definitions" -.IX Header "Definitions" +.Sh "Definitions" +.IX Subsection "Definitions" .ie n .IP "\fB\fB""c""\fB\fR" 4 .el .IP "\fB\f(CBc\fB\fR" 4 .IX Item "c" @@ -1299,8 +1346,8 @@ .el .IP "\fB\f(CBPt\fB\fR" 4 .IX Item "Pt" A text parameter composed of printable characters. -.SH "Values" -.IX Header "Values" +.Sh "Values" +.IX Subsection "Values" .ie n .IP "\fB\fB""ENQ""\fB\fR" 4 .el .IP "\fB\f(CBENQ\fB\fR" 4 .IX Item "ENQ" @@ -1348,8 +1395,8 @@ .el .IP "\fB\f(CBSPC\fB\fR" 4 .IX Item "SPC" Space Character -.SH "Escape Sequences" -.IX Header "Escape Sequences" +.Sh "Escape Sequences" +.IX Subsection "Escape Sequences" .ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4 .el .IP "\fB\f(CBESC # 8\fB\fR" 4 .IX Item "ESC # 8" @@ -1452,8 +1499,8 @@ .PP .IX Xref "CSI" -.SH "CSI (Command Sequence Introducer) Sequences" -.IX Header "CSI (Command Sequence Introducer) Sequences" +.Sh "\s-1CSI\s0 (Command Sequence Introducer) Sequences" +.IX Subsection "CSI (Command Sequence Introducer) Sequences" .ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4 .el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4 .IX Item "ESC [ Ps @" @@ -1726,8 +1773,8 @@ .PP .IX Xref "PrivateModes" -.SH "DEC Private Modes" -.IX Header "DEC Private Modes" +.Sh "\s-1DEC\s0 Private Modes" +.IX Subsection "DEC Private Modes" .ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4 .el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4 .IX Item "ESC [ ? Pm h" @@ -2004,8 +2051,8 @@ .PP .IX Xref "XTerm" -.SH "XTerm Operating System Commands" -.IX Header "XTerm Operating System Commands" +.Sh "XTerm Operating System Commands" +.IX Subsection "XTerm Operating System Commands" .ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4 .el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4 .IX Item "ESC ] Ps;Pt ST" @@ -2047,9 +2094,6 @@ Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl). .TE -.PP - -.IX Xref "XPM" .SH "XPM" .IX Header "XPM" For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value @@ -2428,7 +2472,7 @@ .IP "\-\-enable\-dmalloc (default: off)" 4 .IX Item "--enable-dmalloc (default: off)" Use Gray Watson's malloc \- which is good for debugging See -http://www.letters.com/dmalloc/ for details If you use either this or the + for details If you use either this or the next option, you may need to edit src/Makefile after compiling to point \&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places. .Sp