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.102 by root, Tue Jan 31 20:50:48 2006 UTC vs.
Revision 1.115 by root, Tue Feb 21 01:01:33 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?
… …
36 36
37Beginning with version 7.3, there is a perl extension that implements a 37Beginning with version 7.3, there is a perl extension that implements a
38simple tabbed terminal. It is installed by default, so any of these should 38simple tabbed terminal. It is installed by default, so any of these should
39give you tabs: 39give you tabs:
40 40
41 @@RXVT_NAME@@ -pe tabbed 41 @@URXVT_NAME@@ -pe tabbed
42 42
43 URxvt.perl-ext-common: default,tabbed 43 URxvt.perl-ext-common: default,tabbed
44 44
45It will also work fine with tabbing functionality of many window managers 45It will also work fine with tabbing functionality of many window managers
46or similar tabbing programs, and its embedding-features allow it to be 46or similar tabbing programs, and its embedding-features allow it to be
… …
50 50
51=head3 How do I know which rxvt-unicode version I'm using? 51=head3 How do I know which rxvt-unicode version I'm using?
52 52
53The version number is displayed with the usage (-h). Also the escape 53The version number is displayed with the usage (-h). Also the escape
54sequence C<ESC [ 8 n> sets the window title to the version number. When 54sequence C<ESC [ 8 n> sets the window title to the version number. When
55using the @@RXVT_NAME@@c client, the version displayed is that of the 55using the @@URXVT_NAME@@c client, the version displayed is that of the
56daemon. 56daemon.
57 57
58=head3 Rxvt-unicode uses gobs of memory, how can I reduce that? 58=head3 Rxvt-unicode uses gobs of memory, how can I reduce that?
59 59
60Rxvt-unicode tries to obey the rule of not charging you for something you 60Rxvt-unicode tries to obey the rule of not charging you for something you
… …
686 bytes per screen cell. For a 160x?? window this amounts to almost a 686 bytes per screen cell. For a 160x?? window this amounts to almost a
69kilobyte per line. A scrollback buffer of 10000 lines will then (if full) 69kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
70use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as 70use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
71rxvt-unicode then uses 8 bytes per screen cell. 71rxvt-unicode then uses 8 bytes per screen cell.
72 72
73=head3 How can I start @@RXVT_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<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_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 wether 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 unreasnobaly 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
… …
203descriptions for the programs mentioned and rxvt-unicode. Really, do it! 220descriptions for the programs mentioned and rxvt-unicode. Really, do it!
204 221
2051. Use inheritPixmap: 2221. Use inheritPixmap:
206 223
207 Esetroot wallpaper.jpg 224 Esetroot wallpaper.jpg
208 @@RXVT_NAME@@ -ip -tint red -sh 40 225 @@URXVT_NAME@@ -ip -tint red -sh 40
209 226
210That works. If you think it doesn't, you lack transparency and tinting 227That works. If you think it doesn't, you lack transparency and tinting
211support, or you are unable to read. 228support, or you are unable to read.
212 229
2132. Use a simple pixmap and emulate pseudo-transparency. This enables you 2302. Use a simple pixmap and emulate pseudo-transparency. This enables you
214to use effects other than tinting and shading: Just shade/tint/whatever 231to use effects other than tinting and shading: Just shade/tint/whatever
215your picture with gimp or any other tool: 232your picture with gimp or any other tool:
216 233
217 convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm 234 convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
218 @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background 235 @@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
219 236
220That works. If you think it doesn't, you lack XPM and Perl support, or you 237That works. If you think it doesn't, you lack XPM and Perl support, or you
221are unable to read. 238are unable to read.
222 239
2233. Use an ARGB visual: 2403. Use an ARGB visual:
224 241
225 @@RXVT_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 neccessary
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
… …
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
… …
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 @@RXVT_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
… …
470B<perl-ext-common> resource to the empty string, which also keeps 487B<perl-ext-common> resource to the empty string, which also keeps
471rxvt-unicode from initialising perl, saving memory. 488rxvt-unicode from initialising perl, saving memory.
472 489
473If you only want to disable specific features, you first have to 490If you only want to disable specific features, you first have to
474identify which perl extension is responsible. For this, read the section 491identify which perl extension is responsible. For this, read the section
475B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For 492B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For
476example, to disable the B<selection-popup> and B<option-popup>, specify 493example, to disable the B<selection-popup> and B<option-popup>, specify
477this B<perl-ext-common> resource: 494this B<perl-ext-common> resource:
478 495
479 URxvt.perl-ext-common: default,-selection-popup,-option-popup 496 URxvt.perl-ext-common: default,-selection-popup,-option-popup
480 497
… …
558 575
559For starting a new rxvt-unicode: 576For starting a new rxvt-unicode:
560 577
561 # use Backspace = ^H 578 # use Backspace = ^H
562 $ stty erase ^H 579 $ stty erase ^H
563 $ @@RXVT_NAME@@ 580 $ @@URXVT_NAME@@
564 581
565 # use Backspace = ^? 582 # use Backspace = ^?
566 $ stty erase ^? 583 $ stty erase ^?
567 $ @@RXVT_NAME@@ 584 $ @@URXVT_NAME@@
568 585
569Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>. 586Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
570 587
571For an existing rxvt-unicode: 588For an existing rxvt-unicode:
572 589
… …
599 616
600There are some compile-time selections available via configure. Unless 617There are some compile-time selections available via configure. Unless
601you have run "configure" with the C<--disable-resources> option you can 618you have run "configure" with the C<--disable-resources> option you can
602use the `keysym' resource to alter the keystrings associated with keysyms. 619use the `keysym' resource to alter the keystrings associated with keysyms.
603 620
604Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt> 621Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt>
605 622
606 URxvt.keysym.Home: \033[1~ 623 URxvt.keysym.Home: \033[1~
607 URxvt.keysym.End: \033[4~ 624 URxvt.keysym.End: \033[4~
608 URxvt.keysym.C-apostrophe: \033<C-'> 625 URxvt.keysym.C-apostrophe: \033<C-'>
609 URxvt.keysym.C-slash: \033<C-/> 626 URxvt.keysym.C-slash: \033<C-/>
… …
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 pelr error mssages 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> confgiures urxvt to scroll in full-screen
707apps, like screen, so lines scorlled 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> mentioend 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. Whene ditign 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
… …
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.
698 869
699=head3 C<bash>'s readline does not work correctly under @@RXVT_NAME@@. 870=head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@.
700 871
701See next entry. 872See next entry.
702 873
703=head3 I need a termcap file entry. 874=head3 I need a termcap file entry.
704 875
… …
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>. Youc an 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
… …
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
… …
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
… …
2249Remove support for mouse selection style like that of xterm. 2447Remove support for mouse selection style like that of xterm.
2250 2448
2251=item --enable-dmalloc (default: off) 2449=item --enable-dmalloc (default: off)
2252 2450
2253Use Gray Watson's malloc - which is good for debugging See 2451Use Gray Watson's malloc - which is good for debugging See
2254http://www.letters.com/dmalloc/ for details If you use either this or the 2452L<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 2453next option, you may need to edit src/Makefile after compiling to point
2256DINCLUDE and DLIB to the right places. 2454DINCLUDE and DLIB to the right places.
2257 2455
2258You can only use either this option and the following (should 2456You can only use either this option and the following (should
2259you use either) . 2457you use either) .

Diff Legend

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