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

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.103 by root, Tue Jan 31 20:57:29 2006 UTC vs.
Revision 1.120 by root, Mon Aug 7 15:59:44 2006 UTC

… …
19all escape sequences, and other background information. 19all escape sequences, and other background information.
20 20
21The newest version of this document is also available on the World Wide Web at 21The newest version of this document is also available on the World Wide Web at
22L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>. 22L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
23 23
24=head1 FREQUENTLY ASKED QUESTIONS 24=head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
25 25
26 26
27=head2 Meta, Features & Commandline Issues 27=head2 Meta, Features & Commandline Issues
28 28
29=head3 My question isn't answered here, can I ask a human? 29=head3 My question isn't answered here, can I ask a human?
… …
73=head3 How can I start @@URXVT_NAME@@d in a race-free way? 73=head3 How can I start @@URXVT_NAME@@d in a race-free way?
74 74
75Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the 75Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
76display, create the listening socket and then fork. 76display, create the listening socket and then fork.
77 77
78=head3 How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?
79
80If you want to start @@URXVT_NAME@@d automatically whenever you run
81@@URXVT_NAME@@c and the daemon isn't running yet, use this script:
82
83 #!/bin/sh
84 @@URXVT_NAME@@c "$@"
85 if [ $? -eq 2 ]; then
86 @@URXVT_NAME@@d -q -o -f
87 @@URXVT_NAME@@c "$@"
88 fi
89
90This tries to create a new terminal, and if fails with exit status 2,
91meaning it couldn't connect to the daemon, it will start the daemon and
92re-run the command. Subsequent invocations of the script will re-use the
93existing daemon.
94
78=head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. 95=head3 How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
79 96
80rxvt and rxvt-unicode always export the variable "COLORTERM", so you can 97The original rxvt and rxvt-unicode always export the variable "COLORTERM",
81check and see if that is set. Note that several programs, JED, slrn, 98so you can check and see if that is set. Note that several programs, JED,
82Midnight Commander automatically check this variable to decide whether or 99slrn, Midnight Commander automatically check this variable to decide
83not to use color. 100whether or not to use color.
84 101
85=head3 How do I set the correct, full IP address for the DISPLAY variable? 102=head3 How do I set the correct, full IP address for the DISPLAY variable?
86 103
87If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled 104If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
88insecure mode then it is possible to use the following shell script 105insecure mode then it is possible to use the following shell script
… …
125 142
126 text data bss drs rss filename 143 text data bss drs rss filename
127 98398 1664 24 15695 1824 rxvt --disable-everything 144 98398 1664 24 15695 1824 rxvt --disable-everything
128 188985 9048 66616 18222 1788 urxvt --disable-everything 145 188985 9048 66616 18222 1788 urxvt --disable-everything
129 146
130When you C<--enable-everything> (which _is_ unfair, as this involves xft 147When you C<--enable-everything> (which I<is> unfair, as this involves xft
131and full locale/XIM support which are quite bloaty inside libX11 and my 148and full locale/XIM support which are quite bloaty inside libX11 and my
132libc), the two diverge, but not unreasnobaly so. 149libc), the two diverge, but not unreasonably so.
133 150
134 text data bss drs rss filename 151 text data bss drs rss filename
135 163431 2152 24 20123 2060 rxvt --enable-everything 152 163431 2152 24 20123 2060 rxvt --enable-everything
136 1035683 49680 66648 29096 3680 urxvt --enable-everything 153 1035683 49680 66648 29096 3680 urxvt --enable-everything
137 154
… …
224 241
225 @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc 242 @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
226 243
227This requires XFT support, and the support of your X-server. If that 244This requires XFT support, and the support of your X-server. If that
228doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't 245doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
229there yet, no matter what they claim. Rxvt-Unicode contains the neccessary 246there yet, no matter what they claim. Rxvt-Unicode contains the necessary
230bugfixes and workarounds for Xft and Xlib to make it work, but that 247bugfixes and workarounds for Xft and Xlib to make it work, but that
231doesn't mean that your WM has the required kludges in place. 248doesn't mean that your WM has the required kludges in place.
232 249
2334. Use xcompmgr and let it do the job: 2504. Use xcompmgr and let it do the job:
234 251
… …
236 -set _NET_WM_WINDOW_OPACITY 0xc0000000 253 -set _NET_WM_WINDOW_OPACITY 0xc0000000
237 254
238Then click on a window you want to make transparent. Replace C<0xc0000000> 255Then click on a window you want to make transparent. Replace C<0xc0000000>
239by other values to change the degree of opacity. If it doesn't work and 256by other values to change the degree of opacity. If it doesn't work and
240your server crashes, you got to keep the pieces. 257your server crashes, you got to keep the pieces.
241
242=head3 Why do some chinese characters look so different than others?
243
244This is because there is a difference between script and language --
245rxvt-unicode does not know which language the text that is output is,
246as it only knows the unicode character codes. If rxvt-unicode first
247sees a japanese/chinese character, it might choose a japanese font for
248display. Subsequent japanese characters will use that font. Now, many
249chinese characters aren't represented in japanese fonts, so when the first
250non-japanese character comes up, rxvt-unicode will look for a chinese font
251-- unfortunately at this point, it will still use the japanese font for
252chinese characters that are also in the japanese font.
253
254The workaround is easy: just tag a chinese font at the end of your font
255list (see the previous question). The key is to view the font list as
256a preference list: If you expect more japanese, list a japanese font
257first. If you expect more chinese, put a chinese font first.
258
259In the future it might be possible to switch language preferences at
260runtime (the internal data structure has no problem with using different
261fonts for the same character at the same time, but no interface for this
262has been designed yet).
263
264Until then, you might get away with switching fonts at runtime (see L<Can
265I switch the fonts at runtime?> later in this document).
266 258
267=head3 Why does rxvt-unicode sometimes leave pixel droppings? 259=head3 Why does rxvt-unicode sometimes leave pixel droppings?
268 260
269Most fonts were not designed for terminal use, which means that character 261Most fonts were not designed for terminal use, which means that character
270size varies a lot. A font that is otherwise fine for terminal use might 262size varies a lot. A font that is otherwise fine for terminal use might
… …
276however: Xft fonts often draw glyphs larger than their acclaimed bounding 268however: Xft fonts often draw glyphs larger than their acclaimed bounding
277box, and rxvt-unicode has no way of detecting this (the correct way is to 269box, and rxvt-unicode has no way of detecting this (the correct way is to
278ask for the character bounding box, which unfortunately is wrong in these 270ask for the character bounding box, which unfortunately is wrong in these
279cases). 271cases).
280 272
281It's not clear (to me at least), wether this is a bug in Xft, freetype, 273It's not clear (to me at least), whether this is a bug in Xft, freetype,
282or the respective font. If you encounter this problem you might try using 274or the respective font. If you encounter this problem you might try using
283the C<-lsp> option to give the font more height. If that doesn't work, you 275the C<-lsp> option to give the font more height. If that doesn't work, you
284might be forced to use a different font. 276might be forced to use a different font.
285 277
286All of this is not a problem when using X11 core fonts, as their bounding 278All of this is not a problem when using X11 core fonts, as their bounding
… …
310=head3 Can I switch the fonts at runtime? 302=head3 Can I switch the fonts at runtime?
311 303
312Yes, using an escape sequence. Try something like this, which has the same 304Yes, using an escape sequence. Try something like this, which has the same
313effect as using the C<-fn> switch, and takes effect immediately: 305effect as using the C<-fn> switch, and takes effect immediately:
314 306
315 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" 307 printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic"
316 308
317This is useful if you e.g. work primarily with japanese (and prefer a 309This is useful if you e.g. work primarily with japanese (and prefer a
318japanese font), but you have to switch to chinese temporarily, where 310japanese font), but you have to switch to chinese temporarily, where
319japanese fonts would only be in your way. 311japanese fonts would only be in your way.
320 312
… …
322 314
323=head3 Why do italic characters look as if clipped? 315=head3 Why do italic characters look as if clipped?
324 316
325Many fonts have difficulties with italic characters and hinting. For 317Many fonts have difficulties with italic characters and hinting. For
326example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans 318example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
327Mono> completely fails in it's italic face. A workaround might be to 319Mono> completely fails in its italic face. A workaround might be to
328enable freetype autohinting, i.e. like this: 320enable freetype autohinting, i.e. like this:
329 321
330 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 322 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
331 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 323 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
332 324
… …
338memory and also speeds up rendering considerably. 330memory and also speeds up rendering considerably.
339 331
340=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? 332=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
341 333
342Rxvt-unicode will use whatever you specify as a font. If it needs to 334Rxvt-unicode will use whatever you specify as a font. If it needs to
343fall back to it's default font search list it will prefer X11 core 335fall back to its default font search list it will prefer X11 core
344fonts, because they are small and fast, and then use Xft fonts. It has 336fonts, because they are small and fast, and then use Xft fonts. It has
345antialiasing disabled for most of them, because the author thinks they 337antialiasing disabled for most of them, because the author thinks they
346look best that way. 338look best that way.
347 339
348If you want antialiasing, you have to specify the fonts manually. 340If you want antialiasing, you have to specify the fonts manually.
… …
388 URxvt.color12: #0000FF 380 URxvt.color12: #0000FF
389 URxvt.color13: #FF00FF 381 URxvt.color13: #FF00FF
390 URxvt.color14: #00FFFF 382 URxvt.color14: #00FFFF
391 URxvt.color15: #FFFFFF 383 URxvt.color15: #FFFFFF
392 384
393And here is a more complete set of non-standard colors described (not by 385And here is a more complete set of non-standard colors.
394me) as "pretty girly".
395 386
396 URxvt.cursorColor: #dc74d1 387 URxvt.cursorColor: #dc74d1
397 URxvt.pointerColor: #dc74d1 388 URxvt.pointerColor: #dc74d1
398 URxvt.background: #0e0e0e 389 URxvt.background: #0e0e0e
399 URxvt.foreground: #4ad5e1 390 URxvt.foreground: #4ad5e1
… …
410 URxvt.color6: #73f7ff 401 URxvt.color6: #73f7ff
411 URxvt.color14: #73f7ff 402 URxvt.color14: #73f7ff
412 URxvt.color7: #e1dddd 403 URxvt.color7: #e1dddd
413 URxvt.color15: #e1dddd 404 URxvt.color15: #e1dddd
414 405
406They have been described (not by me) as "pretty girly".
407
415=head3 Why do some characters look so much different than others? 408=head3 Why do some characters look so much different than others?
416 409
417See next entry. 410See next entry.
418 411
419=head3 How does rxvt-unicode choose fonts? 412=head3 How does rxvt-unicode choose fonts?
420 413
421Most fonts do not contain the full range of Unicode, which is 414Most fonts do not contain the full range of Unicode, which is
422fine. Chances are that the font you (or the admin/package maintainer of 415fine. Chances are that the font you (or the admin/package maintainer of
423your system/os) have specified does not cover all the characters you want 416your system/os) have specified does not cover all the characters you want
424to display. 417to display.
425 418
426B<rxvt-unicode> makes a best-effort try at finding a replacement 419B<rxvt-unicode> makes a best-effort try at finding a replacement
427font. Often the result is fine, but sometimes the chosen font looks 420font. Often the result is fine, but sometimes the chosen font looks
428bad/ugly/wrong. Some fonts have totally strange characters that don't 421bad/ugly/wrong. Some fonts have totally strange characters that don't
429resemble the correct glyph at all, and rxvt-unicode lacks the artificial 422resemble the correct glyph at all, and rxvt-unicode lacks the artificial
430intelligence to detect that a specific glyph is wrong: it has to believe 423intelligence to detect that a specific glyph is wrong: it has to believe
431the font that the characters it claims to contain indeed look correct. 424the font that the characters it claims to contain indeed look correct.
432 425
433In that case, select a font of your taste and add it to the font list, 426In that case, select a font of your taste and add it to the font list,
434e.g.: 427e.g.:
435 428
436 @@URXVT_NAME@@ -fn basefont,font2,font3... 429 @@URXVT_NAME@@ -fn basefont,font2,font3...
437 430
438When rxvt-unicode sees a character, it will first look at the base 431When rxvt-unicode sees a character, it will first look at the base
439font. If the base font does not contain the character, it will go to the 432font. If the base font does not contain the character, it will go to the
440next font, and so on. Specifying your own fonts will also speed up this 433next font, and so on. Specifying your own fonts will also speed up this
441search and use less resources within rxvt-unicode and the X-server. 434search and use less resources within rxvt-unicode and the X-server.
442 435
443The only limitation is that none of the fonts may be larger than the base 436The only limitation is that none of the fonts may be larger than the base
444font, as the base font defines the terminal character cell size, which 437font, as the base font defines the terminal character cell size, which
445must be the same due to the way terminals work. 438must be the same due to the way terminals work.
446 439
440=head3 Why do some chinese characters look so different than others?
441
442This is because there is a difference between script and language --
443rxvt-unicode does not know which language the text that is output is,
444as it only knows the unicode character codes. If rxvt-unicode first
445sees a japanese/chinese character, it might choose a japanese font for
446display. Subsequent japanese characters will use that font. Now, many
447chinese characters aren't represented in japanese fonts, so when the first
448non-japanese character comes up, rxvt-unicode will look for a chinese font
449-- unfortunately at this point, it will still use the japanese font for
450chinese characters that are also in the japanese font.
451
452The workaround is easy: just tag a chinese font at the end of your font
453list (see the previous question). The key is to view the font list as
454a preference list: If you expect more japanese, list a japanese font
455first. If you expect more chinese, put a chinese font first.
456
457In the future it might be possible to switch language preferences at
458runtime (the internal data structure has no problem with using different
459fonts for the same character at the same time, but no interface for this
460has been designed yet).
461
462Until then, you might get away with switching fonts at runtime (see L<Can
463I switch the fonts at runtime?> later in this document).
447 464
448=head2 Keyboard, Mouse & User Interaction 465=head2 Keyboard, Mouse & User Interaction
449 466
450=head3 The new selection selects pieces that are too big, how can I select single words? 467=head3 The new selection selects pieces that are too big, how can I select single words?
451 468
… …
495circumstances, it will move your cursor around when you click into the 512circumstances, it will move your cursor around when you click into the
496line that contains it. It tries hard not to do this at the wrong moment, 513line that contains it. It tries hard not to do this at the wrong moment,
497but when running a program that doesn't parse cursor movements or in some 514but when running a program that doesn't parse cursor movements or in some
498cases during rlogin sessions, it fails to detect this properly. 515cases during rlogin sessions, it fails to detect this properly.
499 516
500You can permamently switch this feature off by disabling the C<readline> 517You can permanently switch this feature off by disabling the C<readline>
501extension: 518extension:
502 519
503 URxvt.perl-ext-common: default,-readline 520 URxvt.perl-ext-common: default,-readline
504 521
505=head3 My numerical keypad acts weird and generates differing output? 522=head3 My numerical keypad acts weird and generates differing output?
506 523
507Some Debian GNUL/Linux users seem to have this problem, although no 524Some Debian GNUL/Linux users seem to have this problem, although no
508specific details were reported so far. It is possible that this is caused 525specific details were reported so far. It is possible that this is caused
509by the wrong C<TERM> setting, although the details of wether and how 526by the wrong C<TERM> setting, although the details of whether and how
510this can happen are unknown, as C<TERM=rxvt> should offer a compatible 527this can happen are unknown, as C<TERM=rxvt> should offer a compatible
511keymap. See the answer to the previous question, and please report if that 528keymap. See the answer to the previous question, and please report if that
512helped. 529helped.
513 530
514=head3 My Compose (Multi_key) key is no longer working. 531=head3 My Compose (Multi_key) key is no longer working.
… …
540depressed. 557depressed.
541 558
542=head3 What's with the strange Backspace/Delete key behaviour? 559=head3 What's with the strange Backspace/Delete key behaviour?
543 560
544Assuming that the physical Backspace key corresponds to the 561Assuming that the physical Backspace key corresponds to the
545BackSpace keysym (not likely for Linux ... see the following 562Backspace keysym (not likely for Linux ... see the following
546question) there are two standard values that can be used for 563question) there are two standard values that can be used for
547Backspace: C<^H> and C<^?>. 564Backspace: C<^H> and C<^?>.
548 565
549Historically, either value is correct, but rxvt-unicode adopts the debian 566Historically, either value is correct, but rxvt-unicode adopts the debian
550policy of using C<^?> when unsure, because it's the one only only correct 567policy of using C<^?> when unsure, because it's the one only only correct
… …
641 658
642 659
643 660
644=head2 Terminal Configuration 661=head2 Terminal Configuration
645 662
663=head3 Can I see a typical configuration?
664
665The default configuration tries to be xterm-like, which I don't like that
666much, but it's least surprise to regular users.
667
668As a rxvt or rxvt-unicode user, you are practically supposed to invest
669time into customising your terminal. To get you started, here is the
670author's .Xdefaults entries, with comments on what they do. It's certainly
671not I<typical>, but what's typical...
672
673 URxvt.cutchars: "()*,<>[]{}|'
674 URxvt.print-pipe: cat >/tmp/xxx
675
676These are just for testing stuff.
677
678 URxvt.imLocale: ja_JP.UTF-8
679 URxvt.preeditType: OnTheSpot,None
680
681This tells rxvt-unicode to use a special locale when communicating with
682the X Input Method, and also tells it to only use the OnTheSpot pre-edit
683type, which requires the C<xim-onthespot> perl extension but rewards me
684with correct-looking fonts.
685
686 URxvt.perl-lib: /root/lib/urxvt
687 URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
688 URxvt.selection.pattern-0: ( at .*? line \\d+)
689 URxvt.selection.pattern-1: ^(/[^:]+):\
690 URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
691 URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/
692
693This is my perl configuration. The first two set the perl library
694directory and also tells urxvt to use a large number of extensions. I
695develop for myself mostly, so I actually use most of the extensions I
696write.
697
698The selection stuff mainly makes the selection perl-error-message aware
699and tells it to convert perl error messages into vi-commands to load the
700relevant file and go tot he error line number.
701
702 URxvt.scrollstyle: plain
703 URxvt.secondaryScroll: true
704
705As the documentation says: plain is the preferred scrollbar for the
706author. The C<secondaryScroll> configures urxvt to scroll in full-screen
707apps, like screen, so lines scrolled out of screen end up in urxvt's
708scrollback buffer.
709
710 URxvt.background: #000000
711 URxvt.foreground: gray90
712 URxvt.color7: gray90
713 URxvt.colorBD: #ffffff
714 URxvt.cursorColor: #e0e080
715 URxvt.throughColor: #8080f0
716 URxvt.highlightColor: #f0f0f0
717
718Some colours. Not sure which ones are being used or even non-defaults, but
719these are in my .Xdefaults. Most notably, they set foreground/background
720to light gray/black, and also make sure that the colour 7 matches the
721default foreground colour.
722
723 URxvt.underlineColor: yellow
724
725Another colour, makes underline lines look different. Sometimes hurts, but
726is mostly a nice effect.
727
728 URxvt.geometry: 154x36
729 URxvt.loginShell: false
730 URxvt.meta: ignore
731 URxvt.utmpInhibit: true
732
733Uh, well, should be mostly self-explanatory. By specifying some defaults
734manually, I can quickly switch them for testing.
735
736 URxvt.saveLines: 8192
737
738A large scrollback buffer is essential. Really.
739
740 URxvt.mapAlert: true
741
742The only case I use it is for my IRC window, which I like to keep
743iconified till people msg me (which beeps).
744
745 URxvt.visualBell: true
746
747The audible bell is often annoying, especially when in a crowd.
748
749 URxvt.insecure: true
750
751Please don't hack my mutt! Ooops...
752
753 URxvt.pastableTabs: false
754
755I once thought this is a great idea.
756
757 urxvt.font: 9x15bold,\
758 -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
759 -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
760 [codeset=JISX0208]xft:Kochi Gothic, \
761 xft:Bitstream Vera Sans Mono:autohint=true, \
762 xft:Code2000:antialias=false
763 urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
764 urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
765 urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
766
767I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
768overwhelmed. A special note: the C<9x15bold> mentioned above is actually
769the version from XFree-3.3, as XFree-4 replaced it by a totally different
770font (different glyphs for C<;> and many other harmless characters),
771while the second font is actually the C<9x15bold> from XFree4/XOrg. The
772bold version has less chars than the medium version, so I use it for rare
773characters, too. When editing sources with vim, I use italic for comments
774and other stuff, which looks quite good with Bitstream Vera anti-aliased.
775
776Terminus is a quite bad font (many very wrong glyphs), but for most of my
777purposes, it works, and gives a different look, as my normal (Non-bold)
778font is already bold, and I want to see a difference between bold and
779normal fonts.
780
781Please note that I used the C<urxvt> instance name and not the C<URxvt>
782class name. Thats because I use different configs for different purposes,
783for example, my IRC window is started with C<-name IRC>, and uses these
784defaults:
785
786 IRC*title: IRC
787 IRC*geometry: 87x12+535+542
788 IRC*saveLines: 0
789 IRC*mapAlert: true
790 IRC*font: suxuseuro
791 IRC*boldFont: suxuseuro
792 IRC*colorBD: white
793 IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
794 IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
795
796C<Alt-Shift-1> and C<Alt-Shift-2> switch between two different font
797sizes. C<suxuseuro> allows me to keep an eye (and actually read)
798stuff while keeping a very small window. If somebody pastes something
799complicated (e.g. japanese), I temporarily switch to a larger font.
800
801The above is all in my C<.Xdefaults> (I don't use C<.Xresources> nor
802C<xrdb>). I also have some resources in a separate C<.Xdefaults-hostname>
803file for different hosts, for example, on ym main desktop, I use:
804
805 URxvt.keysym.C-M-q: command:\033[3;5;5t
806 URxvt.keysym.C-M-y: command:\033[3;5;606t
807 URxvt.keysym.C-M-e: command:\033[3;1605;5t
808 URxvt.keysym.C-M-c: command:\033[3;1605;606t
809 URxvt.keysym.C-M-p: perl:test
810
811The first for keysym definitions allow me to quickly bring some windows
812in the layout I like most. Ion users might start laughing but will stop
813immediately when I tell them that I use my own Fvwm2 module for much the
814same effect as Ion provides, and I only very rarely use the above key
815combinations :->
816
646=head3 Why doesn't rxvt-unicode read my resources? 817=head3 Why doesn't rxvt-unicode read my resources?
647 818
648Well, why, indeed? It does, in a way very similar to other X 819Well, why, indeed? It does, in a way very similar to other X
649applications. Most importantly, this means that if you or your OS loads 820applications. Most importantly, this means that if you or your OS loads
650resources into the X display (the right way to do it), rxvt-unicode will 821resources into the X display (the right way to do it), rxvt-unicode will
… …
658Also consider the form resources have to use: 829Also consider the form resources have to use:
659 830
660 URxvt.resource: value 831 URxvt.resource: value
661 832
662If you want to use another form (there are lots of different ways of 833If you want to use another form (there are lots of different ways of
663specifying resources), make sure you understand wether and why it 834specifying resources), make sure you understand whether and why it
664works. If unsure, use the form above. 835works. If unsure, use the form above.
665 836
666=head3 When I log-in to another system it tells me about missing terminfo data? 837=head3 When I log-in to another system it tells me about missing terminfo data?
667 838
668The terminal description used by rxvt-unicode is not as widely available 839The terminal description used by rxvt-unicode is not as widely available
… …
687resource to set it: 858resource to set it:
688 859
689 URxvt.termName: rxvt 860 URxvt.termName: rxvt
690 861
691If you don't plan to use B<rxvt> (quite common...) you could also replace 862If you don't plan to use B<rxvt> (quite common...) you could also replace
692the rxvt terminfo file with the rxvt-unicode one. 863the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>.
693 864
694=head3 C<tic> outputs some error when compiling the terminfo entry. 865=head3 C<tic> outputs some error when compiling the terminfo entry.
695 866
696Most likely it's the empty definition for C<enacs=>. Just replace it by 867Most likely it's the empty definition for C<enacs=>. Just replace it by
697C<enacs=\E[0@> and try again. 868C<enacs=\E[0@> and try again.
… …
705One reason you might want this is that some distributions or operating 876One reason you might want this is that some distributions or operating
706systems still compile some programs using the long-obsoleted termcap 877systems still compile some programs using the long-obsoleted termcap
707library (Fedora Core's bash is one example) and rely on a termcap entry 878library (Fedora Core's bash is one example) and rely on a termcap entry
708for C<rxvt-unicode>. 879for C<rxvt-unicode>.
709 880
710You could use rxvt's termcap entry with resonable results in many cases. 881You could use rxvt's termcap entry with reasonable results in many cases.
711You can also create a termcap entry by using terminfo's infocmp program 882You can also create a termcap entry by using terminfo's infocmp program
712like this: 883like this:
713 884
714 infocmp -C rxvt-unicode 885 infocmp -C rxvt-unicode
715 886
… …
737 :vs=\E[?25h: 908 :vs=\E[?25h:
738 909
739=head3 Why does C<ls> no longer have coloured output? 910=head3 Why does C<ls> no longer have coloured output?
740 911
741The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to 912The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
742decide wether a terminal has colour, but uses it's own configuration 913decide whether a terminal has colour, but uses its own configuration
743file. Needless to say, C<rxvt-unicode> is not in it's default file (among 914file. Needless to say, C<rxvt-unicode> is not in its default file (among
744with most other terminals supporting colour). Either add: 915with most other terminals supporting colour). Either add:
745 916
746 TERM rxvt-unicode 917 TERM rxvt-unicode
747 918
748to C</etc/DIR_COLORS> or simply add: 919to C</etc/DIR_COLORS> or simply add:
… …
789something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work. 960something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
790 961
791The best thing is to fix your startup environment, as you will likely run 962The best thing is to fix your startup environment, as you will likely run
792into other problems. If nothing works you can try this in your .profile. 963into other problems. If nothing works you can try this in your .profile.
793 964
794 printf '\e]701;%s\007' "$LC_CTYPE" 965 printf '\33]701;%s\007' "$LC_CTYPE"
795 966
796If this doesn't work, then maybe you use a C<LC_CTYPE> specification not 967If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
797supported on your systems. Some systems have a C<locale> command which 968supported on your systems. Some systems have a C<locale> command which
798displays this (also, C<perl -e0> can be used to check locale settings, as 969displays this (also, C<perl -e0> can be used to check locale settings, as
799it will complain loudly if it cannot set the locale). If it displays something 970it will complain loudly if it cannot set the locale). If it displays something
… …
820The reasons is that there exists a perfectly fine mechanism for selecting 991The reasons is that there exists a perfectly fine mechanism for selecting
821the encoding, doing I/O and (most important) communicating this to all 992the encoding, doing I/O and (most important) communicating this to all
822applications so everybody agrees on character properties such as width 993applications so everybody agrees on character properties such as width
823and code number. This mechanism is the I<locale>. Applications not using 994and code number. This mechanism is the I<locale>. Applications not using
824that info will have problems (for example, C<xterm> gets the width of 995that info will have problems (for example, C<xterm> gets the width of
825characters wrong as it uses it's own, locale-independent table under all 996characters wrong as it uses its own, locale-independent table under all
826locales). 997locales).
827 998
828Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All 999Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
829programs doing the same (that is, most) will automatically agree in the 1000programs doing the same (that is, most) will automatically agree in the
830interpretation of characters. 1001interpretation of characters.
… …
849=head3 Can I switch locales at runtime? 1020=head3 Can I switch locales at runtime?
850 1021
851Yes, using an escape sequence. Try something like this, which sets 1022Yes, using an escape sequence. Try something like this, which sets
852rxvt-unicode's idea of C<LC_CTYPE>. 1023rxvt-unicode's idea of C<LC_CTYPE>.
853 1024
854 printf '\e]701;%s\007' ja_JP.SJIS 1025 printf '\33]701;%s\007' ja_JP.SJIS
855 1026
856See also the previous answer. 1027See also the previous answer.
857 1028
858Sometimes this capability is rather handy when you want to work in 1029Sometimes this capability is rather handy when you want to work in
859one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it 1030one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
860(e.g. UTF-8). For example, I use this script to start C<xjdic>, which 1031(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
861first switches to a locale supported by xjdic and back later: 1032first switches to a locale supported by xjdic and back later:
862 1033
863 printf '\e]701;%s\007' ja_JP.SJIS 1034 printf '\33]701;%s\007' ja_JP.SJIS
864 xjdic -js 1035 xjdic -js
865 printf '\e]701;%s\007' de_DE.UTF-8 1036 printf '\33]701;%s\007' de_DE.UTF-8
866 1037
867You can also use xterm's C<luit> program, which usually works fine, except 1038You can also use xterm's C<luit> program, which usually works fine, except
868for some locales where character width differs between program- and 1039for some locales where character width differs between program- and
869rxvt-unicode-locales. 1040rxvt-unicode-locales.
870 1041
1042=head3 I have problems getting my input method working.
1043
1044Try a search engine, as this is slightly different for every input method server.
1045
1046Here is a checklist:
1047
1048=over 4
1049
1050=item - Make sure your locale I<and> the imLocale are supported on your OS.
1051
1052Try C<locale -a> or check the documentation for your OS.
1053
1054=item - Make sure your locale or imLocale matches a locale supported by your XIM.
1055
1056For example, B<kinput2> does not support UTF-8 locales, you should use
1057C<ja_JP.EUC-JP> or equivalent.
1058
1059=item - Make sure your XIM server is actually running.
1060
1061=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
1062
1063When you want to use e.g. B<kinput2>, it must be set to
1064C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. You can see what input
1065method servers are running with this command:
1066
1067 xprop -root XIM_SERVERS
1068
1069=item
1070
1071=back
1072
871=head3 My input method wants <some encoding> but I want UTF-8, what can I do? 1073=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
872 1074
873You can specify separate locales for the input method and the rest of the 1075You can specify separate locales for the input method and the rest of the
874terminal, using the resource C<imlocale>: 1076terminal, using the resource C<imlocale>:
875 1077
876 URxvt.imlocale: ja_JP.EUC-JP 1078 URxvt.imlocale: ja_JP.EUC-JP
877 1079
878Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still 1080Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
879use your input method. Please note, however, that you will not be able to 1081use your input method. Please note, however, that, depending on your Xlib
880input characters outside C<EUC-JP> in a normal way then, as your input 1082version, you may not be able to input characters outside C<EUC-JP> in a
881method limits you. 1083normal way then, as your input method limits you.
882 1084
883=head3 Rxvt-unicode crashes when the X Input Method changes or exits. 1085=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
884 1086
885Unfortunately, this is unavoidable, as the XIM protocol is racy by 1087Unfortunately, this is unavoidable, as the XIM protocol is racy by
886design. Applications can avoid some crashes at the expense of memory 1088design. Applications can avoid some crashes at the expense of memory
… …
912 1114
913=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? 1115=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
914 1116
915You should build one binary with the default options. F<configure> 1117You should build one binary with the default options. F<configure>
916now enables most useful options, and the trend goes to making them 1118now enables most useful options, and the trend goes to making them
917runtime-switchable, too, so there is usually no drawback to enbaling them, 1119runtime-switchable, too, so there is usually no drawback to enabling them,
918except higher disk and possibly memory usage. The perl interpreter should 1120except higher disk and possibly memory usage. The perl interpreter should
919be enabled, as important functionality (menus, selection, likely more in 1121be enabled, as important functionality (menus, selection, likely more in
920the future) depends on it. 1122the future) depends on it.
921 1123
922You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources 1124You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
… …
957 1159
958=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all. 1160=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
959 1161
960Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined 1162Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
961in your compile environment, or an implementation that implements it, 1163in your compile environment, or an implementation that implements it,
962wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that 1164whether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
963B<wchar_t> is represented as unicode. 1165B<wchar_t> is represented as unicode.
964 1166
965As you might have guessed, FreeBSD does neither define this symobl nor 1167As you might have guessed, FreeBSD does neither define this symbol nor
966does it support it. Instead, it uses it's own internal representation of 1168does it support it. Instead, it uses its own internal representation of
967B<wchar_t>. This is, of course, completely fine with respect to standards. 1169B<wchar_t>. This is, of course, completely fine with respect to standards.
968 1170
969However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and 1171However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
970C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>. 1172C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
971 1173
… …
1003 1205
1004At the time of this writing, cygwin didn't seem to support any multi-byte 1206At the time of this writing, cygwin didn't seem to support any multi-byte
1005encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited 1207encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
1006to 8-bit encodings. 1208to 8-bit encodings.
1007 1209
1008=head1 RXVT TECHNICAL REFERENCE 1210=head1 RXVT-UNICODE TECHNICAL REFERENCE
1009
1010=head1 DESCRIPTION
1011 1211
1012The rest of this document describes various technical aspects of 1212The rest of this document describes various technical aspects of
1013B<rxvt-unicode>. First the description of supported command sequences, 1213B<rxvt-unicode>. First the description of supported command sequences,
1014followed by pixmap support and last by a description of all features 1214followed by pixmap support and last by a description of all features
1015selectable at C<configure> time. 1215selectable at C<configure> time.
1016 1216
1017=head1 Definitions 1217=head2 Definitions
1018 1218
1019=over 4 1219=over 4
1020 1220
1021=item B<< C<c> >> 1221=item B<< C<c> >>
1022 1222
… …
1040 1240
1041A text parameter composed of printable characters. 1241A text parameter composed of printable characters.
1042 1242
1043=back 1243=back
1044 1244
1045=head1 Values 1245=head2 Values
1046 1246
1047=over 4 1247=over 4
1048 1248
1049=item B<< C<ENQ> >> 1249=item B<< C<ENQ> >>
1050 1250
… …
1093 1293
1094Space Character 1294Space Character
1095 1295
1096=back 1296=back
1097 1297
1098=head1 Escape Sequences 1298=head2 Escape Sequences
1099 1299
1100=over 4 1300=over 4
1101 1301
1102=item B<< C<ESC # 8> >> 1302=item B<< C<ESC # 8> >>
1103 1303
… …
1201 1401
1202=back 1402=back
1203 1403
1204X<CSI> 1404X<CSI>
1205 1405
1206=head1 CSI (Command Sequence Introducer) Sequences 1406=head2 CSI (Command Sequence Introducer) Sequences
1207 1407
1208=over 4 1408=over 4
1209 1409
1210=item B<< C<ESC [ Ps @> >> 1410=item B<< C<ESC [ Ps @> >>
1211 1411
… …
1481 1681
1482=back 1682=back
1483 1683
1484X<PrivateModes> 1684X<PrivateModes>
1485 1685
1486=head1 DEC Private Modes 1686=head2 DEC Private Modes
1487 1687
1488=over 4 1688=over 4
1489 1689
1490=item B<< C<ESC [ ? Pm h> >> 1690=item B<< C<ESC [ ? Pm h> >>
1491 1691
… …
1507 1707
1508Toggle DEC Private Mode Values (rxvt extension). I<where> 1708Toggle DEC Private Mode Values (rxvt extension). I<where>
1509 1709
1510=over 4 1710=over 4
1511 1711
1512=item B<< C<Ps = 1> >> (DECCKM) 1712=item B<< C<Pm = 1> >> (DECCKM)
1513 1713
1514=begin table 1714=begin table
1515 1715
1516 B<< C<h> >> Application Cursor Keys 1716 B<< C<h> >> Application Cursor Keys
1517 B<< C<l> >> Normal Cursor Keys 1717 B<< C<l> >> Normal Cursor Keys
1518 1718
1519=end table 1719=end table
1520 1720
1521=item B<< C<Ps = 2> >> (ANSI/VT52 mode) 1721=item B<< C<Pm = 2> >> (ANSI/VT52 mode)
1522 1722
1523=begin table 1723=begin table
1524 1724
1525 B<< C<h> >> Enter VT52 mode 1725 B<< C<h> >> Enter VT52 mode
1526 B<< C<l> >> Enter VT52 mode 1726 B<< C<l> >> Enter VT52 mode
1527 1727
1528=end table 1728=end table
1529 1729
1530=item B<< C<Ps = 3> >> 1730=item B<< C<Pm = 3> >>
1531 1731
1532=begin table 1732=begin table
1533 1733
1534 B<< C<h> >> 132 Column Mode (DECCOLM) 1734 B<< C<h> >> 132 Column Mode (DECCOLM)
1535 B<< C<l> >> 80 Column Mode (DECCOLM) 1735 B<< C<l> >> 80 Column Mode (DECCOLM)
1536 1736
1537=end table 1737=end table
1538 1738
1539=item B<< C<Ps = 4> >> 1739=item B<< C<Pm = 4> >>
1540 1740
1541=begin table 1741=begin table
1542 1742
1543 B<< C<h> >> Smooth (Slow) Scroll (DECSCLM) 1743 B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)
1544 B<< C<l> >> Jump (Fast) Scroll (DECSCLM) 1744 B<< C<l> >> Jump (Fast) Scroll (DECSCLM)
1545 1745
1546=end table 1746=end table
1547 1747
1548=item B<< C<Ps = 5> >> 1748=item B<< C<Pm = 5> >>
1549 1749
1550=begin table 1750=begin table
1551 1751
1552 B<< C<h> >> Reverse Video (DECSCNM) 1752 B<< C<h> >> Reverse Video (DECSCNM)
1553 B<< C<l> >> Normal Video (DECSCNM) 1753 B<< C<l> >> Normal Video (DECSCNM)
1554 1754
1555=end table 1755=end table
1556 1756
1557=item B<< C<Ps = 6> >> 1757=item B<< C<Pm = 6> >>
1558 1758
1559=begin table 1759=begin table
1560 1760
1561 B<< C<h> >> Origin Mode (DECOM) 1761 B<< C<h> >> Origin Mode (DECOM)
1562 B<< C<l> >> Normal Cursor Mode (DECOM) 1762 B<< C<l> >> Normal Cursor Mode (DECOM)
1563 1763
1564=end table 1764=end table
1565 1765
1566=item B<< C<Ps = 7> >> 1766=item B<< C<Pm = 7> >>
1567 1767
1568=begin table 1768=begin table
1569 1769
1570 B<< C<h> >> Wraparound Mode (DECAWM) 1770 B<< C<h> >> Wraparound Mode (DECAWM)
1571 B<< C<l> >> No Wraparound Mode (DECAWM) 1771 B<< C<l> >> No Wraparound Mode (DECAWM)
1572 1772
1573=end table 1773=end table
1574 1774
1575=item B<< C<Ps = 8> >> I<unimplemented> 1775=item B<< C<Pm = 8> >> I<unimplemented>
1576 1776
1577=begin table 1777=begin table
1578 1778
1579 B<< C<h> >> Auto-repeat Keys (DECARM) 1779 B<< C<h> >> Auto-repeat Keys (DECARM)
1580 B<< C<l> >> No Auto-repeat Keys (DECARM) 1780 B<< C<l> >> No Auto-repeat Keys (DECARM)
1581 1781
1582=end table 1782=end table
1583 1783
1584=item B<< C<Ps = 9> >> X10 XTerm 1784=item B<< C<Pm = 9> >> X10 XTerm
1585 1785
1586=begin table 1786=begin table
1587 1787
1588 B<< C<h> >> Send Mouse X & Y on button press. 1788 B<< C<h> >> Send Mouse X & Y on button press.
1589 B<< C<l> >> No mouse reporting. 1789 B<< C<l> >> No mouse reporting.
1590 1790
1591=end table 1791=end table
1592 1792
1593=item B<< C<Ps = 25> >> 1793=item B<< C<Pm = 25> >>
1594 1794
1595=begin table 1795=begin table
1596 1796
1597 B<< C<h> >> Visible cursor {cnorm/cvvis} 1797 B<< C<h> >> Visible cursor {cnorm/cvvis}
1598 B<< C<l> >> Invisible cursor {civis} 1798 B<< C<l> >> Invisible cursor {civis}
1599 1799
1600=end table 1800=end table
1601 1801
1602=item B<< C<Ps = 30> >> 1802=item B<< C<Pm = 30> >>
1603 1803
1604=begin table 1804=begin table
1605 1805
1606 B<< C<h> >> scrollBar visisble 1806 B<< C<h> >> scrollBar visisble
1607 B<< C<l> >> scrollBar invisisble 1807 B<< C<l> >> scrollBar invisisble
1608 1808
1609=end table 1809=end table
1610 1810
1611=item B<< C<Ps = 35> >> (B<rxvt>) 1811=item B<< C<Pm = 35> >> (B<rxvt>)
1612 1812
1613=begin table 1813=begin table
1614 1814
1615 B<< C<h> >> Allow XTerm Shift+key sequences 1815 B<< C<h> >> Allow XTerm Shift+key sequences
1616 B<< C<l> >> Disallow XTerm Shift+key sequences 1816 B<< C<l> >> Disallow XTerm Shift+key sequences
1617 1817
1618=end table 1818=end table
1619 1819
1620=item B<< C<Ps = 38> >> I<unimplemented> 1820=item B<< C<Pm = 38> >> I<unimplemented>
1621 1821
1622Enter Tektronix Mode (DECTEK) 1822Enter Tektronix Mode (DECTEK)
1623 1823
1624=item B<< C<Ps = 40> >> 1824=item B<< C<Pm = 40> >>
1625 1825
1626=begin table 1826=begin table
1627 1827
1628 B<< C<h> >> Allow 80/132 Mode 1828 B<< C<h> >> Allow 80/132 Mode
1629 B<< C<l> >> Disallow 80/132 Mode 1829 B<< C<l> >> Disallow 80/132 Mode
1630 1830
1631=end table 1831=end table
1632 1832
1633=item B<< C<Ps = 44> >> I<unimplemented> 1833=item B<< C<Pm = 44> >> I<unimplemented>
1634 1834
1635=begin table 1835=begin table
1636 1836
1637 B<< C<h> >> Turn On Margin Bell 1837 B<< C<h> >> Turn On Margin Bell
1638 B<< C<l> >> Turn Off Margin Bell 1838 B<< C<l> >> Turn Off Margin Bell
1639 1839
1640=end table 1840=end table
1641 1841
1642=item B<< C<Ps = 45> >> I<unimplemented> 1842=item B<< C<Pm = 45> >> I<unimplemented>
1643 1843
1644=begin table 1844=begin table
1645 1845
1646 B<< C<h> >> Reverse-wraparound Mode 1846 B<< C<h> >> Reverse-wraparound Mode
1647 B<< C<l> >> No Reverse-wraparound Mode 1847 B<< C<l> >> No Reverse-wraparound Mode
1648 1848
1649=end table 1849=end table
1650 1850
1651=item B<< C<Ps = 46> >> I<unimplemented> 1851=item B<< C<Pm = 46> >> I<unimplemented>
1652 1852
1653=item B<< C<Ps = 47> >> 1853=item B<< C<Pm = 47> >>
1654 1854
1655=begin table 1855=begin table
1656 1856
1657 B<< C<h> >> Use Alternate Screen Buffer 1857 B<< C<h> >> Use Alternate Screen Buffer
1658 B<< C<l> >> Use Normal Screen Buffer 1858 B<< C<l> >> Use Normal Screen Buffer
1659 1859
1660=end table 1860=end table
1661 1861
1662X<Priv66> 1862X<Priv66>
1663 1863
1664=item B<< C<Ps = 66> >> 1864=item B<< C<Pm = 66> >>
1665 1865
1666=begin table 1866=begin table
1667 1867
1668 B<< C<h> >> Application Keypad (DECPAM) == C<ESC => 1868 B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>
1669 B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >> 1869 B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>
1670 1870
1671=end table 1871=end table
1672 1872
1673=item B<< C<Ps = 67> >> 1873=item B<< C<Pm = 67> >>
1674 1874
1675=begin table 1875=begin table
1676 1876
1677 B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >> 1877 B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>
1678 B<< C<l> >> Backspace key sends B<< C<DEL> >> 1878 B<< C<l> >> Backspace key sends B<< C<DEL> >>
1679 1879
1680=end table 1880=end table
1681 1881
1682=item B<< C<Ps = 1000> >> (X11 XTerm) 1882=item B<< C<Pm = 1000> >> (X11 XTerm)
1683 1883
1684=begin table 1884=begin table
1685 1885
1686 B<< C<h> >> Send Mouse X & Y on button press and release. 1886 B<< C<h> >> Send Mouse X & Y on button press and release.
1687 B<< C<l> >> No mouse reporting. 1887 B<< C<l> >> No mouse reporting.
1688 1888
1689=end table 1889=end table
1690 1890
1691=item B<< C<Ps = 1001> >> (X11 XTerm) I<unimplemented> 1891=item B<< C<Pm = 1001> >> (X11 XTerm) I<unimplemented>
1692 1892
1693=begin table 1893=begin table
1694 1894
1695 B<< C<h> >> Use Hilite Mouse Tracking. 1895 B<< C<h> >> Use Hilite Mouse Tracking.
1696 B<< C<l> >> No mouse reporting. 1896 B<< C<l> >> No mouse reporting.
1697 1897
1698=end table 1898=end table
1699 1899
1700=item B<< C<Ps = 1010> >> (B<rxvt>) 1900=item B<< C<Pm = 1010> >> (B<rxvt>)
1701 1901
1702=begin table 1902=begin table
1703 1903
1704 B<< C<h> >> Don't scroll to bottom on TTY output 1904 B<< C<h> >> Don't scroll to bottom on TTY output
1705 B<< C<l> >> Scroll to bottom on TTY output 1905 B<< C<l> >> Scroll to bottom on TTY output
1706 1906
1707=end table 1907=end table
1708 1908
1709=item B<< C<Ps = 1011> >> (B<rxvt>) 1909=item B<< C<Pm = 1011> >> (B<rxvt>)
1710 1910
1711=begin table 1911=begin table
1712 1912
1713 B<< C<h> >> Scroll to bottom when a key is pressed 1913 B<< C<h> >> Scroll to bottom when a key is pressed
1714 B<< C<l> >> Don't scroll to bottom when a key is pressed 1914 B<< C<l> >> Don't scroll to bottom when a key is pressed
1715 1915
1716=end table 1916=end table
1717 1917
1718=item B<< C<Ps = 1021> >> (B<rxvt>) 1918=item B<< C<Pm = 1021> >> (B<rxvt>)
1719 1919
1720=begin table 1920=begin table
1721 1921
1722 B<< C<h> >> Bold/italic implies high intensity (see option B<-is>) 1922 B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
1723 B<< C<l> >> Font styles have no effect on intensity (Compile styles) 1923 B<< C<l> >> Font styles have no effect on intensity (Compile styles)
1724 1924
1725=end table 1925=end table
1726 1926
1727=item B<< C<Ps = 1047> >> 1927=item B<< C<Pm = 1047> >>
1728 1928
1729=begin table 1929=begin table
1730 1930
1731 B<< C<h> >> Use Alternate Screen Buffer 1931 B<< C<h> >> Use Alternate Screen Buffer
1732 B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it 1932 B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it
1733 1933
1734=end table 1934=end table
1735 1935
1736=item B<< C<Ps = 1048> >> 1936=item B<< C<Pm = 1048> >>
1737 1937
1738=begin table 1938=begin table
1739 1939
1740 B<< C<h> >> Save cursor position 1940 B<< C<h> >> Save cursor position
1741 B<< C<l> >> Restore cursor position 1941 B<< C<l> >> Restore cursor position
1742 1942
1743=end table 1943=end table
1744 1944
1745=item B<< C<Ps = 1049> >> 1945=item B<< C<Pm = 1049> >>
1746 1946
1747=begin table 1947=begin table
1748 1948
1749 B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it 1949 B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
1750 B<< C<l> >> Use Normal Screen Buffer 1950 B<< C<l> >> Use Normal Screen Buffer
… …
1755 1955
1756=back 1956=back
1757 1957
1758X<XTerm> 1958X<XTerm>
1759 1959
1760=head1 XTerm Operating System Commands 1960=head2 XTerm Operating System Commands
1761 1961
1762=over 4 1962=over 4
1763 1963
1764=item B<< C<ESC ] Ps;Pt ST> >> 1964=item B<< C<ESC ] Ps;Pt ST> >>
1765 1965
… …
1803 2003
1804=end table 2004=end table
1805 2005
1806=back 2006=back
1807 2007
1808X<XPM>
1809
1810=head1 XPM 2008=head1 XPM
1811 2009
1812For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value 2010For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
1813of B<< C<Pt> >> can be the name of the background pixmap followed by a 2011of B<< C<Pt> >> can be the name of the background pixmap followed by a
1814sequence of scaling/positioning commands separated by semi-colons. The 2012sequence of scaling/positioning commands separated by semi-colons. The
… …
1911=begin table 2109=begin table
1912 2110
1913 4 Shift 2111 4 Shift
1914 8 Meta 2112 8 Meta
1915 16 Control 2113 16 Control
1916 32 Double Click I<(Rxvt extension)> 2114 32 Double Click I<(rxvt extension)>
1917 2115
1918=end table 2116=end table
1919 2117
1920Col = B<< C<< <x> - SPACE >> >> 2118Col = B<< C<< <x> - SPACE >> >>
1921 2119
… …
2205 cursor blinking and underline cursor (-cb, -uc) 2403 cursor blinking and underline cursor (-cb, -uc)
2206 XEmbed support (-embed) 2404 XEmbed support (-embed)
2207 user-pty (-pty-fd) 2405 user-pty (-pty-fd)
2208 hold on exit (-hold) 2406 hold on exit (-hold)
2209 skip builtin block graphics (-sbg) 2407 skip builtin block graphics (-sbg)
2408 separate highlightcolor support (-hc)
2210 2409
2211It also enabled some non-essential features otherwise disabled, such as: 2410It also enables some non-essential features otherwise disabled, such as:
2212 2411
2213 some round-trip time optimisations 2412 some round-trip time optimisations
2214 nearest color allocation on pseudocolor screens 2413 nearest color allocation on pseudocolor screens
2215 UTF8_STRING supporr for selection 2414 UTF8_STRING supporr for selection
2216 sgr modes 90..97 and 100..107 2415 sgr modes 90..97 and 100..107
… …
2249Remove support for mouse selection style like that of xterm. 2448Remove support for mouse selection style like that of xterm.
2250 2449
2251=item --enable-dmalloc (default: off) 2450=item --enable-dmalloc (default: off)
2252 2451
2253Use Gray Watson's malloc - which is good for debugging See 2452Use Gray Watson's malloc - which is good for debugging See
2254http://www.letters.com/dmalloc/ for details If you use either this or the 2453L<http://www.letters.com/dmalloc/> for details If you use either this or the
2255next option, you may need to edit src/Makefile after compiling to point 2454next option, you may need to edit src/Makefile after compiling to point
2256DINCLUDE and DLIB to the right places. 2455DINCLUDE and DLIB to the right places.
2257 2456
2258You can only use either this option and the following (should 2457You can only use either this option and the following (should
2259you use either) . 2458you use either) .

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines