ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.man.in
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents):
Revision 1.65 by root, Tue Jan 31 21:00:26 2006 UTC vs.
Revision 1.73 by root, Tue Feb 21 01:00:40 2006 UTC

127.\} 127.\}
128.rm #[ #] #H #V #F C 128.rm #[ #] #H #V #F C
129.\" ======================================================================== 129.\" ========================================================================
130.\" 130.\"
131.IX Title "rxvt 7" 131.IX Title "rxvt 7"
132.TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE" 132.TH rxvt 7 "2006-02-21" "7.6" "RXVT-UNICODE"
133.SH "NAME" 133.SH "NAME"
134RXVT REFERENCE \- FAQ, command sequences and other background information 134RXVT REFERENCE \- FAQ, command sequences and other background information
135.SH "SYNOPSIS" 135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS" 136.IX Header "SYNOPSIS"
137.Vb 2 137.Vb 2
214\fIHow can I start @@URXVT_NAME@@d in a race-free way?\fR 214\fIHow can I start @@URXVT_NAME@@d in a race-free way?\fR
215.IX Subsection "How can I start @@URXVT_NAME@@d in a race-free way?" 215.IX Subsection "How can I start @@URXVT_NAME@@d in a race-free way?"
216.PP 216.PP
217Try \f(CW\*(C`@@URXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@URXVT_NAME@@d to open the 217Try \f(CW\*(C`@@URXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@URXVT_NAME@@d to open the
218display, create the listening socket and then fork. 218display, create the listening socket and then fork.
219.PP
220\fIHow can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?\fR
221.IX Subsection "How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?"
222.PP
223If you want to start @@URXVT_NAME@@d automatically whenever you run
224@@URXVT_NAME@@c and the daemon isn't running yet, use this script:
225.PP
226.Vb 6
227\& #!/bin/sh
228\& @@URXVT_NAME@@c "$@"
229\& if [ $? -eq 2 ]; then
230\& @@URXVT_NAME@@d -q -o -f
231\& @@URXVT_NAME@@c "$@"
232\& fi
233.Ve
234.PP
235This tries to create a new terminal, and if fails with exit status 2,
236meaning it couldn't connect to the daemon, it will start the daemon and
237re-run the command. Subsequent invocations of the script will re-use the
238existing daemon.
219.PP 239.PP
220\fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR 240\fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR
221.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." 241.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."
222.PP 242.PP
223The original rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", 243The original rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R",
275\& text data bss drs rss filename 295\& text data bss drs rss filename
276\& 98398 1664 24 15695 1824 rxvt --disable-everything 296\& 98398 1664 24 15695 1824 rxvt --disable-everything
277\& 188985 9048 66616 18222 1788 urxvt --disable-everything 297\& 188985 9048 66616 18222 1788 urxvt --disable-everything
278.Ve 298.Ve
279.PP 299.PP
280When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft 300When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which \fIis\fR unfair, as this involves xft
281and full locale/XIM support which are quite bloaty inside libX11 and my 301and full locale/XIM support which are quite bloaty inside libX11 and my
282libc), the two diverge, but not unreasnobaly so. 302libc), the two diverge, but not unreasnobaly so.
283.PP 303.PP
284.Vb 3 304.Vb 3
285\& text data bss drs rss filename 305\& text data bss drs rss filename
400.Ve 420.Ve
401.PP 421.PP
402Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR 422Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR
403by other values to change the degree of opacity. If it doesn't work and 423by other values to change the degree of opacity. If it doesn't work and
404your server crashes, you got to keep the pieces. 424your server crashes, you got to keep the pieces.
405.PP
406\fIWhy do some chinese characters look so different than others?\fR
407.IX Subsection "Why do some chinese characters look so different than others?"
408.PP
409This is because there is a difference between script and language \*(--
410rxvt-unicode does not know which language the text that is output is,
411as it only knows the unicode character codes. If rxvt-unicode first
412sees a japanese/chinese character, it might choose a japanese font for
413display. Subsequent japanese characters will use that font. Now, many
414chinese characters aren't represented in japanese fonts, so when the first
415non-japanese character comes up, rxvt-unicode will look for a chinese font
416\&\*(-- unfortunately at this point, it will still use the japanese font for
417chinese characters that are also in the japanese font.
418.PP
419The workaround is easy: just tag a chinese font at the end of your font
420list (see the previous question). The key is to view the font list as
421a preference list: If you expect more japanese, list a japanese font
422first. If you expect more chinese, put a chinese font first.
423.PP
424In the future it might be possible to switch language preferences at
425runtime (the internal data structure has no problem with using different
426fonts for the same character at the same time, but no interface for this
427has been designed yet).
428.PP
429Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document).
430.PP 425.PP
431\fIWhy does rxvt-unicode sometimes leave pixel droppings?\fR 426\fIWhy does rxvt-unicode sometimes leave pixel droppings?\fR
432.IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?" 427.IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?"
433.PP 428.PP
434Most fonts were not designed for terminal use, which means that character 429Most fonts were not designed for terminal use, which means that character
571\& URxvt.color13: #FF00FF 566\& URxvt.color13: #FF00FF
572\& URxvt.color14: #00FFFF 567\& URxvt.color14: #00FFFF
573\& URxvt.color15: #FFFFFF 568\& URxvt.color15: #FFFFFF
574.Ve 569.Ve
575.PP 570.PP
576And here is a more complete set of non-standard colors described (not by 571And here is a more complete set of non-standard colors.
577me) as \*(L"pretty girly\*(R".
578.PP 572.PP
579.Vb 18 573.Vb 18
580\& URxvt.cursorColor: #dc74d1 574\& URxvt.cursorColor: #dc74d1
581\& URxvt.pointerColor: #dc74d1 575\& URxvt.pointerColor: #dc74d1
582\& URxvt.background: #0e0e0e 576\& URxvt.background: #0e0e0e
595\& URxvt.color14: #73f7ff 589\& URxvt.color14: #73f7ff
596\& URxvt.color7: #e1dddd 590\& URxvt.color7: #e1dddd
597\& URxvt.color15: #e1dddd 591\& URxvt.color15: #e1dddd
598.Ve 592.Ve
599.PP 593.PP
594They have been described (not by me) as \*(L"pretty girly\*(R".
595.PP
600\fIWhy do some characters look so much different than others?\fR 596\fIWhy do some characters look so much different than others?\fR
601.IX Subsection "Why do some characters look so much different than others?" 597.IX Subsection "Why do some characters look so much different than others?"
602.PP 598.PP
603See next entry. 599See next entry.
604.PP 600.PP
630search and use less resources within rxvt-unicode and the X\-server. 626search and use less resources within rxvt-unicode and the X\-server.
631.PP 627.PP
632The only limitation is that none of the fonts may be larger than the base 628The only limitation is that none of the fonts may be larger than the base
633font, as the base font defines the terminal character cell size, which 629font, as the base font defines the terminal character cell size, which
634must be the same due to the way terminals work. 630must be the same due to the way terminals work.
631.PP
632\fIWhy do some chinese characters look so different than others?\fR
633.IX Subsection "Why do some chinese characters look so different than others?"
634.PP
635This is because there is a difference between script and language \*(--
636rxvt-unicode does not know which language the text that is output is,
637as it only knows the unicode character codes. If rxvt-unicode first
638sees a japanese/chinese character, it might choose a japanese font for
639display. Subsequent japanese characters will use that font. Now, many
640chinese characters aren't represented in japanese fonts, so when the first
641non-japanese character comes up, rxvt-unicode will look for a chinese font
642\&\*(-- unfortunately at this point, it will still use the japanese font for
643chinese characters that are also in the japanese font.
644.PP
645The workaround is easy: just tag a chinese font at the end of your font
646list (see the previous question). The key is to view the font list as
647a preference list: If you expect more japanese, list a japanese font
648first. If you expect more chinese, put a chinese font first.
649.PP
650In the future it might be possible to switch language preferences at
651runtime (the internal data structure has no problem with using different
652fonts for the same character at the same time, but no interface for this
653has been designed yet).
654.PP
655Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document).
635.Sh "Keyboard, Mouse & User Interaction" 656.Sh "Keyboard, Mouse & User Interaction"
636.IX Subsection "Keyboard, Mouse & User Interaction" 657.IX Subsection "Keyboard, Mouse & User Interaction"
637\fIThe new selection selects pieces that are too big, how can I select single words?\fR 658\fIThe new selection selects pieces that are too big, how can I select single words?\fR
638.IX Subsection "The new selection selects pieces that are too big, how can I select single words?" 659.IX Subsection "The new selection selects pieces that are too big, how can I select single words?"
639.PP 660.PP
858Rather than have rxvt-unicode try to accommodate all the various possible 879Rather than have rxvt-unicode try to accommodate all the various possible
859keyboard mappings, it is better to use `xmodmap' to remap the keys as 880keyboard mappings, it is better to use `xmodmap' to remap the keys as
860required for your particular machine. 881required for your particular machine.
861.Sh "Terminal Configuration" 882.Sh "Terminal Configuration"
862.IX Subsection "Terminal Configuration" 883.IX Subsection "Terminal Configuration"
884\fICan I see a typical configuration?\fR
885.IX Subsection "Can I see a typical configuration?"
886.PP
887The default configuration tries to be xterm\-like, which I don't like that
888much, but it's least surprise to regular users.
889.PP
890As a rxvt or rxvt-unicode user, you are practically supposed to invest
891time into customising your terminal. To get you started, here is the
892author's .Xdefaults entries, with comments on what they do:
893.PP
894.Vb 2
895\& URxvt.cutchars: "()*,<>[]{}|'
896\& URxvt.print-pipe: cat >/tmp/xxx
897.Ve
898.PP
899These are just for testing stuff.
900.PP
901.Vb 2
902\& URxvt.imLocale: ja_JP.UTF-8
903\& URxvt.preeditType: OnTheSpot,None
904.Ve
905.PP
906This tells rxvt-unicode to use a special locale when communicating with
907the X Input Method, and also tells it to only use the OnTheSpot pre-edit
908type, which requires the \f(CW\*(C`xim\-onthespot\*(C'\fR perl extension but rewards me
909with correct-looking fonts.
910.PP
911.Vb 6
912\& URxvt.perl-lib: /root/lib/urxvt
913\& URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
914\& URxvt.selection.pattern-0: ( at .*? line \e\ed+)
915\& URxvt.selection.pattern-1: ^(/[^:]+):\e
916\& URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\e\ed+):?$/:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/
917\& URxvt.selection-autotransform.1: s/^ at (.*?) line (\e\ed+)$/:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/
918.Ve
919.PP
920This is my perl configuration. The first two set the perl library
921directory and also tells urxvt to use a large number of extensions. I
922develop for myself mostly, so I actually use most of the extensions I
923write.
924.PP
925The selection stuff mainly makes the selection perl-error-message aware
926and tells it to convert pelr error mssages into vi-commands to load the
927relevant file and go tot he error line number.
928.PP
929.Vb 2
930\& URxvt.scrollstyle: plain
931\& URxvt.secondaryScroll: true
932.Ve
933.PP
934As the documentation says: plain is the preferred scrollbar for the
935author. The \f(CW\*(C`secondaryScroll\*(C'\fR confgiures urxvt to scroll in full-screen
936apps, like screen, so lines scorlled out of screen end up in urxvt's
937scrollback buffer.
938.PP
939.Vb 7
940\& URxvt.background: #000000
941\& URxvt.foreground: gray90
942\& URxvt.color7: gray90
943\& URxvt.colorBD: #ffffff
944\& URxvt.cursorColor: #e0e080
945\& URxvt.throughColor: #8080f0
946\& URxvt.highlightColor: #f0f0f0
947.Ve
948.PP
949Some colours. Not sure which ones are being used or even non\-defaults, but
950these are in my .Xdefaults. Most notably, they set foreground/background
951to light gray/black, and also make sure that the colour 7 matches the
952default foreground colour.
953.PP
954.Vb 1
955\& URxvt.underlineColor: yellow
956.Ve
957.PP
958Another colour, makes underline lines look different. Sometimes hurts, but
959is mostly a nice effect.
960.PP
961.Vb 4
962\& URxvt.geometry: 154x36
963\& URxvt.loginShell: false
964\& URxvt.meta: ignore
965\& URxvt.utmpInhibit: true
966.Ve
967.PP
968Uh, well, should be mostly self\-explanatory. By specifying some defaults
969manually, I can quickly switch them for testing.
970.PP
971.Vb 1
972\& URxvt.saveLines: 8192
973.Ve
974.PP
975A large scrollback buffer is essential. Really.
976.PP
977.Vb 1
978\& URxvt.mapAlert: true
979.Ve
980.PP
981The only case I use it is for my \s-1IRC\s0 window, which I like to keep
982iconified till people msg me (which beeps).
983.PP
984.Vb 1
985\& URxvt.visualBell: true
986.Ve
987.PP
988The audible bell is often annoying, especially when in a crowd.
989.PP
990.Vb 1
991\& URxvt.insecure: true
992.Ve
993.PP
994Please don't hack my mutt! Ooops...
995.PP
996.Vb 1
997\& URxvt.pastableTabs: false
998.Ve
999.PP
1000I once thought this is a great idea.
1001.PP
1002.Vb 9
1003\& urxvt.font: 9x15bold,\e
1004\& -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\e
1005\& -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \e
1006\& [codeset=JISX0208]xft:Kochi Gothic, \e
1007\& xft:Bitstream Vera Sans Mono:autohint=true, \e
1008\& xft:Code2000:antialias=false
1009\& urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
1010\& urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
1011\& urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
1012.Ve
1013.PP
1014I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
1015overwhelmed. A special note: the \f(CW\*(C`9x15bold\*(C'\fR mentioend above is actually
1016the version from XFree\-3.3, as XFree\-4 replaced it by a totally different
1017font (different glyphs for \f(CW\*(C`;\*(C'\fR and many other harmless characters),
1018while the second font is actually the \f(CW\*(C`9x15bold\*(C'\fR from XFree4/XOrg. The
1019bold version has less chars than the medium version, so I use it for rare
1020characters, too. Whene ditign sources with vim, I use italic for comments
1021and other stuff, which looks quite good with Bitstream Vera anti\-aliased.
1022.PP
1023Terminus is a quite bad font (many very wrong glyphs), but for most of my
1024purposes, it works, and gives a different look, as my normal (Non\-bold)
1025font is already bold, and I want to see a difference between bold and
1026normal fonts.
1027.PP
1028Please note that I used the \f(CW\*(C`urxvt\*(C'\fR instance name and not the \f(CW\*(C`URxvt\*(C'\fR
1029class name. Thats because I use different configs for different purposes,
1030for example, my \s-1IRC\s0 window is started with \f(CW\*(C`\-name IRC\*(C'\fR, and uses these
1031defaults:
1032.PP
1033.Vb 9
1034\& IRC*title: IRC
1035\& IRC*geometry: 87x12+535+542
1036\& IRC*saveLines: 0
1037\& IRC*mapAlert: true
1038\& IRC*font: suxuseuro
1039\& IRC*boldFont: suxuseuro
1040\& IRC*colorBD: white
1041\& IRC*keysym.M-C-1: command:\e033]710;suxuseuro\e007\e033]711;suxuseuro\e007
1042\& IRC*keysym.M-C-2: command:\e033]710;9x15bold\e007\e033]711;9x15bold\e007
1043.Ve
1044.PP
1045\&\f(CW\*(C`Alt\-Shift\-1\*(C'\fR and \f(CW\*(C`Alt\-Shift\-2\*(C'\fR switch between two different font
1046sizes. \f(CW\*(C`suxuseuro\*(C'\fR allows me to keep an eye (and actually read)
1047stuff while keeping a very small window. If somebody pastes something
1048complicated (e.g. japanese), I temporarily switch to a larger font.
1049.PP
1050The above is all in my \f(CW\*(C`.Xdefaults\*(C'\fR (I don't use \f(CW\*(C`.Xresources\*(C'\fR nor
1051\&\f(CW\*(C`xrdb\*(C'\fR). I also have some resources in a separate \f(CW\*(C`.Xdefaults\-hostname\*(C'\fR
1052file for different hosts, for example, on ym main desktop, I use:
1053.PP
1054.Vb 5
1055\& URxvt.keysym.C-M-q: command:\e033[3;5;5t
1056\& URxvt.keysym.C-M-y: command:\e033[3;5;606t
1057\& URxvt.keysym.C-M-e: command:\e033[3;1605;5t
1058\& URxvt.keysym.C-M-c: command:\e033[3;1605;606t
1059\& URxvt.keysym.C-M-p: perl:test
1060.Ve
1061.PP
1062The first for keysym definitions allow me to quickly bring some windows
1063in the layout I like most. Ion users might start laughing but will stop
1064immediately when I tell them that I use my own Fvwm2 module for much the
1065same effect as Ion provides, and I only very rarely use the above key
1066combinations :\->
1067.PP
863\fIWhy doesn't rxvt-unicode read my resources?\fR 1068\fIWhy doesn't rxvt-unicode read my resources?\fR
864.IX Subsection "Why doesn't rxvt-unicode read my resources?" 1069.IX Subsection "Why doesn't rxvt-unicode read my resources?"
865.PP 1070.PP
866Well, why, indeed? It does, in a way very similar to other X 1071Well, why, indeed? It does, in a way very similar to other X
867applications. Most importantly, this means that if you or your \s-1OS\s0 loads 1072applications. Most importantly, this means that if you or your \s-1OS\s0 loads
1117.PP 1322.PP
1118You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except 1323You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except
1119for some locales where character width differs between program\- and 1324for some locales where character width differs between program\- and
1120rxvt\-unicode\-locales. 1325rxvt\-unicode\-locales.
1121.PP 1326.PP
1327\fII have problems getting my input method working.\fR
1328.IX Subsection "I have problems getting my input method working."
1329.PP
1330Try a search engine, as this is slightly different for every input method server.
1331.PP
1332Here is a checklist:
1333.IP "\- Make sure your locale \fIand\fR the imLocale are supported on your \s-1OS\s0." 4
1334.IX Item "- Make sure your locale and the imLocale are supported on your OS."
1335Try \f(CW\*(C`locale \-a\*(C'\fR or check the documentation for your \s-1OS\s0.
1336.IP "\- Make sure your locale or imLocale matches a locale supported by your \s-1XIM\s0." 4
1337.IX Item "- Make sure your locale or imLocale matches a locale supported by your XIM."
1338For example, \fBkinput2\fR does not support \s-1UTF\-8\s0 locales, you should use
1339\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR or equivalent.
1340.IP "\- Make sure your \s-1XIM\s0 server is actually running." 4
1341.IX Item "- Make sure your XIM server is actually running."
1342.PD 0
1343.ie n .IP "\- Make sure the ""XMODIFIERS""\fR environment variable is set correctly when \fIstarting rxvt\-unicode." 4
1344.el .IP "\- Make sure the \f(CWXMODIFIERS\fR environment variable is set correctly when \fIstarting\fR rxvt\-unicode." 4
1345.IX Item "- Make sure the XMODIFIERS environment variable is set correctly when starting rxvt-unicode."
1346.PD
1347When you want to use e.g. \fBkinput2\fR, it must be set to
1348\&\f(CW\*(C`@im=kinput2\*(C'\fR. For \fBscim\fR, use \f(CW\*(C`@im=SCIM\*(C'\fR. Youc an see what input
1349method servers are running with this command:
1350.Sp
1351.Vb 1
1352\& xprop -root XIM_SERVERS
1353.Ve
1354.IP "*" 4
1355.PP
1122\fIMy input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?\fR 1356\fIMy input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?\fR
1123.IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?" 1357.IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?"
1124.PP 1358.PP
1125You can specify separate locales for the input method and the rest of the 1359You can specify separate locales for the input method and the rest of the
1126terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR: 1360terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR:
1128.Vb 1 1362.Vb 1
1129\& URxvt.imlocale: ja_JP.EUC-JP 1363\& URxvt.imlocale: ja_JP.EUC-JP
1130.Ve 1364.Ve
1131.PP 1365.PP
1132Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still 1366Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still
1133use your input method. Please note, however, that you will not be able to 1367use your input method. Please note, however, that, depending on your Xlib
1134input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input 1368version, you may not be able to input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a
1135method limits you. 1369normal way then, as your input method limits you.
1136.PP 1370.PP
1137\fIRxvt-unicode crashes when the X Input Method changes or exits.\fR 1371\fIRxvt-unicode crashes when the X Input Method changes or exits.\fR
1138.IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits." 1372.IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits."
1139.PP 1373.PP
1140Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by 1374Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by
1266At the time of this writing, cygwin didn't seem to support any multi-byte 1500At the time of this writing, cygwin didn't seem to support any multi-byte
1267encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited 1501encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited
1268to 8\-bit encodings. 1502to 8\-bit encodings.
1269.SH "RXVT-UNICODE TECHNICAL REFERENCE" 1503.SH "RXVT-UNICODE TECHNICAL REFERENCE"
1270.IX Header "RXVT-UNICODE TECHNICAL REFERENCE" 1504.IX Header "RXVT-UNICODE TECHNICAL REFERENCE"
1271.SH "DESCRIPTION"
1272.IX Header "DESCRIPTION"
1273The rest of this document describes various technical aspects of 1505The rest of this document describes various technical aspects of
1274\&\fBrxvt-unicode\fR. First the description of supported command sequences, 1506\&\fBrxvt-unicode\fR. First the description of supported command sequences,
1275followed by pixmap support and last by a description of all features 1507followed by pixmap support and last by a description of all features
1276selectable at \f(CW\*(C`configure\*(C'\fR time. 1508selectable at \f(CW\*(C`configure\*(C'\fR time.
1277.SH "Definitions" 1509.Sh "Definitions"
1278.IX Header "Definitions" 1510.IX Subsection "Definitions"
1279.ie n .IP "\fB\fB""c""\fB\fR" 4 1511.ie n .IP "\fB\fB""c""\fB\fR" 4
1280.el .IP "\fB\f(CBc\fB\fR" 4 1512.el .IP "\fB\f(CBc\fB\fR" 4
1281.IX Item "c" 1513.IX Item "c"
1282The literal character c. 1514The literal character c.
1283.ie n .IP "\fB\fB""C""\fB\fR" 4 1515.ie n .IP "\fB\fB""C""\fB\fR" 4
1296parameters, separated by \f(CW\*(C`;\*(C'\fR character(s). 1528parameters, separated by \f(CW\*(C`;\*(C'\fR character(s).
1297.ie n .IP "\fB\fB""Pt""\fB\fR" 4 1529.ie n .IP "\fB\fB""Pt""\fB\fR" 4
1298.el .IP "\fB\f(CBPt\fB\fR" 4 1530.el .IP "\fB\f(CBPt\fB\fR" 4
1299.IX Item "Pt" 1531.IX Item "Pt"
1300A text parameter composed of printable characters. 1532A text parameter composed of printable characters.
1301.SH "Values" 1533.Sh "Values"
1302.IX Header "Values" 1534.IX Subsection "Values"
1303.ie n .IP "\fB\fB""ENQ""\fB\fR" 4 1535.ie n .IP "\fB\fB""ENQ""\fB\fR" 4
1304.el .IP "\fB\f(CBENQ\fB\fR" 4 1536.el .IP "\fB\f(CBENQ\fB\fR" 4
1305.IX Item "ENQ" 1537.IX Item "ENQ"
1306Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0) 1538Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0)
1307request attributes from terminal. See \fB\f(CB\*(C`ESC [ Ps c\*(C'\fB\fR. 1539request attributes from terminal. See \fB\f(CB\*(C`ESC [ Ps c\*(C'\fB\fR.
1345Switch to Standard Character Set 1577Switch to Standard Character Set
1346.ie n .IP "\fB\fB""SPC""\fB\fR" 4 1578.ie n .IP "\fB\fB""SPC""\fB\fR" 4
1347.el .IP "\fB\f(CBSPC\fB\fR" 4 1579.el .IP "\fB\f(CBSPC\fB\fR" 4
1348.IX Item "SPC" 1580.IX Item "SPC"
1349Space Character 1581Space Character
1350.SH "Escape Sequences" 1582.Sh "Escape Sequences"
1351.IX Header "Escape Sequences" 1583.IX Subsection "Escape Sequences"
1352.ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4 1584.ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4
1353.el .IP "\fB\f(CBESC # 8\fB\fR" 4 1585.el .IP "\fB\f(CBESC # 8\fB\fR" 4
1354.IX Item "ESC # 8" 1586.IX Item "ESC # 8"
1355\&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0) 1587\&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0)
1356.ie n .IP "\fB\fB""ESC 7""\fB\fR" 4 1588.ie n .IP "\fB\fB""ESC 7""\fB\fR" 4
1449.TE 1681.TE
1450 1682
1451.PP 1683.PP
1452 1684
1453.IX Xref "CSI" 1685.IX Xref "CSI"
1454.SH "CSI (Command Sequence Introducer) Sequences" 1686.Sh "\s-1CSI\s0 (Command Sequence Introducer) Sequences"
1455.IX Header "CSI (Command Sequence Introducer) Sequences" 1687.IX Subsection "CSI (Command Sequence Introducer) Sequences"
1456.ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4 1688.ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4
1457.el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4 1689.el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4
1458.IX Item "ESC [ Ps @" 1690.IX Item "ESC [ Ps @"
1459Insert \fB\f(CB\*(C`Ps\*(C'\fB\fR (Blank) Character(s) [default: 1] (\s-1ICH\s0) 1691Insert \fB\f(CB\*(C`Ps\*(C'\fB\fR (Blank) Character(s) [default: 1] (\s-1ICH\s0)
1460.IX Xref "ESCOBPsA" 1692.IX Xref "ESCOBPsA"
1723.IX Item "ESC [ Ps x" 1955.IX Item "ESC [ Ps x"
1724Request Terminal Parameters (\s-1DECREQTPARM\s0) 1956Request Terminal Parameters (\s-1DECREQTPARM\s0)
1725.PP 1957.PP
1726 1958
1727.IX Xref "PrivateModes" 1959.IX Xref "PrivateModes"
1728.SH "DEC Private Modes" 1960.Sh "\s-1DEC\s0 Private Modes"
1729.IX Header "DEC Private Modes" 1961.IX Subsection "DEC Private Modes"
1730.ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4 1962.ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4
1731.el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4 1963.el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4
1732.IX Item "ESC [ ? Pm h" 1964.IX Item "ESC [ ? Pm h"
1733\&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0) 1965\&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0)
1734.ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4 1966.ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4
2001.RE 2233.RE
2002.PD 2234.PD
2003.PP 2235.PP
2004 2236
2005.IX Xref "XTerm" 2237.IX Xref "XTerm"
2006.SH "XTerm Operating System Commands" 2238.Sh "XTerm Operating System Commands"
2007.IX Header "XTerm Operating System Commands" 2239.IX Subsection "XTerm Operating System Commands"
2008.ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4 2240.ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4
2009.el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4 2241.el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4
2010.IX Item "ESC ] Ps;Pt ST" 2242.IX Item "ESC ] Ps;Pt ST"
2011Set XTerm Parameters. 8\-bit \s-1ST:\s0 0x9c, 7\-bit \s-1ST\s0 sequence: \s-1ESC\s0 \e (0x1b, 2243Set XTerm Parameters. 8\-bit \s-1ST:\s0 0x9c, 7\-bit \s-1ST\s0 sequence: \s-1ESC\s0 \e (0x1b,
20120x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any 22440x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any
2044Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). 2276Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
2045Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). 2277Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
2046Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl). 2278Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).
2047.TE 2279.TE
2048 2280
2049.PP
2050
2051.IX Xref "XPM"
2052.SH "XPM" 2281.SH "XPM"
2053.IX Header "XPM" 2282.IX Header "XPM"
2054For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value 2283For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value
2055of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a 2284of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a
2056sequence of scaling/positioning commands separated by semi\-colons. The 2285sequence of scaling/positioning commands separated by semi\-colons. The
2425.IX Item "--disable-new-selection" 2654.IX Item "--disable-new-selection"
2426Remove support for mouse selection style like that of xterm. 2655Remove support for mouse selection style like that of xterm.
2427.IP "\-\-enable\-dmalloc (default: off)" 4 2656.IP "\-\-enable\-dmalloc (default: off)" 4
2428.IX Item "--enable-dmalloc (default: off)" 2657.IX Item "--enable-dmalloc (default: off)"
2429Use Gray Watson's malloc \- which is good for debugging See 2658Use Gray Watson's malloc \- which is good for debugging See
2430http://www.letters.com/dmalloc/ for details If you use either this or the 2659<http://www.letters.com/dmalloc/> for details If you use either this or the
2431next option, you may need to edit src/Makefile after compiling to point 2660next option, you may need to edit src/Makefile after compiling to point
2432\&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places. 2661\&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places.
2433.Sp 2662.Sp
2434You can only use either this option and the following (should 2663You can only use either this option and the following (should
2435you use either) . 2664you use either) .

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines