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.108 by root, Tue Jan 31 21:04:56 2006 UTC vs.
Revision 1.123 by root, Sat Dec 16 03:48:49 2006 UTC

… …
17 17
18This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting 18This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
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/rxvt-unicode/doc/rxvt.7.html>.
23 23
24=head1 RXVT-UNICODE/URXVT 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
… …
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
80The original rxvt and rxvt-unicode always export the variable "COLORTERM", 97The original rxvt and rxvt-unicode always export the variable "COLORTERM",
81so you can check and see if that is set. Note that several programs, JED, 98so you can check and see if that is set. Note that several programs, JED,
82slrn, Midnight Commander automatically check this variable to decide 99slrn, Midnight Commander automatically check this variable to decide
83whether or not to use color. 100whether or not to use color.
… …
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 I<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.
… …
409 URxvt.color6: #73f7ff 401 URxvt.color6: #73f7ff
410 URxvt.color14: #73f7ff 402 URxvt.color14: #73f7ff
411 URxvt.color7: #e1dddd 403 URxvt.color7: #e1dddd
412 URxvt.color15: #e1dddd 404 URxvt.color15: #e1dddd
413 405
414(They were described (not by me) as "pretty girly"). 406They have been described (not by me) as "pretty girly".
407
408=head3 Why do some characters look so much different than others?
409
410See next entry.
415 411
416=head3 How does rxvt-unicode choose fonts? 412=head3 How does rxvt-unicode choose fonts?
417 413
418Most fonts do not contain the full range of Unicode, which is 414Most fonts do not contain the full range of Unicode, which is
419fine. 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
420your 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
421to display. 417to display.
422 418
423B<rxvt-unicode> makes a best-effort try at finding a replacement 419B<rxvt-unicode> makes a best-effort try at finding a replacement
424font. Often the result is fine, but sometimes the chosen font looks 420font. Often the result is fine, but sometimes the chosen font looks
425bad/ugly/wrong. Some fonts have totally strange characters that don't 421bad/ugly/wrong. Some fonts have totally strange characters that don't
426resemble the correct glyph at all, and rxvt-unicode lacks the artificial 422resemble the correct glyph at all, and rxvt-unicode lacks the artificial
427intelligence 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
428the font that the characters it claims to contain indeed look correct. 424the font that the characters it claims to contain indeed look correct.
429 425
430In 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,
431e.g.: 427e.g.:
432 428
433 @@URXVT_NAME@@ -fn basefont,font2,font3... 429 @@URXVT_NAME@@ -fn basefont,font2,font3...
434 430
435When 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
436font. 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
437next 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
438search and use less resources within rxvt-unicode and the X-server. 434search and use less resources within rxvt-unicode and the X-server.
439 435
440The 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
441font, as the base font defines the terminal character cell size, which 437font, as the base font defines the terminal character cell size, which
442must be the same due to the way terminals work. 438must be the same due to the way terminals work.
443 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).
444 464
445=head2 Keyboard, Mouse & User Interaction 465=head2 Keyboard, Mouse & User Interaction
446 466
447=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?
448 468
… …
492circumstances, it will move your cursor around when you click into the 512circumstances, it will move your cursor around when you click into the
493line 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,
494but 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
495cases during rlogin sessions, it fails to detect this properly. 515cases during rlogin sessions, it fails to detect this properly.
496 516
497You can permamently switch this feature off by disabling the C<readline> 517You can permanently switch this feature off by disabling the C<readline>
498extension: 518extension:
499 519
500 URxvt.perl-ext-common: default,-readline 520 URxvt.perl-ext-common: default,-readline
501 521
502=head3 My numerical keypad acts weird and generates differing output? 522=head3 My numerical keypad acts weird and generates differing output?
503 523
504Some Debian GNUL/Linux users seem to have this problem, although no 524Some Debian GNUL/Linux users seem to have this problem, although no
505specific 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
506by 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
507this 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
508keymap. 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
509helped. 529helped.
510 530
511=head3 My Compose (Multi_key) key is no longer working. 531=head3 My Compose (Multi_key) key is no longer working.
… …
537depressed. 557depressed.
538 558
539=head3 What's with the strange Backspace/Delete key behaviour? 559=head3 What's with the strange Backspace/Delete key behaviour?
540 560
541Assuming that the physical Backspace key corresponds to the 561Assuming that the physical Backspace key corresponds to the
542BackSpace keysym (not likely for Linux ... see the following 562Backspace keysym (not likely for Linux ... see the following
543question) there are two standard values that can be used for 563question) there are two standard values that can be used for
544Backspace: C<^H> and C<^?>. 564Backspace: C<^H> and C<^?>.
545 565
546Historically, either value is correct, but rxvt-unicode adopts the debian 566Historically, either value is correct, but rxvt-unicode adopts the debian
547policy 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
… …
638 658
639 659
640 660
641=head2 Terminal Configuration 661=head2 Terminal Configuration
642 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
643=head3 Why doesn't rxvt-unicode read my resources? 817=head3 Why doesn't rxvt-unicode read my resources?
644 818
645Well, 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
646applications. Most importantly, this means that if you or your OS loads 820applications. Most importantly, this means that if you or your OS loads
647resources 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
… …
655Also consider the form resources have to use: 829Also consider the form resources have to use:
656 830
657 URxvt.resource: value 831 URxvt.resource: value
658 832
659If 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
660specifying resources), make sure you understand wether and why it 834specifying resources), make sure you understand whether and why it
661works. If unsure, use the form above. 835works. If unsure, use the form above.
662 836
663=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?
664 838
665The terminal description used by rxvt-unicode is not as widely available 839The terminal description used by rxvt-unicode is not as widely available
666as that for xterm, or even rxvt (for which the same problem often arises). 840as that for xterm, or even rxvt (for which the same problem often arises).
667 841
668The correct solution for this problem is to install the terminfo, this can 842The correct solution for this problem is to install the terminfo, this can
669be done like this (with ncurses' infocmp): 843be done like this (with ncurses' infocmp and works as user and admin):
670 844
671 REMOTE=remotesystem.domain 845 REMOTE=remotesystem.domain
672 infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" 846 infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
673 847
674... or by installing rxvt-unicode normally on the remote system, 848... or by installing rxvt-unicode normally on the remote system,
849
850One some systems you might need to set C<$TERMINFO> to the full path of
851F<$HOME/.terminfo> for this to work.
675 852
676If you cannot or do not want to do this, then you can simply set 853If you cannot or do not want to do this, then you can simply set
677C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of 854C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
678problems arising, which includes wrong keymapping, less and different 855problems arising, which includes wrong keymapping, less and different
679colours and some refresh errors in fullscreen applications. It's a nice 856colours and some refresh errors in fullscreen applications. It's a nice
… …
702One reason you might want this is that some distributions or operating 879One reason you might want this is that some distributions or operating
703systems still compile some programs using the long-obsoleted termcap 880systems still compile some programs using the long-obsoleted termcap
704library (Fedora Core's bash is one example) and rely on a termcap entry 881library (Fedora Core's bash is one example) and rely on a termcap entry
705for C<rxvt-unicode>. 882for C<rxvt-unicode>.
706 883
707You could use rxvt's termcap entry with resonable results in many cases. 884You could use rxvt's termcap entry with reasonable results in many cases.
708You can also create a termcap entry by using terminfo's infocmp program 885You can also create a termcap entry by using terminfo's infocmp program
709like this: 886like this:
710 887
711 infocmp -C rxvt-unicode 888 infocmp -C rxvt-unicode
712 889
… …
734 :vs=\E[?25h: 911 :vs=\E[?25h:
735 912
736=head3 Why does C<ls> no longer have coloured output? 913=head3 Why does C<ls> no longer have coloured output?
737 914
738The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to 915The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
739decide wether a terminal has colour, but uses it's own configuration 916decide whether a terminal has colour, but uses its own configuration
740file. Needless to say, C<rxvt-unicode> is not in it's default file (among 917file. Needless to say, C<rxvt-unicode> is not in its default file (among
741with most other terminals supporting colour). Either add: 918with most other terminals supporting colour). Either add:
742 919
743 TERM rxvt-unicode 920 TERM rxvt-unicode
744 921
745to C</etc/DIR_COLORS> or simply add: 922to C</etc/DIR_COLORS> or simply add:
… …
786something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work. 963something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work.
787 964
788The best thing is to fix your startup environment, as you will likely run 965The best thing is to fix your startup environment, as you will likely run
789into other problems. If nothing works you can try this in your .profile. 966into other problems. If nothing works you can try this in your .profile.
790 967
791 printf '\e]701;%s\007' "$LC_CTYPE" 968 printf '\33]701;%s\007' "$LC_CTYPE"
792 969
793If this doesn't work, then maybe you use a C<LC_CTYPE> specification not 970If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
794supported on your systems. Some systems have a C<locale> command which 971supported on your systems. Some systems have a C<locale> command which
795displays this (also, C<perl -e0> can be used to check locale settings, as 972displays this (also, C<perl -e0> can be used to check locale settings, as
796it will complain loudly if it cannot set the locale). If it displays something 973it will complain loudly if it cannot set the locale). If it displays something
… …
817The reasons is that there exists a perfectly fine mechanism for selecting 994The reasons is that there exists a perfectly fine mechanism for selecting
818the encoding, doing I/O and (most important) communicating this to all 995the encoding, doing I/O and (most important) communicating this to all
819applications so everybody agrees on character properties such as width 996applications so everybody agrees on character properties such as width
820and code number. This mechanism is the I<locale>. Applications not using 997and code number. This mechanism is the I<locale>. Applications not using
821that info will have problems (for example, C<xterm> gets the width of 998that info will have problems (for example, C<xterm> gets the width of
822characters wrong as it uses it's own, locale-independent table under all 999characters wrong as it uses its own, locale-independent table under all
823locales). 1000locales).
824 1001
825Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All 1002Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
826programs doing the same (that is, most) will automatically agree in the 1003programs doing the same (that is, most) will automatically agree in the
827interpretation of characters. 1004interpretation of characters.
… …
846=head3 Can I switch locales at runtime? 1023=head3 Can I switch locales at runtime?
847 1024
848Yes, using an escape sequence. Try something like this, which sets 1025Yes, using an escape sequence. Try something like this, which sets
849rxvt-unicode's idea of C<LC_CTYPE>. 1026rxvt-unicode's idea of C<LC_CTYPE>.
850 1027
851 printf '\e]701;%s\007' ja_JP.SJIS 1028 printf '\33]701;%s\007' ja_JP.SJIS
852 1029
853See also the previous answer. 1030See also the previous answer.
854 1031
855Sometimes this capability is rather handy when you want to work in 1032Sometimes this capability is rather handy when you want to work in
856one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it 1033one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it
857(e.g. UTF-8). For example, I use this script to start C<xjdic>, which 1034(e.g. UTF-8). For example, I use this script to start C<xjdic>, which
858first switches to a locale supported by xjdic and back later: 1035first switches to a locale supported by xjdic and back later:
859 1036
860 printf '\e]701;%s\007' ja_JP.SJIS 1037 printf '\33]701;%s\007' ja_JP.SJIS
861 xjdic -js 1038 xjdic -js
862 printf '\e]701;%s\007' de_DE.UTF-8 1039 printf '\33]701;%s\007' de_DE.UTF-8
863 1040
864You can also use xterm's C<luit> program, which usually works fine, except 1041You can also use xterm's C<luit> program, which usually works fine, except
865for some locales where character width differs between program- and 1042for some locales where character width differs between program- and
866rxvt-unicode-locales. 1043rxvt-unicode-locales.
867 1044
1045=head3 I have problems getting my input method working.
1046
1047Try a search engine, as this is slightly different for every input method server.
1048
1049Here is a checklist:
1050
1051=over 4
1052
1053=item - Make sure your locale I<and> the imLocale are supported on your OS.
1054
1055Try C<locale -a> or check the documentation for your OS.
1056
1057=item - Make sure your locale or imLocale matches a locale supported by your XIM.
1058
1059For example, B<kinput2> does not support UTF-8 locales, you should use
1060C<ja_JP.EUC-JP> or equivalent.
1061
1062=item - Make sure your XIM server is actually running.
1063
1064=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
1065
1066When you want to use e.g. B<kinput2>, it must be set to
1067C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. You can see what input
1068method servers are running with this command:
1069
1070 xprop -root XIM_SERVERS
1071
1072=item
1073
1074=back
1075
868=head3 My input method wants <some encoding> but I want UTF-8, what can I do? 1076=head3 My input method wants <some encoding> but I want UTF-8, what can I do?
869 1077
870You can specify separate locales for the input method and the rest of the 1078You can specify separate locales for the input method and the rest of the
871terminal, using the resource C<imlocale>: 1079terminal, using the resource C<imlocale>:
872 1080
873 URxvt.imlocale: ja_JP.EUC-JP 1081 URxvt.imlocale: ja_JP.EUC-JP
874 1082
875Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still 1083Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
876use your input method. Please note, however, that you will not be able to 1084use your input method. Please note, however, that, depending on your Xlib
877input characters outside C<EUC-JP> in a normal way then, as your input 1085version, you may not be able to input characters outside C<EUC-JP> in a
878method limits you. 1086normal way then, as your input method limits you.
879 1087
880=head3 Rxvt-unicode crashes when the X Input Method changes or exits. 1088=head3 Rxvt-unicode crashes when the X Input Method changes or exits.
881 1089
882Unfortunately, this is unavoidable, as the XIM protocol is racy by 1090Unfortunately, this is unavoidable, as the XIM protocol is racy by
883design. Applications can avoid some crashes at the expense of memory 1091design. Applications can avoid some crashes at the expense of memory
… …
909 1117
910=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? 1118=head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
911 1119
912You should build one binary with the default options. F<configure> 1120You should build one binary with the default options. F<configure>
913now enables most useful options, and the trend goes to making them 1121now enables most useful options, and the trend goes to making them
914runtime-switchable, too, so there is usually no drawback to enbaling them, 1122runtime-switchable, too, so there is usually no drawback to enabling them,
915except higher disk and possibly memory usage. The perl interpreter should 1123except higher disk and possibly memory usage. The perl interpreter should
916be enabled, as important functionality (menus, selection, likely more in 1124be enabled, as important functionality (menus, selection, likely more in
917the future) depends on it. 1125the future) depends on it.
918 1126
919You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources 1127You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources
… …
954 1162
955=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all. 1163=head3 I am on FreeBSD and rxvt-unicode does not seem to work at all.
956 1164
957Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined 1165Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
958in your compile environment, or an implementation that implements it, 1166in your compile environment, or an implementation that implements it,
959wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that 1167whether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
960B<wchar_t> is represented as unicode. 1168B<wchar_t> is represented as unicode.
961 1169
962As you might have guessed, FreeBSD does neither define this symobl nor 1170As you might have guessed, FreeBSD does neither define this symbol nor
963does it support it. Instead, it uses it's own internal representation of 1171does it support it. Instead, it uses its own internal representation of
964B<wchar_t>. This is, of course, completely fine with respect to standards. 1172B<wchar_t>. This is, of course, completely fine with respect to standards.
965 1173
966However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and 1174However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and
967C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>. 1175C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>.
968 1176
… …
1002encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited 1210encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
1003to 8-bit encodings. 1211to 8-bit encodings.
1004 1212
1005=head1 RXVT-UNICODE TECHNICAL REFERENCE 1213=head1 RXVT-UNICODE TECHNICAL REFERENCE
1006 1214
1007=head1 DESCRIPTION
1008
1009The rest of this document describes various technical aspects of 1215The rest of this document describes various technical aspects of
1010B<rxvt-unicode>. First the description of supported command sequences, 1216B<rxvt-unicode>. First the description of supported command sequences,
1011followed by pixmap support and last by a description of all features 1217followed by pixmap support and last by a description of all features
1012selectable at C<configure> time. 1218selectable at C<configure> time.
1013 1219
1014=head1 Definitions 1220=head2 Definitions
1015 1221
1016=over 4 1222=over 4
1017 1223
1018=item B<< C<c> >> 1224=item B<< C<c> >>
1019 1225
… …
1037 1243
1038A text parameter composed of printable characters. 1244A text parameter composed of printable characters.
1039 1245
1040=back 1246=back
1041 1247
1042=head1 Values 1248=head2 Values
1043 1249
1044=over 4 1250=over 4
1045 1251
1046=item B<< C<ENQ> >> 1252=item B<< C<ENQ> >>
1047 1253
… …
1090 1296
1091Space Character 1297Space Character
1092 1298
1093=back 1299=back
1094 1300
1095=head1 Escape Sequences 1301=head2 Escape Sequences
1096 1302
1097=over 4 1303=over 4
1098 1304
1099=item B<< C<ESC # 8> >> 1305=item B<< C<ESC # 8> >>
1100 1306
… …
1198 1404
1199=back 1405=back
1200 1406
1201X<CSI> 1407X<CSI>
1202 1408
1203=head1 CSI (Command Sequence Introducer) Sequences 1409=head2 CSI (Command Sequence Introducer) Sequences
1204 1410
1205=over 4 1411=over 4
1206 1412
1207=item B<< C<ESC [ Ps @> >> 1413=item B<< C<ESC [ Ps @> >>
1208 1414
… …
1478 1684
1479=back 1685=back
1480 1686
1481X<PrivateModes> 1687X<PrivateModes>
1482 1688
1483=head1 DEC Private Modes 1689=head2 DEC Private Modes
1484 1690
1485=over 4 1691=over 4
1486 1692
1487=item B<< C<ESC [ ? Pm h> >> 1693=item B<< C<ESC [ ? Pm h> >>
1488 1694
… …
1504 1710
1505Toggle DEC Private Mode Values (rxvt extension). I<where> 1711Toggle DEC Private Mode Values (rxvt extension). I<where>
1506 1712
1507=over 4 1713=over 4
1508 1714
1509=item B<< C<Ps = 1> >> (DECCKM) 1715=item B<< C<Pm = 1> >> (DECCKM)
1510 1716
1511=begin table 1717=begin table
1512 1718
1513 B<< C<h> >> Application Cursor Keys 1719 B<< C<h> >> Application Cursor Keys
1514 B<< C<l> >> Normal Cursor Keys 1720 B<< C<l> >> Normal Cursor Keys
1515 1721
1516=end table 1722=end table
1517 1723
1518=item B<< C<Ps = 2> >> (ANSI/VT52 mode) 1724=item B<< C<Pm = 2> >> (ANSI/VT52 mode)
1519 1725
1520=begin table 1726=begin table
1521 1727
1522 B<< C<h> >> Enter VT52 mode 1728 B<< C<h> >> Enter VT52 mode
1523 B<< C<l> >> Enter VT52 mode 1729 B<< C<l> >> Enter VT52 mode
1524 1730
1525=end table 1731=end table
1526 1732
1527=item B<< C<Ps = 3> >> 1733=item B<< C<Pm = 3> >>
1528 1734
1529=begin table 1735=begin table
1530 1736
1531 B<< C<h> >> 132 Column Mode (DECCOLM) 1737 B<< C<h> >> 132 Column Mode (DECCOLM)
1532 B<< C<l> >> 80 Column Mode (DECCOLM) 1738 B<< C<l> >> 80 Column Mode (DECCOLM)
1533 1739
1534=end table 1740=end table
1535 1741
1536=item B<< C<Ps = 4> >> 1742=item B<< C<Pm = 4> >>
1537 1743
1538=begin table 1744=begin table
1539 1745
1540 B<< C<h> >> Smooth (Slow) Scroll (DECSCLM) 1746 B<< C<h> >> Smooth (Slow) Scroll (DECSCLM)
1541 B<< C<l> >> Jump (Fast) Scroll (DECSCLM) 1747 B<< C<l> >> Jump (Fast) Scroll (DECSCLM)
1542 1748
1543=end table 1749=end table
1544 1750
1545=item B<< C<Ps = 5> >> 1751=item B<< C<Pm = 5> >>
1546 1752
1547=begin table 1753=begin table
1548 1754
1549 B<< C<h> >> Reverse Video (DECSCNM) 1755 B<< C<h> >> Reverse Video (DECSCNM)
1550 B<< C<l> >> Normal Video (DECSCNM) 1756 B<< C<l> >> Normal Video (DECSCNM)
1551 1757
1552=end table 1758=end table
1553 1759
1554=item B<< C<Ps = 6> >> 1760=item B<< C<Pm = 6> >>
1555 1761
1556=begin table 1762=begin table
1557 1763
1558 B<< C<h> >> Origin Mode (DECOM) 1764 B<< C<h> >> Origin Mode (DECOM)
1559 B<< C<l> >> Normal Cursor Mode (DECOM) 1765 B<< C<l> >> Normal Cursor Mode (DECOM)
1560 1766
1561=end table 1767=end table
1562 1768
1563=item B<< C<Ps = 7> >> 1769=item B<< C<Pm = 7> >>
1564 1770
1565=begin table 1771=begin table
1566 1772
1567 B<< C<h> >> Wraparound Mode (DECAWM) 1773 B<< C<h> >> Wraparound Mode (DECAWM)
1568 B<< C<l> >> No Wraparound Mode (DECAWM) 1774 B<< C<l> >> No Wraparound Mode (DECAWM)
1569 1775
1570=end table 1776=end table
1571 1777
1572=item B<< C<Ps = 8> >> I<unimplemented> 1778=item B<< C<Pm = 8> >> I<unimplemented>
1573 1779
1574=begin table 1780=begin table
1575 1781
1576 B<< C<h> >> Auto-repeat Keys (DECARM) 1782 B<< C<h> >> Auto-repeat Keys (DECARM)
1577 B<< C<l> >> No Auto-repeat Keys (DECARM) 1783 B<< C<l> >> No Auto-repeat Keys (DECARM)
1578 1784
1579=end table 1785=end table
1580 1786
1581=item B<< C<Ps = 9> >> X10 XTerm 1787=item B<< C<Pm = 9> >> X10 XTerm
1582 1788
1583=begin table 1789=begin table
1584 1790
1585 B<< C<h> >> Send Mouse X & Y on button press. 1791 B<< C<h> >> Send Mouse X & Y on button press.
1586 B<< C<l> >> No mouse reporting. 1792 B<< C<l> >> No mouse reporting.
1587 1793
1588=end table 1794=end table
1589 1795
1590=item B<< C<Ps = 25> >> 1796=item B<< C<Pm = 25> >>
1591 1797
1592=begin table 1798=begin table
1593 1799
1594 B<< C<h> >> Visible cursor {cnorm/cvvis} 1800 B<< C<h> >> Visible cursor {cnorm/cvvis}
1595 B<< C<l> >> Invisible cursor {civis} 1801 B<< C<l> >> Invisible cursor {civis}
1596 1802
1597=end table 1803=end table
1598 1804
1599=item B<< C<Ps = 30> >> 1805=item B<< C<Pm = 30> >>
1600 1806
1601=begin table 1807=begin table
1602 1808
1603 B<< C<h> >> scrollBar visisble 1809 B<< C<h> >> scrollBar visisble
1604 B<< C<l> >> scrollBar invisisble 1810 B<< C<l> >> scrollBar invisisble
1605 1811
1606=end table 1812=end table
1607 1813
1608=item B<< C<Ps = 35> >> (B<rxvt>) 1814=item B<< C<Pm = 35> >> (B<rxvt>)
1609 1815
1610=begin table 1816=begin table
1611 1817
1612 B<< C<h> >> Allow XTerm Shift+key sequences 1818 B<< C<h> >> Allow XTerm Shift+key sequences
1613 B<< C<l> >> Disallow XTerm Shift+key sequences 1819 B<< C<l> >> Disallow XTerm Shift+key sequences
1614 1820
1615=end table 1821=end table
1616 1822
1617=item B<< C<Ps = 38> >> I<unimplemented> 1823=item B<< C<Pm = 38> >> I<unimplemented>
1618 1824
1619Enter Tektronix Mode (DECTEK) 1825Enter Tektronix Mode (DECTEK)
1620 1826
1621=item B<< C<Ps = 40> >> 1827=item B<< C<Pm = 40> >>
1622 1828
1623=begin table 1829=begin table
1624 1830
1625 B<< C<h> >> Allow 80/132 Mode 1831 B<< C<h> >> Allow 80/132 Mode
1626 B<< C<l> >> Disallow 80/132 Mode 1832 B<< C<l> >> Disallow 80/132 Mode
1627 1833
1628=end table 1834=end table
1629 1835
1630=item B<< C<Ps = 44> >> I<unimplemented> 1836=item B<< C<Pm = 44> >> I<unimplemented>
1631 1837
1632=begin table 1838=begin table
1633 1839
1634 B<< C<h> >> Turn On Margin Bell 1840 B<< C<h> >> Turn On Margin Bell
1635 B<< C<l> >> Turn Off Margin Bell 1841 B<< C<l> >> Turn Off Margin Bell
1636 1842
1637=end table 1843=end table
1638 1844
1639=item B<< C<Ps = 45> >> I<unimplemented> 1845=item B<< C<Pm = 45> >> I<unimplemented>
1640 1846
1641=begin table 1847=begin table
1642 1848
1643 B<< C<h> >> Reverse-wraparound Mode 1849 B<< C<h> >> Reverse-wraparound Mode
1644 B<< C<l> >> No Reverse-wraparound Mode 1850 B<< C<l> >> No Reverse-wraparound Mode
1645 1851
1646=end table 1852=end table
1647 1853
1648=item B<< C<Ps = 46> >> I<unimplemented> 1854=item B<< C<Pm = 46> >> I<unimplemented>
1649 1855
1650=item B<< C<Ps = 47> >> 1856=item B<< C<Pm = 47> >>
1651 1857
1652=begin table 1858=begin table
1653 1859
1654 B<< C<h> >> Use Alternate Screen Buffer 1860 B<< C<h> >> Use Alternate Screen Buffer
1655 B<< C<l> >> Use Normal Screen Buffer 1861 B<< C<l> >> Use Normal Screen Buffer
1656 1862
1657=end table 1863=end table
1658 1864
1659X<Priv66> 1865X<Priv66>
1660 1866
1661=item B<< C<Ps = 66> >> 1867=item B<< C<Pm = 66> >>
1662 1868
1663=begin table 1869=begin table
1664 1870
1665 B<< C<h> >> Application Keypad (DECPAM) == C<ESC => 1871 B<< C<h> >> Application Keypad (DECPAM) == C<ESC =>
1666 B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >> 1872 B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >>
1667 1873
1668=end table 1874=end table
1669 1875
1670=item B<< C<Ps = 67> >> 1876=item B<< C<Pm = 67> >>
1671 1877
1672=begin table 1878=begin table
1673 1879
1674 B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >> 1880 B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >>
1675 B<< C<l> >> Backspace key sends B<< C<DEL> >> 1881 B<< C<l> >> Backspace key sends B<< C<DEL> >>
1676 1882
1677=end table 1883=end table
1678 1884
1679=item B<< C<Ps = 1000> >> (X11 XTerm) 1885=item B<< C<Pm = 1000> >> (X11 XTerm)
1680 1886
1681=begin table 1887=begin table
1682 1888
1683 B<< C<h> >> Send Mouse X & Y on button press and release. 1889 B<< C<h> >> Send Mouse X & Y on button press and release.
1684 B<< C<l> >> No mouse reporting. 1890 B<< C<l> >> No mouse reporting.
1685 1891
1686=end table 1892=end table
1687 1893
1688=item B<< C<Ps = 1001> >> (X11 XTerm) I<unimplemented> 1894=item B<< C<Pm = 1001> >> (X11 XTerm) I<unimplemented>
1689 1895
1690=begin table 1896=begin table
1691 1897
1692 B<< C<h> >> Use Hilite Mouse Tracking. 1898 B<< C<h> >> Use Hilite Mouse Tracking.
1693 B<< C<l> >> No mouse reporting. 1899 B<< C<l> >> No mouse reporting.
1694 1900
1695=end table 1901=end table
1696 1902
1697=item B<< C<Ps = 1010> >> (B<rxvt>) 1903=item B<< C<Pm = 1010> >> (B<rxvt>)
1698 1904
1699=begin table 1905=begin table
1700 1906
1701 B<< C<h> >> Don't scroll to bottom on TTY output 1907 B<< C<h> >> Don't scroll to bottom on TTY output
1702 B<< C<l> >> Scroll to bottom on TTY output 1908 B<< C<l> >> Scroll to bottom on TTY output
1703 1909
1704=end table 1910=end table
1705 1911
1706=item B<< C<Ps = 1011> >> (B<rxvt>) 1912=item B<< C<Pm = 1011> >> (B<rxvt>)
1707 1913
1708=begin table 1914=begin table
1709 1915
1710 B<< C<h> >> Scroll to bottom when a key is pressed 1916 B<< C<h> >> Scroll to bottom when a key is pressed
1711 B<< C<l> >> Don't scroll to bottom when a key is pressed 1917 B<< C<l> >> Don't scroll to bottom when a key is pressed
1712 1918
1713=end table 1919=end table
1714 1920
1715=item B<< C<Ps = 1021> >> (B<rxvt>) 1921=item B<< C<Pm = 1021> >> (B<rxvt>)
1716 1922
1717=begin table 1923=begin table
1718 1924
1719 B<< C<h> >> Bold/italic implies high intensity (see option B<-is>) 1925 B<< C<h> >> Bold/italic implies high intensity (see option B<-is>)
1720 B<< C<l> >> Font styles have no effect on intensity (Compile styles) 1926 B<< C<l> >> Font styles have no effect on intensity (Compile styles)
1721 1927
1722=end table 1928=end table
1723 1929
1724=item B<< C<Ps = 1047> >> 1930=item B<< C<Pm = 1047> >>
1725 1931
1726=begin table 1932=begin table
1727 1933
1728 B<< C<h> >> Use Alternate Screen Buffer 1934 B<< C<h> >> Use Alternate Screen Buffer
1729 B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it 1935 B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it
1730 1936
1731=end table 1937=end table
1732 1938
1733=item B<< C<Ps = 1048> >> 1939=item B<< C<Pm = 1048> >>
1734 1940
1735=begin table 1941=begin table
1736 1942
1737 B<< C<h> >> Save cursor position 1943 B<< C<h> >> Save cursor position
1738 B<< C<l> >> Restore cursor position 1944 B<< C<l> >> Restore cursor position
1739 1945
1740=end table 1946=end table
1741 1947
1742=item B<< C<Ps = 1049> >> 1948=item B<< C<Pm = 1049> >>
1743 1949
1744=begin table 1950=begin table
1745 1951
1746 B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it 1952 B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
1747 B<< C<l> >> Use Normal Screen Buffer 1953 B<< C<l> >> Use Normal Screen Buffer
… …
1752 1958
1753=back 1959=back
1754 1960
1755X<XTerm> 1961X<XTerm>
1756 1962
1757=head1 XTerm Operating System Commands 1963=head2 XTerm Operating System Commands
1758 1964
1759=over 4 1965=over 4
1760 1966
1761=item B<< C<ESC ] Ps;Pt ST> >> 1967=item B<< C<ESC ] Ps;Pt ST> >>
1762 1968
… …
1799 B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl). 2005 B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl).
1800 2006
1801=end table 2007=end table
1802 2008
1803=back 2009=back
1804
1805X<XPM>
1806 2010
1807=head1 XPM 2011=head1 XPM
1808 2012
1809For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value 2013For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value
1810of B<< C<Pt> >> can be the name of the background pixmap followed by a 2014of B<< C<Pt> >> can be the name of the background pixmap followed by a
… …
2202 cursor blinking and underline cursor (-cb, -uc) 2406 cursor blinking and underline cursor (-cb, -uc)
2203 XEmbed support (-embed) 2407 XEmbed support (-embed)
2204 user-pty (-pty-fd) 2408 user-pty (-pty-fd)
2205 hold on exit (-hold) 2409 hold on exit (-hold)
2206 skip builtin block graphics (-sbg) 2410 skip builtin block graphics (-sbg)
2411 separate highlightcolor support (-hc)
2207 2412
2208It also enabled some non-essential features otherwise disabled, such as: 2413It also enables some non-essential features otherwise disabled, such as:
2209 2414
2210 some round-trip time optimisations 2415 some round-trip time optimisations
2211 nearest color allocation on pseudocolor screens 2416 nearest color allocation on pseudocolor screens
2212 UTF8_STRING supporr for selection 2417 UTF8_STRING supporr for selection
2213 sgr modes 90..97 and 100..107 2418 sgr modes 90..97 and 100..107
… …
2246Remove support for mouse selection style like that of xterm. 2451Remove support for mouse selection style like that of xterm.
2247 2452
2248=item --enable-dmalloc (default: off) 2453=item --enable-dmalloc (default: off)
2249 2454
2250Use Gray Watson's malloc - which is good for debugging See 2455Use Gray Watson's malloc - which is good for debugging See
2251http://www.letters.com/dmalloc/ for details If you use either this or the 2456L<http://www.letters.com/dmalloc/> for details If you use either this or the
2252next option, you may need to edit src/Makefile after compiling to point 2457next option, you may need to edit src/Makefile after compiling to point
2253DINCLUDE and DLIB to the right places. 2458DINCLUDE and DLIB to the right places.
2254 2459
2255You can only use either this option and the following (should 2460You can only use either this option and the following (should
2256you use either) . 2461you use either) .

Diff Legend

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