--- rxvt-unicode/doc/rxvt.7.man.in 2006/01/31 20:50:48 1.62 +++ rxvt-unicode/doc/rxvt.7.man.in 2006/02/21 01:00:40 1.73 @@ -129,7 +129,7 @@ .\" ======================================================================== .\" .IX Title "rxvt 7" -.TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE" +.TH rxvt 7 "2006-02-21" "7.6" "RXVT-UNICODE" .SH "NAME" RXVT REFERENCE \- FAQ, command sequences and other background information .SH "SYNOPSIS" @@ -155,8 +155,8 @@ .PP The newest version of this document is also available on the World Wide Web at . -.SH "FREQUENTLY ASKED QUESTIONS" -.IX Header "FREQUENTLY ASKED QUESTIONS" +.SH "RXVT\-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS" +.IX Header "RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS" .Sh "Meta, Features & Commandline Issues" .IX Subsection "Meta, Features & Commandline Issues" \fIMy question isn't answered here, can I ask a human?\fR @@ -174,7 +174,7 @@ give you tabs: .PP .Vb 1 -\& @@RXVT_NAME@@ -pe tabbed +\& @@URXVT_NAME@@ -pe tabbed .Ve .PP .Vb 1 @@ -192,7 +192,7 @@ .PP The version number is displayed with the usage (\-h). Also the escape sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When -using the @@RXVT_NAME@@c client, the version displayed is that of the +using the @@URXVT_NAME@@c client, the version displayed is that of the daemon. .PP \fIRxvt-unicode uses gobs of memory, how can I reduce that?\fR @@ -211,19 +211,39 @@ use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as rxvt-unicode then uses 8 bytes per screen cell. .PP -\fIHow can I start @@RXVT_NAME@@d in a race-free way?\fR -.IX Subsection "How can I start @@RXVT_NAME@@d in a race-free way?" +\fIHow can I start @@URXVT_NAME@@d in a race-free way?\fR +.IX Subsection "How can I start @@URXVT_NAME@@d in a race-free way?" .PP -Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the +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 -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 +297,7 @@ \& 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 @@ -362,7 +382,7 @@ .PP .Vb 2 \& Esetroot wallpaper.jpg -\& @@RXVT_NAME@@ -ip -tint red -sh 40 +\& @@URXVT_NAME@@ -ip -tint red -sh 40 .Ve .PP That works. If you think it doesn't, you lack transparency and tinting @@ -374,7 +394,7 @@ .PP .Vb 2 \& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm -\& @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background +\& @@URXVT_NAME@@ -pixmap background.xpm -pe automove-background .Ve .PP That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you @@ -383,7 +403,7 @@ 3. Use an \s-1ARGB\s0 visual: .PP .Vb 1 -\& @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc +\& @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc .Ve .PP This requires \s-1XFT\s0 support, and the support of your X\-server. If that @@ -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 @@ -573,8 +568,7 @@ \& 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 +591,8 @@ \& URxvt.color15: #e1dddd .Ve .PP +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?" .PP @@ -621,7 +617,7 @@ e.g.: .PP .Vb 1 -\& @@RXVT_NAME@@ -fn basefont,font2,font3... +\& @@URXVT_NAME@@ -fn basefont,font2,font3... .Ve .PP When rxvt-unicode sees a character, it will first look at the base @@ -632,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 @@ -665,7 +686,7 @@ .PP If you only want to disable specific features, you first have to identify which perl extension is responsible. For this, read the section -\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For +\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@URXVT_NAME@@\fIperl\fR\|(3) manpage. For example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify this \fBperl-ext-common\fR resource: .PP @@ -767,13 +788,13 @@ .Vb 3 \& # use Backspace = ^H \& $ stty erase ^H -\& $ @@RXVT_NAME@@ +\& $ @@URXVT_NAME@@ .Ve .PP .Vb 3 \& # use Backspace = ^? \& $ stty erase ^? -\& $ @@RXVT_NAME@@ +\& $ @@URXVT_NAME@@ .Ve .PP Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR. @@ -816,7 +837,7 @@ you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can use the `keysym' resource to alter the keystrings associated with keysyms. .PP -Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR +Here's an example for a URxvt session started using \f(CW\*(C`@@URXVT_NAME@@ \-name URxvt\*(C'\fR .PP .Vb 20 \& URxvt.keysym.Home: \e033[1~ @@ -860,6 +881,190 @@ required for your particular machine. .Sh "Terminal Configuration" .IX Subsection "Terminal Configuration" +\fICan I see a typical configuration?\fR +.IX Subsection "Can I see a typical configuration?" +.PP +The default configuration tries to be xterm\-like, which I don't like that +much, but it's least surprise to regular users. +.PP +As a rxvt or rxvt-unicode user, you are practically supposed to invest +time into customising your terminal. To get you started, here is the +author's .Xdefaults entries, with comments on what they do: +.PP +.Vb 2 +\& URxvt.cutchars: "()*,<>[]{}|' +\& URxvt.print-pipe: cat >/tmp/xxx +.Ve +.PP +These are just for testing stuff. +.PP +.Vb 2 +\& URxvt.imLocale: ja_JP.UTF-8 +\& URxvt.preeditType: OnTheSpot,None +.Ve +.PP +This tells rxvt-unicode to use a special locale when communicating with +the X Input Method, and also tells it to only use the OnTheSpot pre-edit +type, which requires the \f(CW\*(C`xim\-onthespot\*(C'\fR perl extension but rewards me +with correct-looking fonts. +.PP +.Vb 6 +\& URxvt.perl-lib: /root/lib/urxvt +\& URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard +\& URxvt.selection.pattern-0: ( at .*? line \e\ed+) +\& URxvt.selection.pattern-1: ^(/[^:]+):\e +\& URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\e\ed+):?$/:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/ +\& URxvt.selection-autotransform.1: s/^ at (.*?) line (\e\ed+)$/:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/ +.Ve +.PP +This is my perl configuration. The first two set the perl library +directory and also tells urxvt to use a large number of extensions. I +develop for myself mostly, so I actually use most of the extensions I +write. +.PP +The selection stuff mainly makes the selection perl-error-message aware +and tells it to convert pelr error mssages into vi-commands to load the +relevant file and go tot he error line number. +.PP +.Vb 2 +\& URxvt.scrollstyle: plain +\& URxvt.secondaryScroll: true +.Ve +.PP +As the documentation says: plain is the preferred scrollbar for the +author. The \f(CW\*(C`secondaryScroll\*(C'\fR confgiures urxvt to scroll in full-screen +apps, like screen, so lines scorlled out of screen end up in urxvt's +scrollback buffer. +.PP +.Vb 7 +\& URxvt.background: #000000 +\& URxvt.foreground: gray90 +\& URxvt.color7: gray90 +\& URxvt.colorBD: #ffffff +\& URxvt.cursorColor: #e0e080 +\& URxvt.throughColor: #8080f0 +\& URxvt.highlightColor: #f0f0f0 +.Ve +.PP +Some colours. Not sure which ones are being used or even non\-defaults, but +these are in my .Xdefaults. Most notably, they set foreground/background +to light gray/black, and also make sure that the colour 7 matches the +default foreground colour. +.PP +.Vb 1 +\& URxvt.underlineColor: yellow +.Ve +.PP +Another colour, makes underline lines look different. Sometimes hurts, but +is mostly a nice effect. +.PP +.Vb 4 +\& URxvt.geometry: 154x36 +\& URxvt.loginShell: false +\& URxvt.meta: ignore +\& URxvt.utmpInhibit: true +.Ve +.PP +Uh, well, should be mostly self\-explanatory. By specifying some defaults +manually, I can quickly switch them for testing. +.PP +.Vb 1 +\& URxvt.saveLines: 8192 +.Ve +.PP +A large scrollback buffer is essential. Really. +.PP +.Vb 1 +\& URxvt.mapAlert: true +.Ve +.PP +The only case I use it is for my \s-1IRC\s0 window, which I like to keep +iconified till people msg me (which beeps). +.PP +.Vb 1 +\& URxvt.visualBell: true +.Ve +.PP +The audible bell is often annoying, especially when in a crowd. +.PP +.Vb 1 +\& URxvt.insecure: true +.Ve +.PP +Please don't hack my mutt! Ooops... +.PP +.Vb 1 +\& URxvt.pastableTabs: false +.Ve +.PP +I once thought this is a great idea. +.PP +.Vb 9 +\& urxvt.font: 9x15bold,\e +\& -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\e +\& -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \e +\& [codeset=JISX0208]xft:Kochi Gothic, \e +\& xft:Bitstream Vera Sans Mono:autohint=true, \e +\& xft:Code2000:antialias=false +\& urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 +\& urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true +\& urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true +.Ve +.PP +I wrote rxvt-unicode to be able to specify fonts exactly. So don't be +overwhelmed. A special note: the \f(CW\*(C`9x15bold\*(C'\fR mentioend above is actually +the version from XFree\-3.3, as XFree\-4 replaced it by a totally different +font (different glyphs for \f(CW\*(C`;\*(C'\fR and many other harmless characters), +while the second font is actually the \f(CW\*(C`9x15bold\*(C'\fR from XFree4/XOrg. The +bold version has less chars than the medium version, so I use it for rare +characters, too. Whene ditign sources with vim, I use italic for comments +and other stuff, which looks quite good with Bitstream Vera anti\-aliased. +.PP +Terminus is a quite bad font (many very wrong glyphs), but for most of my +purposes, it works, and gives a different look, as my normal (Non\-bold) +font is already bold, and I want to see a difference between bold and +normal fonts. +.PP +Please note that I used the \f(CW\*(C`urxvt\*(C'\fR instance name and not the \f(CW\*(C`URxvt\*(C'\fR +class name. Thats because I use different configs for different purposes, +for example, my \s-1IRC\s0 window is started with \f(CW\*(C`\-name IRC\*(C'\fR, and uses these +defaults: +.PP +.Vb 9 +\& IRC*title: IRC +\& IRC*geometry: 87x12+535+542 +\& IRC*saveLines: 0 +\& IRC*mapAlert: true +\& IRC*font: suxuseuro +\& IRC*boldFont: suxuseuro +\& IRC*colorBD: white +\& IRC*keysym.M-C-1: command:\e033]710;suxuseuro\e007\e033]711;suxuseuro\e007 +\& IRC*keysym.M-C-2: command:\e033]710;9x15bold\e007\e033]711;9x15bold\e007 +.Ve +.PP +\&\f(CW\*(C`Alt\-Shift\-1\*(C'\fR and \f(CW\*(C`Alt\-Shift\-2\*(C'\fR switch between two different font +sizes. \f(CW\*(C`suxuseuro\*(C'\fR allows me to keep an eye (and actually read) +stuff while keeping a very small window. If somebody pastes something +complicated (e.g. japanese), I temporarily switch to a larger font. +.PP +The above is all in my \f(CW\*(C`.Xdefaults\*(C'\fR (I don't use \f(CW\*(C`.Xresources\*(C'\fR nor +\&\f(CW\*(C`xrdb\*(C'\fR). I also have some resources in a separate \f(CW\*(C`.Xdefaults\-hostname\*(C'\fR +file for different hosts, for example, on ym main desktop, I use: +.PP +.Vb 5 +\& URxvt.keysym.C-M-q: command:\e033[3;5;5t +\& URxvt.keysym.C-M-y: command:\e033[3;5;606t +\& URxvt.keysym.C-M-e: command:\e033[3;1605;5t +\& URxvt.keysym.C-M-c: command:\e033[3;1605;606t +\& URxvt.keysym.C-M-p: perl:test +.Ve +.PP +The first for keysym definitions allow me to quickly bring some windows +in the layout I like most. Ion users might start laughing but will stop +immediately when I tell them that I use my own Fvwm2 module for much the +same effect as Ion provides, and I only very rarely use the above key +combinations :\-> +.PP \fIWhy doesn't rxvt-unicode read my resources?\fR .IX Subsection "Why doesn't rxvt-unicode read my resources?" .PP @@ -914,7 +1119,7 @@ .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." @@ -922,8 +1127,8 @@ Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. .PP -\fI\f(CI\*(C`bash\*(C'\fI's readline does not work correctly under @@RXVT_NAME@@.\fR -.IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@." +\fI\f(CI\*(C`bash\*(C'\fI's readline does not work correctly under @@URXVT_NAME@@.\fR +.IX Subsection "bash's readline does not work correctly under @@URXVT_NAME@@." .PP See next entry. .PP @@ -1119,6 +1324,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 @@ -1130,9 +1364,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." @@ -1266,16 +1500,14 @@ 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 "DESCRIPTION" -.IX Header "DESCRIPTION" +.SH "RXVT-UNICODE TECHNICAL REFERENCE" +.IX Header "RXVT-UNICODE TECHNICAL REFERENCE" 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" @@ -1298,8 +1530,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" @@ -1347,8 +1579,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" @@ -1451,8 +1683,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 @" @@ -1725,8 +1957,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" @@ -2003,8 +2235,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" @@ -2046,9 +2278,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 @@ -2128,7 +2357,7 @@ 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 @@ -2427,7 +2656,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