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

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.12 by root, Mon Aug 16 02:09:28 2004 UTC vs.
Revision 1.53 by root, Fri Feb 11 18:14:07 2005 UTC

11B<rxvt-unicode>, version B<@@RXVT_VERSION@@>, is a colour vt102 terminal 11B<rxvt-unicode>, version B<@@RXVT_VERSION@@>, is a colour vt102 terminal
12emulator intended as an I<xterm>(1) replacement for users who do not 12emulator intended as an I<xterm>(1) replacement for users who do not
13require features such as Tektronix 4014 emulation and toolkit-style 13require features such as Tektronix 4014 emulation and toolkit-style
14configurability. As a result, B<rxvt-unicode> uses much less swap space -- 14configurability. As a result, B<rxvt-unicode> uses much less swap space --
15a significant advantage on a machine serving many X sessions. 15a significant advantage on a machine serving many X sessions.
16
17=head1 FREQUENTLY ASKED QUESTIONS
18
19See @@RXVT_NAME@@(7) (try C<man 7 @@RXVT_NAME@@>) for a list of
20frequently asked questions and answer to them and some common
21problems. That document is also accessible on the World-Wide-Web at
22L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
16 23
17=head1 RXVT-UNICODE VS. RXVT 24=head1 RXVT-UNICODE VS. RXVT
18 25
19Unlike the original rxvt, B<rxvt-unicode> stores all text in Unicode 26Unlike the original rxvt, B<rxvt-unicode> stores all text in Unicode
20internally. That means it can store and display most scripts in the 27internally. That means it can store and display most scripts in the
24like tibetan or devenagari. Don't expect pretty output when using these 31like tibetan or devenagari. Don't expect pretty output when using these
25scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work 32scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work
26fine, though. A somewhat difficult case are left-to-right scripts, such 33fine, though. A somewhat difficult case are left-to-right scripts, such
27as hebrew: B<rxvt-unicode> adopts the view that bidirectional algorithms 34as hebrew: B<rxvt-unicode> adopts the view that bidirectional algorithms
28belong into the application, not the terminal emulator (too many things -- 35belong into the application, not the terminal emulator (too many things --
29such as cursor-movement while editing -- break othwerwise), but that might 36such as cursor-movement while editing -- break otherwise), but that might
30change. 37change.
31 38
32If you are looking for a terminal that supports more exotic scripts, let 39If you are looking for a terminal that supports more exotic scripts, let
33me recommend C<mlterm>, which is a very userfriendly, lean and clean 40me recommend C<mlterm>, which is a very userfriendly, lean and clean
34terminal emulator. In fact, the reason rxvt-unicode was born was solely 41terminal emulator. In fact, the reason rxvt-unicode was born was solely
53drastically reduces memory usage. See @@RXVT_NAME@@d(1) (daemon) and 60drastically reduces memory usage. See @@RXVT_NAME@@d(1) (daemon) and
54@@RXVT_NAME@@c(1) (client). 61@@RXVT_NAME@@c(1) (client).
55 62
56It also makes technical information about escape sequences (which have 63It also makes technical information about escape sequences (which have
57been extended) easier accessible: see @@RXVT_NAME@@(7) for technical 64been extended) easier accessible: see @@RXVT_NAME@@(7) for technical
58reference documentation (escape sequences etc.) and the FAQ section at the 65reference documentation (escape sequences etc.).
59end of this document.
60 66
61=head1 OPTIONS 67=head1 OPTIONS
62 68
63The B<@@RXVT_NAME@@> options (mostly a subset of I<xterm>'s) are listed 69The B<@@RXVT_NAME@@> options (mostly a subset of I<xterm>'s) are listed
64below. In keeping with the smaller-is-better philosophy, options may be 70below. In keeping with the smaller-is-better philosophy, options may be
106Turn on/off inheriting parent window's pixmap. Alternative form is 112Turn on/off inheriting parent window's pixmap. Alternative form is
107B<-tr>; resource B<inheritPixmap>. 113B<-tr>; resource B<inheritPixmap>.
108 114
109=item B<-fade> I<number> 115=item B<-fade> I<number>
110 116
111Fade the text by the given percentage when focus is lost. 117Fade the text by the given percentage when focus is lost. resource B<fading>.
112 118
113=item B<-tint> I<colour> 119=item B<-tint> I<colour>
114 120
115Tint the transparent background pixmap with the given colour when 121Tint the transparent background pixmap with the given colour when
116transparency is enabled with B<-tr> or B<-ip>. See also the B<-sh> 122transparency is enabled with B<-tr> or B<-ip>. See also the B<-sh>
119 125
120=item B<-sh> 126=item B<-sh>
121 127
122I<number> Darken (0 .. 100) or lighten (-1 .. -100) the transparent 128I<number> Darken (0 .. 100) or lighten (-1 .. -100) the transparent
123background image in addition to tinting it (i.e. B<-tint> must be 129background image in addition to tinting it (i.e. B<-tint> must be
124specified, too). 130specified, too, e.g. C<-tint white>).
125 131
126=item B<-bg> I<colour> 132=item B<-bg> I<colour>
127 133
128Window background colour; resource B<background>. 134Window background colour; resource B<background>.
129 135
132Window foreground colour; resource B<foreground>. 138Window foreground colour; resource B<foreground>.
133 139
134=item B<-pixmap> I<file[;geom]> 140=item B<-pixmap> I<file[;geom]>
135 141
136Compile I<XPM>: Specify XPM file for the background and also optionally 142Compile I<XPM>: Specify XPM file for the background and also optionally
137specify its scaling with a geometry string. Note you may need to add 143specify its scaling with a geometry string. Note you may need to
138quotes to avoid special shell interpretation of the `;' in the 144add quotes to avoid special shell interpretation of the C<;> in the
139command-line; resource B<backgroundPixmap>. 145command-line; resource B<backgroundPixmap>.
140 146
141=item B<-cr> I<colour> 147=item B<-cr> I<colour>
142 148
143The cursor colour; resource B<cursorColor>. 149The cursor colour; resource B<cursorColor>.
150 156
151The mouse pointer background colour; resource B<pointerColor2>. 157The mouse pointer background colour; resource B<pointerColor2>.
152 158
153=item B<-bd> I<colour> 159=item B<-bd> I<colour>
154 160
155The colour of the border between the xterm scrollbar and the text; 161The colour of the border around the text area and between the scrollbar and the text;
156resource B<borderColor>. 162resource B<borderColor>.
157 163
158=item B<-fn> I<fontname> 164=item B<-fn> I<fontlist>
159 165
160Select the fonts to be used. This is a comma seperated list of font 166Select the fonts to be used. This is a comma separated list of font names
161names that are used in turn when trying to display Unicode characters. 167that are used in turn when trying to display Unicode characters. The
162The first font defines the cell size for characters; other fonts might 168first font defines the cell size for characters; other fonts might be
163be smaller, but not larger. A reasonable default font list is always 169smaller, but not (in general) larger. A (hopefully) reasonable default
164appended to it. resource B<font>. 170font list is always appended to it. See resource B<font> for more details.
171
172In short, to specify an X11 core font, just specify it's name or prefix it
173with C<x:>. To specify an XFT-font, you need to prefix it with C<xft:>,
174e.g.:
175
176 @@RXVT_NAME@@ -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
177 @@RXVT_NAME@@ -fn "9x15bold,xft:Bitstream Vera Sans Mono"
165 178
166See also the question "How does rxvt-unicode choose fonts?" in the FAQ 179See also the question "How does rxvt-unicode choose fonts?" in the FAQ
167section. 180section of @@RXVT_NAME@@(7).
168 181
169=item B<-rb>|B<+rb> 182=item B<-fb> I<fontlist>
170 183
171Enable "real bold" support. When this option is on, bold text will be 184Compile font-styles: The bold font list to use when bold characters are to
172displayed using the first available bold font in the font list. Bold 185be printed. See resource B<boldFont> for details.
173fonts should thus be specified in the font list after their 186
174corresponding regular fonts. If no bold font can be found, a regular 187=item B<-fi> I<fontlist>
175font will be used. resource B<realBold>. 188
189Compile font-styles: The italic font list to use when bold characters are to
190be printed. See resource B<italicFont> for details.
191
192=item B<-fbi> I<fontlist>
193
194Compile font-styles: The bold italic font list to use when bold characters are to
195be printed. See resource B<boldItalicFont> for details.
176 196
177=item B<-name> I<name> 197=item B<-name> I<name>
178 198
179Specify the application name under which resources are to be obtained, 199Specify the application name under which resources are to be obtained,
180rather than the default executable file name. Name should not contain 200rather than the default executable file name. Name should not contain
221=item B<-st>|B<+st> 241=item B<-st>|B<+st>
222 242
223Display normal (non XTerm/NeXT) scrollbar without/with a trough; 243Display normal (non XTerm/NeXT) scrollbar without/with a trough;
224resource B<scrollBar_floating>. 244resource B<scrollBar_floating>.
225 245
246=item B<-ptab>|B<+ptab>
247
248If enabled (default), "Horizontal Tab" characters are being stored as
249actual wide characters in the screen buffer, which makes it possible to
250select and paste them. Since a horizontal tab is a cursor movement and
251not an actual glyph, this can sometimes be visually annoying as the cursor
252on a tab character is displayed as a wide cursor; resource B<pastableTabs>.
253
226=item B<-bc>|B<+bc> 254=item B<-bc>|B<+bc>
227 255
228Blink the cursor; resource B<cursorBlink>. 256Blink the cursor; resource B<cursorBlink>.
229 257
230=item B<-iconic> 258=item B<-iconic>
254if honoured by the WM, the rxvt-unicode window will not have window 282if honoured by the WM, the rxvt-unicode window will not have window
255decorations; resource B<borderLess>. 283decorations; resource B<borderLess>.
256 284
257=item B<-lsp> I<number> 285=item B<-lsp> I<number>
258 286
259Compile I<linespace>: Lines (pixel height) to insert between each row 287Compile I<frills>: Lines (pixel height) to insert between each row of
260of the display; resource B<linespace>. 288the display. Useful to work around font rendering problems; resource
289B<linespace>.
261 290
262=item B<-tn> I<termname> 291=item B<-tn> I<termname>
263 292
264This option specifies the name of the terminal type to be set in the 293This option specifies the name of the terminal type to be set in the
265B<TERM> environment variable. This terminal type must exist in the 294B<TERM> environment variable. This terminal type must exist in the
301 330
302Compile I<XIM>: input method name. resource B<inputMethod>. 331Compile I<XIM>: input method name. resource B<inputMethod>.
303 332
304=item B<-imlocale> I<string> 333=item B<-imlocale> I<string>
305 334
306The locale to use for opening the IM. You can use an LC_CTYPE of e.g. 335The locale to use for opening the IM. You can use an C<LC_CTYPE> of e.g.
307de_DE.UTF-8 for normal text processing but ja_JP.EUC-JP for the input 336C<de_DE.UTF-8> for normal text processing but C<ja_JP.EUC-JP> for the
308extension to be able to input japanese characters while staying in 337input extension to be able to input japanese characters while staying in
309another locale. 338another locale. resource B<imLocale>.
339
340=item B<-imfont> I<fontset>
341
342Set the font set to use for the X Input Method, see resource B<imFont>
343for more info.
344
345=item B<-tcw>
346
347Change the meaning of triple-click selection with the left mouse
348button. Instead of selecting a full line it will extend the selection the
349end of the logical line only. resource B<tripleclickwords>.
310 350
311=item B<-insecure> 351=item B<-insecure>
312 352
313Enable "insecure" mode, which currently enables most of the escape 353Enable "insecure" mode, which currently enables most of the escape
314sequences that echo strings. See the resource B<insecure> for more 354sequences that echo strings. See the resource B<insecure> for more
327 367
328=item B<-ssr>|B<+ssr> 368=item B<-ssr>|B<+ssr>
329 369
330Turn on/off secondary screen scroll (default enabled); resource 370Turn on/off secondary screen scroll (default enabled); resource
331B<secondaryScroll>. 371B<secondaryScroll>.
372
373=item B<-keysym.>I<sym>: I<string>
374
375Remap a key symbol. See resource B<keysym>.
332 376
333=item B<-xrm> I<resourcestring> 377=item B<-xrm> I<resourcestring>
334 378
335No effect on rxvt-unicode. Simply passes through an argument to be made 379No effect on rxvt-unicode. Simply passes through an argument to be made
336available in the instance's argument list. Appears in I<WM_COMMAND> in 380available in the instance's argument list. Appears in I<WM_COMMAND> in
345 389
346There are two different methods that @@RXVT_NAME@@ can use to get the 390There are two different methods that @@RXVT_NAME@@ can use to get the
347Xresource data: using the X libraries (Xrm*-functions) or internal 391Xresource data: using the X libraries (Xrm*-functions) or internal
348Xresources reader (B<~/.Xdefaults>). For the first method (ie. 392Xresources reader (B<~/.Xdefaults>). For the first method (ie.
349B<@@RXVT_NAME@@ -h> lists B<XGetDefaults>), you can set and change the 393B<@@RXVT_NAME@@ -h> lists B<XGetDefaults>), you can set and change the
350resources using X11 tools like B<xset>. Many distribution do also load 394resources using X11 tools like B<xrdb>. Many distribution do also load
351settings from the B<~/.Xresources> file when X starts. 395settings from the B<~/.Xresources> file when X starts. @@RXVT_NAME@@
396will consult the following files/resources in order, with later settings
397overwriting earlier ones:
398
399 1. system-wide app-defaults file, either locale-dependent OR global
400 2. app-defaults file in $XAPPLRESDIR
401 3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults
402 4. SCREEN_RESOURCES for the current screen
403 5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename>
352 404
353If compiled with internal Xresources support (i.e. B<@@RXVT_NAME@@ -h> 405If compiled with internal Xresources support (i.e. B<@@RXVT_NAME@@ -h>
354lists B<.Xdefaults>) then B<@@RXVT_NAME@@> accepts application defaults 406lists B<.Xdefaults>) then B<@@RXVT_NAME@@> accepts application defaults
355set in XAPPLOADDIR/URxvt (compile-time defined: usually 407set in XAPPLOADDIR/URxvt (compile-time defined: usually
356B</usr/lib/X11/app-defaults/URxvt>) and resources set in 408B</usr/lib/X11/app-defaults/URxvt>) and resources set in
389high-intensity (bold = bright foreground, blink = bright background) 441high-intensity (bold = bright foreground, blink = bright background)
390colours. The canonical names are as follows: 0=black, 1=red, 2=green, 442colours. The canonical names are as follows: 0=black, 1=red, 2=green,
3913=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour 4433=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour
392names used are listed in the B<COLORS AND GRAPHICS> section. 444names used are listed in the B<COLORS AND GRAPHICS> section.
393 445
446Colours higher than 15 cannot be set using resources (yet), but can be
447changed using an escape command (see @@RXVT_NAME@@(7)).
448
449Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with
45088 colour support). Colours 80-87 are evenly spaces grey steps.
451
394=item B<colorBD:> I<colour> 452=item B<colorBD:> I<colour>
395 453
454=item B<colorIT:> I<colour>
455
396Use the specified colour to display bold characters when the foreground 456Use the specified colour to display bold or italic characters when the
397colour is the default. This option will be ignored if B<realBold> is 457foreground colour is the default. If font styles are not available
398enabled. 458(Compile I<styles>) and this option is unset, reverse video is used instead.
399 459
400=item B<colorUL:> I<colour> 460=item B<colorUL:> I<colour>
401 461
402Use the specified colour to display underlined characters when the 462Use the specified colour to display underlined characters when the
403foreground colour is the default. 463foreground colour is the default.
404 464
405=item B<colorRV:> I<colour> 465=item B<colorRV:> I<colour>
406 466
407Use the specified colour as the background for reverse video 467Use the specified colour as the background for reverse video
408characters. 468characters.
469
470=item B<underlineColor:> I<colour>
471
472If set, use the specified colour as the colour for the underline
473itself. If unset, use the foreground colour.
409 474
410=item B<cursorColor:> I<colour> 475=item B<cursorColor:> I<colour>
411 476
412Use the specified colour for the cursor. The default is to use the 477Use the specified colour for the cursor. The default is to use the
413foreground colour; option B<-cr>. 478foreground colour; option B<-cr>.
447=item B<shading:> I<number> 512=item B<shading:> I<number>
448 513
449Darken (0 .. 100) or lighten (-1 .. -100) the transparent background 514Darken (0 .. 100) or lighten (-1 .. -100) the transparent background
450image in addition to tinting it. 515image in addition to tinting it.
451 516
452=item B<fading:> I<number>
453
454Scale the tint colour by the given percentage.
455
456=item B<scrollColor:> I<colour> 517=item B<scrollColor:> I<colour>
457 518
458Use the specified colour for the scrollbar [default #B2B2B2]. 519Use the specified colour for the scrollbar [default #B2B2B2].
459 520
460=item B<troughColor:> I<colour> 521=item B<troughColor:> I<colour>
461 522
462Use the specified colour for the scrollbar's trough area [default 523Use the specified colour for the scrollbar's trough area [default
463#969696]. Only relevant for normal (non XTerm/NeXT) scrollbar. 524#969696]. Only relevant for normal (non XTerm/NeXT) scrollbar.
525
526=item B<borderColor:> I<colour>
527
528The colour of the border around the text area and between the scrollbar
529and the text.
464 530
465=item B<backgroundPixmap:> I<file[;geom]> 531=item B<backgroundPixmap:> I<file[;geom]>
466 532
467Use the specified XPM file (note the `.xpm' extension is optional) for 533Use the specified XPM file (note the `.xpm' extension is optional) for
468the background and also optionally specify its scaling with a geometry 534the background and also optionally specify its scaling with a geometry
484 550
485Specify the colon-delimited search path for finding files (XPM and 551Specify the colon-delimited search path for finding files (XPM and
486menus), in addition to the paths specified by the B<RXVTPATH> and 552menus), in addition to the paths specified by the B<RXVTPATH> and
487B<PATH> environment variables. 553B<PATH> environment variables.
488 554
489=item B<font:> I<fontname> 555=item B<font:> I<fontlist>
490 556
491Select the fonts to be used. This is a comma seperated list of font 557Select the fonts to be used. This is a comma separated list of font
492names that are used in turn when trying to display Unicode characters. 558names that are used in turn when trying to display Unicode characters.
493The first font defines the cell size for characters; other fonts might 559The first font defines the cell size for characters; other fonts might
494be smaller, but not larger. A reasonable default font list is always 560be smaller, but not larger. A reasonable default font list is always
495appended to it. option B<-fn>. 561appended to it. option B<-fn>.
496 562
497=item B<realBold:> I<boolean> 563Each font can either be a standard X11 core font (XLFD) name, with
564optional prefix C<x:> or a Xft font (Compile I<xft>), prefixed with C<xft:>.
498 565
499B<True>: Enable "real bold" support. When this option is on, bold text 566In addition, each font can be prefixed with additional hints and
500will be displayed using the first available bold font in the font list. 567specifications enclosed in square brackets (C<[]>). The only available
501Bold fonts should thus be specified in the font list after their 568hint currently is C<codeset=codeset-name>, and this is only used for Xft
502corresponding regular fonts. If no bold font can be found, a regular 569fonts.
503font will be used. option B<-rb>. B<False>: Display bold text in a 570
504regular font, using the color specified with B<colorBD>; option B<+rb>. 571For example, this font resource
572
573 URxvt*font: 9x15bold,\
574 -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
575 -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
576 [codeset=JISX0208]xft:Kochi Gothic:antialias=false, \
577 xft:Code2000:antialias=false
578
579specifies five fonts to be used. The first one is C<9x15bold> (actually
580the iso8859-1 version of the second font), which is the base font (because
581it is named first) and thus defines the character cell grid to be 9 pixels
582wide and 15 pixels high.
583
584The second font is just used to add additional unicode characters not in
585the base font, likewise the third, which is unfortunately non-bold, but
586the bold version of the font does contain less characters, so this is a
587useful supplement.
588
589The third font is an Xft font with aliasing turned off, and the characters
590are limited to the B<JIS 0208> codeset (i.e. japanese kanji). The font
591contains other characters, but we are not interested in them.
592
593The last font is a useful catch-all font that supplies most of the
594remaining unicode characters.
595
596=item B<boldFont:> I<fontlist>
597
598=item B<italicFont:> I<fontlist>
599
600=item B<boldItalicFont:> I<fontlist>
601
602The font list to use for displaying B<bold>, I<italic> or B<< I<bold
603italic> >> characters, respectively.
604
605If specified and non-empty, then the syntax is the same as for the
606B<font>-resource, and the given font list will be used as is, which makes
607it possible to substitute completely different font styles for bold and
608italic.
609
610If unset (the default), a suitable font list will be synthesized by
611"morphing" the normal text font list into the desired shape. If that is
612not possible, replacement fonts of the desired shape will be tried.
613
614If set, but empty, then this specific style is disabled and the normal
615text font will being used for the given style.
505 616
506=item B<selectstyle:> I<mode> 617=item B<selectstyle:> I<mode>
507 618
508Set mouse selection style to B<old> which is 2.20, B<oldword> which is 619Set mouse selection style to B<old> which is 2.20, B<oldword> which is
509xterm style with 2.20 old word selection, or anything else which gives 620xterm style with 2.20 old word selection, or anything else which gives
580B<False>: do not scroll to bottom when tty receives output; option 691B<False>: do not scroll to bottom when tty receives output; option
581B<+si>. 692B<+si>.
582 693
583=item B<scrollWithBuffer:> I<boolean> 694=item B<scrollWithBuffer:> I<boolean>
584 695
585B<True>: scroll with scrollback buffer when tty recieves new lines (and 696B<True>: scroll with scrollback buffer when tty receives new lines (and
586B<scrollTtyOutput> is False); option B<+sw>. B<False>: do not scroll 697B<scrollTtyOutput> is False); option B<+sw>. B<False>: do not scroll
587with scrollback buffer when tty recieves new lines; option B<-sw>. 698with scrollback buffer when tty recieves new lines; option B<-sw>.
588 699
589=item B<scrollTtyKeypress:> I<boolean> 700=item B<scrollTtyKeypress:> I<boolean>
590 701
631=item B<mouseWheelScrollPage:> I<boolean> 742=item B<mouseWheelScrollPage:> I<boolean>
632 743
633B<True>: the mouse wheel scrolls a page full. B<False>: the mouse wheel 744B<True>: the mouse wheel scrolls a page full. B<False>: the mouse wheel
634scrolls five lines [default]. 745scrolls five lines [default].
635 746
747=item B<pastableTabs:> I<boolean>
748
749B<True>: store tabs as wide characters. B<False>: interpret tabs as cursor
750movement only; option C<-ptab>.
751
636=item B<cursorBlink:> I<boolean> 752=item B<cursorBlink:> I<boolean>
637 753
638B<True>: blink the cursor. B<False>: do not blink the cursor [default]; 754B<True>: blink the cursor. B<False>: do not blink the cursor [default];
639option B<-bc>. 755option B<-bc>.
640 756
684 800
685I<name> of inputMethod to use; option B<-im>. 801I<name> of inputMethod to use; option B<-im>.
686 802
687=item B<imLocale:> I<name> 803=item B<imLocale:> I<name>
688 804
689The locale to use for opening the IM. You can use an LC_CTYPE of e.g. 805The locale to use for opening the IM. You can use an C<LC_CTYPE> of e.g.
690de_DE.UTF-8 for normal text processing but ja_JP.EUC-JP for the input 806C<de_DE.UTF-8> for normal text processing but C<ja_JP.EUC-JP> for the
691extension to be able to input japanese characters while staying in 807input extension to be able to input japanese characters while staying in
692another locale. option B<-imlocale>. 808another locale. option B<-imlocale>.
693 809
694=item B<insecure> 810=item B<imFont:> I<fontset>
811
812Specify the font-set used for XIM styles C<OverTheSpot> or
813C<OffTheSpot>. It must be a standard X font set (XLFD patterns separated
814by commas), i.e. it's not in the same format as the other font lists used
815in @@RXVT_NAME@@. The default will be set-up to chose *any* suitable found
816found, preferably one or two pixels differing in size to the base font.
817option B<-imfont>.
818
819=item B<tripleclickwords:> I<boolean>
820
821Change the meaning of triple-click selection with the left mouse
822button. Instead of selecting a full line it will extend the selection to
823the end of the logical line only. option B<-tcw>.
824
825=item B<insecure:> I<boolean>
695 826
696Enables "insecure" mode. Rxvt-unicode offers some escape sequences that 827Enables "insecure" mode. Rxvt-unicode offers some escape sequences that
697echo arbitrary strings like the icon name or the locale. This could be 828echo arbitrary strings like the icon name or the locale. This could be
698abused if somebody gets 8-bit-clean access to your display, wether 829abused if somebody gets 8-bit-clean access to your display, whether
699throuh a mail client displaying mail bodies unfiltered or though 830throuh a mail client displaying mail bodies unfiltered or though
700write(1). Therefore, these sequences are disabled by default. (Note 831write(1). Therefore, these sequences are disabled by default. (Note
701that other terminals, including xterm, have these sequences 832that other terminals, including xterm, have these sequences
702enabled by default). You can enable them by setting this boolean 833enabled by default). You can enable them by setting this boolean
703resource or specifying B<-insecure> as an option. At the moment, this 834resource or specifying B<-insecure> as an option. At the moment, this
727scrollback buffer and switching to/from the secondary screen will 858scrollback buffer and switching to/from the secondary screen will
728instead scroll the screen up. 859instead scroll the screen up.
729 860
730=item B<keysym.>I<sym>: I<string> 861=item B<keysym.>I<sym>: I<string>
731 862
732Associate I<string> with keysym I<sym> (B<0xFF00 - 0xFFFF>). It may 863Compile I<frills>: Associate I<string> with keysym I<sym>. The
733contain escape values (\a: bell, \b: backspace, \e, \E: escape, \n: 864intervening resource name B<keysym.> cannot be omitted.
734newline, \r: return, \t: 865
866The format of I<sym> is "I<(modifiers-)key>", where I<modifiers> can be
867any combination of B<ISOLevel3>, B<AppKeypad>, B<Control>, B<NumLock>,
868B<Shift>, B<Meta>, B<Lock>, B<Mod1>, B<Mod2>, B<Mod3>, B<Mod4>, B<Mod5>,
869and the abbreviated B<I>, B<K>, B<C>, B<N>, B<S>, B<M>, B<A>, B<L>, B<1>,
870B<2>, B<3>, B<4>, B<5>.
871
872The B<NumLock>, B<Meta> and B<ISOLevel3> modifiers are usually aliased to
873whatever modifier the NumLock key, Meta/Alt keys or ISO Level3 Shift/AltGr
874keys are being mapped. B<AppKeypad> is a synthetic modifier mapped to the
875current application keymap mode state.
876
877The spellings of I<key> can be obtained by using B<xev>(1) command or
878searching keysym macros from B</usr/X11R6/include/X11/keysymdef.h> and
879omitting the prefix B<XK_>. Alternatively you can specify I<key> by its hex
880keysym value (B<0x0000 - 0xFFFF>). Note that the lookup of I<sym>s is not
881performed in an exact manner; however, the closest match is assured.
882
883I<string> may contain escape values (C<\a>: bell, C<\b>: backspace,
884C<\e>, C<\E>: escape, C<\n>: newline, C<\r>: carriage return, C<\t>: tab,
735tab, \000: octal number) or control characters (^?: delete, ^@: null, 885C<\000>: octal number) or verbatim control characters (C<^?>: delete,
736^A ...) and may enclosed with double quotes so that it can start or end 886C<^@>: null, C<^A> ...) and may be enclosed with double quotes so that it
737with whitespace. The intervening resource name B<keysym.> cannot be 887can start or end with whitespace.
738omitted. This resource is only available when compiled with 888
739KEYSYM_RESOURCE. 889Please note that you need to double the C<\> when using
890C<--enable-xgetdefault>, as X itself does it's own de-escaping (you can
891use C<\033> instead of C<\e> (and so on), which will work with both Xt and
892@@RXVT_NAME@@'s own processing).
893
894You can define a range of keysyms in one shot by providing a I<string>
895with pattern B<list/PREFIX/MIDDLE/SUFFIX>, where the delimeter `/'
896should be a character not used by the strings.
897
898Its usage can be demonstrated by an example:
899
900 URxvt.keysym.M-C-0x61: list|\033<M-C-|abc|>
901
902The above line is equivalent to the following three lines:
903
904 URxvt.keysym.Meta-Control-0x61: \033<M-C-a>
905 URxvt.keysym.Meta-Control-0x62: \033<M-C-b>
906 URxvt.keysym.Meta-Control-0x63: \033<M-C-c>
907
908If I<string> takes the form of C<command:STRING>, the specified B<STRING>
909is interpreted and executed as @@RXVT_NAME@@'s control sequence. For
910example the following means "change the current locale to C<zh_CN.GBK>
911when Control-Meta-c is being pressed":
912
913 URxvt.keysym.M-C-c: command:\033]701;zh_CN.GBK\007
914
915The following example will map Control-Meta-1 and Control-Meta-2 to
916the fonts C<suxuseuro> and C<9x15bold>, so you can have some limited
917font-switching at runtime:
918
919 URxvt.keysym.M-C-1: command:\033]50;suxuseuro\007
920 URxvt.keysym.M-C-2: command:\033]50;9x15bold\007
921
922Other things are possible, e.g. resizing (see @@RXVT_NAME@@(7) for more
923info):
924
925 URxvt.keysym.M-C-3: command:\033[8;25;80t
926 URxvt.keysym.M-C-4: command:\033[8;48;110t
740 927
741=back 928=back
742 929
743=head1 THE SCROLLBAR 930=head1 THE SCROLLBAR
744 931
758the normal text selection/insertion, hold either the Shift or the Meta 945the normal text selection/insertion, hold either the Shift or the Meta
759(Alt) key while performing the desired mouse action. 946(Alt) key while performing the desired mouse action.
760 947
761If mouse reporting mode is active, the normal scrollbar actions are 948If mouse reporting mode is active, the normal scrollbar actions are
762disabled -- on the assumption that we are using a fullscreen 949disabled -- on the assumption that we are using a fullscreen
763application. Instead, pressing Button1 and Button3 sends B<ESC[6~> 950application. Instead, pressing Button1 and Button3 sends B<ESC [ 6 ~>
764(Next) and B<ESC[5~> (Prior), respectively. Similarly, clicking on the 951(Next) and B<ESC [ 5 ~> (Prior), respectively. Similarly, clicking on the
765up and down arrows sends B<ESC[A> (Up) and B<ESC[B> (Down), 952up and down arrows sends B<ESC [ A> (Up) and B<ESC [ B> (Down),
766respectively. 953respectively.
767 954
768=head1 TEXT SELECTION AND INSERTION 955=head1 TEXT SELECTION AND INSERTION
769 956
770The behaviour of text selection and insertion mechanism is similar to 957The behaviour of text selection and insertion mechanism is similar to
772 959
773=over 4 960=over 4
774 961
775=item B<Selection>: 962=item B<Selection>:
776 963
777Left click at the beginning of the region, drag to the end of the 964Left click at the beginning of the region, drag to the end of the region
778region and release; Right click to extend the marked region; Left 965and release; Right click to extend the marked region; Left double-click
779double-click to select a word; Left triple-click to select the entire 966to select a word; Left triple-click to select the entire logical line
780line. 967(which can span multiple screen lines), unless modified by resource
968B<tripleclickwords>.
969
970Starting a selection while pressing the B<Meta> key (or B<Meta+Ctrl> keys)
971(Compile: I<frills>) will create a rectangular selection instead of a normal
972one.
781 973
782=item B<Insertion>: 974=item B<Insertion>:
783 975
784Pressing and releasing the Middle mouse button (or B<Shift-Insert>) in 976Pressing and releasing the Middle mouse button (or B<Shift-Insert>) in
785an B<@@RXVT_NAME@@> window causes the current text selection to be 977an B<@@RXVT_NAME@@> window causes the current text selection to be
807C<--enable-frills>, the rest is available when rxvt-unicode was compiled 999C<--enable-frills>, the rest is available when rxvt-unicode was compiled
808with C<--enable-iso14755>. 1000with C<--enable-iso14755>.
809 1001
810=over 4 1002=over 4
811 1003
812=item 5.1: Basic method 1004=item * 5.1: Basic method
813 1005
814This allows you to enter unicode characters using their hexcode. 1006This allows you to enter unicode characters using their hexcode.
815 1007
816Start by pressing and holding both C<Control> and C<Shift>, then enter 1008Start by pressing and holding both C<Control> and C<Shift>, then enter
817hex-digits (between one and six). Releasing C<Control> and C<Shift> will 1009hex-digits (between one and six). Releasing C<Control> and C<Shift> will
824address, which you cannot type. Fortunately, the card has the e-mail 1016address, which you cannot type. Fortunately, the card has the e-mail
825address printed as hexcodes, e.g. C<671d 65e5>. You can enter this easily 1017address printed as hexcodes, e.g. C<671d 65e5>. You can enter this easily
826by pressing C<Control> and C<Shift>, followed by C<6-7-1-D-SPACE-6-5-E-5>, 1018by pressing C<Control> and C<Shift>, followed by C<6-7-1-D-SPACE-6-5-E-5>,
827followed by releasing the modifier keys. 1019followed by releasing the modifier keys.
828 1020
829=item 5.2: Keyboard symbols entry method 1021=item * 5.2: Keyboard symbols entry method
830 1022
831This mode lets you input characters representing the keycap symbols of 1023This mode lets you input characters representing the keycap symbols of
832your keyboard, if representable in the current locale encoding. 1024your keyboard, if representable in the current locale encoding.
833 1025
834Start by pressing C<Control> and C<Shift> together, then releasing 1026Start by pressing C<Control> and C<Shift> together, then releasing
835them. The next special key (cursor keys, home etc.) you enter will not 1027them. The next special key (cursor keys, home etc.) you enter will not
836invoke it's usual function but instead will insert the corresponding 1028invoke it's usual function but instead will insert the corresponding
837keycap symbol. The symbol will only be entered when the key has been 1029keycap symbol. The symbol will only be entered when the key has been
838released, otherwise pressing e.g. C<Shift> would enter the symbol for 1030released, otherwise pressing e.g. C<Shift> would enter the symbol for
839C<ISO Level 2 Switch>, although your intention might have beenm to enter a 1031C<ISO Level 2 Switch>, although your intention might have been to enter a
840reverse tab (Shift-Tab). 1032reverse tab (Shift-Tab).
841 1033
842=item 5.3: Screen-selection entry method 1034=item * 5.3: Screen-selection entry method
843 1035
844While this is implemented already (it's basically the selection 1036While this is implemented already (it's basically the selection
845mechanism), it could be extended by displaying a unicode character map. 1037mechanism), it could be extended by displaying a unicode character map.
846 1038
847=item 5.4: Feedback method for identifying displayed characters for later input 1039=item * 5.4: Feedback method for identifying displayed characters for later input
848 1040
849This method lets you display the unicode character code associated with 1041This method lets you display the unicode character code associated with
850characters already displayed. 1042characters already displayed.
851 1043
852You enter this mode by holding down C<Control> and C<Shift> together, then 1044You enter this mode by holding down C<Control> and C<Shift> together, then
853pressing and holding the left mouse button and moving around. The unicode 1045pressing and holding the left mouse button and moving around. The unicode
854hex code(s) (it might be a combining character) of the character under the 1046hex code(s) (it might be a combining character) of the character under the
855pointer is displayed until you release C<Control> and C<Shift>. 1047pointer is displayed until you release C<Control> and C<Shift>.
856 1048
1049In addition to the hex codes it will display the font used to draw this
1050character - due to implementation reasons, characters combined with
1051combining characters, line drawing characters and unknown characters will
1052always be drawn using the built-in support font.
1053
857=back 1054=back
858 1055
859With respect to conformance, rxvt-unicode is supposed to be compliant to 1056With respect to conformance, rxvt-unicode is supposed to be compliant to
860both scenario A and B of ISO 14755, including part 5.2. 1057both scenario A and B of ISO 14755, including part 5.2.
861 1058
862=head1 LOGIN STAMP 1059=head1 LOGIN STAMP
863 1060
864B<@@RXVT_NAME@@> tries to write an entry into the I<utmp>(5) file so 1061B<@@RXVT_NAME@@> tries to write an entry into the I<utmp>(5) file so that
865that it can be seen via the I<who(1)> command, and can accept messages. 1062it can be seen via the I<who(1)> command, and can accept messages. To
866To allow this feature, B<@@RXVT_NAME@@> must be installed setuid root on 1063allow this feature, B<@@RXVT_NAME@@> may need to be installed setuid root
867some systems. 1064on some systems or setgid to root or to some other group on others.
868 1065
869=head1 COLORS AND GRAPHICS 1066=head1 COLORS AND GRAPHICS
870 1067
871In addition to the default foreground and background colours, 1068In addition to the default foreground and background colours,
872B<@@RXVT_NAME@@> can display up to 16 colours (8 ANSI colours plus 1069B<@@RXVT_NAME@@> can display up to 16 colours (8 ANSI colours plus
913would yield White on Black, while on I<xterm>(1) it would yield Black 1110would yield White on Black, while on I<xterm>(1) it would yield Black
914on White. 1111on White.
915 1112
916=back 1113=back
917 1114
918=head1 FREQUENTLY ASKED QUESTIONS (FAQ) 1115=head1 ENVIRONMENT
1116
1117B<@@RXVT_NAME@@> sets and/or uses the following environment variables:
919 1118
920=over 4 1119=over 4
921 1120
922=item How do I know which rxvt-unicode version I'm using? 1121=item B<TERM>
923 1122
924The version number is displayed with the usage (-h). For rxvt-unicode 1123Normally set to C<rxvt-unicode>, unless overwritten at configure time, via
925version 2.14 and later, the escape sequence C<ESC[8n> sets the window 1124resources or on the commandline.
926title to the version number.
927 1125
928=item Rxvt-unicode does not seem to understand the selected encoding? 1126=item B<COLORTERM>
929 1127
930=item Unicode does not seem to work? 1128Either C<rxvt>, C<rxvt-xpm>, depending on wether @@RXVT_NAME@@ was
1129compiled with XPM support, and optionally with the added extension
1130C<-mono> to indicate that rxvt-unicode runs on a monochrome screen.
931 1131
932If you encounter strange problems like typing an accented character but 1132=item B<COLORFGBG>
933getting two unrelated other characters or similar, or if program output is
934subtly garbled, then you should check your locale settings.
935 1133
936Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the 1134Set to a string of the form C<fg;bg> or C<fg;xpm;bg>, where C<fg> is
937programs. Often rxvt-unicode is started in the C<C> locale, while the 1135the colour code used as default foreground/text colour (or the string
938login script running within the rxvt-unicode window changes the locale to 1136C<default> to indicate that the default-colour escape sequence is to be
939sth. else, e.h. C<en_GB.UTF-8>. Needless to say, this is not going to work. 1137used), C<bg> is the colour code used as default background colour (or the
1138string C<default>), and C<xpm> is the string C<default> if @@RXVT_NAME@@
1139was compiled with XPM support. Libraries like C<slang> can (and do) use
1140this information to optimize screen output.
940 1141
941The best thing is to fix your startup environment, as you will likely run 1142=item B<WINDOWID>
942into other problems. If nothing works you can try this in your .profile.
943 1143
944 printf '\e]701;%s\007' "$LC_CTYPE" 1144Set to the (decimal) X Window ID of the @@RXVT_NAME@@ window (the toplevel
1145window, which usually has subwindows for the scrollbar, the terminal
1146window and so on).
945 1147
946If this doesn't work, then maybe you use a C<LC_CTYPE> specification not 1148=item B<TERMINFO>
947supported on your systems. Some systems have a C<locale> comamnd which
948displays this. If it displays sth. like:
949 1149
950 locale: Cannot set LC_CTYPE to default locale: ... 1150Set to the terminfo directory iff @@RXVT_NAME@@ was configured with
1151C<--with-terminfo=PATH>.
951 1152
952Then the locale you specified is not supported on your system. 1153=item B<DISPLAY>
953 1154
954If nothing works and you are sure that everything is set correctly then 1155Used by @@RXVT_NAME@@ to connect to the display and set to the correct
955you will need to remember a little known fact: Some programs just don't 1156display in it's child processes.
956support locales :(
957 1157
958=item Why do the characters look ugly? 1158=item B<SHELL>
959 1159
960=item How does rxvt-unicode choose fonts? 1160The shell to be used for command execution, defaults to C</bin/sh>.
961 1161
962Most fonts do not contain the full range of Unicode, which is 1162=item B<RXVTPATH>
963fine. Chances are that the font you (or the admin/package maintainer of
964your system/os) have specified does not cover all the characters you want
965to display.
966 1163
967B<rxvt-unicode> makes a best-effort try at finding a replacement 1164The path where @@RXVT_NAME@@ looks for support files such as menu and xpm
968font. Often the result is fine, but sometimes the chosen font looks 1165files.
969bad. In that case, select a font of your taste and add it to the font
970list, e.g.:
971 1166
972 @@RXVT_NAME@@ -fn basefont,font2,font3... 1167=item B<PATH>
973 1168
974When rxvt-unicode sees a character, it will first look at the base 1169Used in the same way as C<RXVTPATH>.
975font. If the base font does not contain the character, it will go to the
976next font, and so on.
977 1170
978The only limitation is that all the fonts must not be larger than the base 1171=item B<RXVT_SOCKET>
979font, as the base font defines the principial cell size, which must be the
980same due to the way terminals work.
981 1172
982=item Why do some chinese characters look so different than others? 1173The unix domain socket path used by @@RXVT_NAME@@c(1) and
1174@@RXVT_NAME@@d(1).
983 1175
984This is because there is a difference between script and language -- 1176Default C<< $HOME/.rxvt-unicode-<nodename >>.
985rxvt-unicode does not know which language the text that is output
986is, as it only knows the unicode character codes. If rxvt-unicode
987first sees a japanese character, it might choose a japanese font for
988it. Subseqzuent japanese characters will take that font. Now, many chinese
989characters aren't represented in japanese fonts, so when the first
990non-japanese character comes up, rxvt-unicode will look for a chinese font
991-- unfortunately at this point, it will still use the japanese font for
992japanese characters that are also chinese.
993 1177
994The workaround is easy: just tag a chinese font at the end of your font 1178=item B<HOME>
995list (see the previous question). The key is to view the font list as
996a preference list: If you expect more japanese, list a japanese font
997first. If you expect more chinese, put a chinese font first.
998 1179
999In the future it might be possible to switch preferences at runtime (the 1180Used to locate the default directory for the unix domain socket for
1000internal data structure has no problem with using different fonts for 1181daemon communications and to locate various resource files (such as
1001the same character at the same time, but no interface for this has been 1182C<.Xdefaults>)
1002designed yet).
1003 1183
1004=item How does rxvt-unicode determine the encoding to use? 1184=item B<XAPPLRESDIR>
1005 1185
1006=item Is there an option to switch encodings? 1186Directory where various X resource files are being located.
1007 1187
1008Unlike some other terminals, rxvt-unicode has no encoding switch, and no 1188=item B<XENVIRONMENT>
1009specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
1010UTF-8 or any other encodings with respect to terminal I/O.
1011 1189
1012The reasons is that there exists a perfectly fine mechanism for selecting 1190If set and accessible, gives the name of a X resource file to be loaded by
1013the encoding, doing I/O and (most important) communicating this to all
1014applications so everybody agrees on character properties such as width and
1015code number. This mechanism is the I<locale>.
1016
1017Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
1018programs doing the same (that is, most) will automatically agree in the
1019interpretation of characters.
1020
1021Unfortunately, there is no system-independent way to select locales, nor
1022is there a standard on how locale specifiers will look like.
1023
1024On most systems, the content of the C<LC_CTYPE> environment variable
1025contains an arbitrary string which corresponds to an already-installed
1026locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
1027C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
1028(i.e. C<de> or C<german>) are also common.
1029
1030Rxvt-unicode ignores all other locale categories, and except for
1031the encoding, ignores country or language-specific settings,
1032i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the same for rxvt-unicode.
1033
1034If you want to use a specific encoding you have to make sure you start
1035rxvt-unicode with the correct C<LC_CTYPE> category.
1036
1037=item Can I switch locales at runtime?
1038
1039Yes, using an escape sequence. Try sth. like this, which sets
1040rxvt-unicode's idea of C<LC_CTYPE>.
1041
1042 printf '\e]701;%s\007' ja_JP.SJIS
1043
1044See also the previous question.
1045
1046Sometimes this capability is rather handy when you want to work in one
1047locale (e.g. C<de_DE.UTF-8>) but some programs don't support UTF-8. For
1048example, I use this script to start C<xjdic>, which first switches to a
1049locale supported by xjdic and back later:
1050
1051 printf '\e]701;%s\007' ja_JP.SJIS
1052 xjdic -js
1053 printf '\e]701;%s\007' de_DE.UTF-8
1054
1055=item Can I switch the fonts at runtime?
1056
1057Yes, using an escape sequence. Try sth. like this, which has the same
1058effect as using the C<-fn> switch, and takes effect immediately:
1059
1060 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
1061
1062This is useful if you e.g. work primarily with japanese (and prefer a
1063japanese font), but you have to switch to chinese temporarily, where
1064japanese fonts would only be in your way.
1065
1066You can think of this as a kind of manual ISO-2022 switching.
1067
1068=item Mouse cut/paste suddenly no longer works.
1069
1070Make sure that mouse reporting is actually turned off since killing
1071some editors prematurely may leave the mouse in mouse report mode. I've
1072heard that tcsh may use mouse reporting unless it otherwise specified. A
1073quick check is to see if cut/paste works when the Alt or Shift keys are
1074depressed. See @@RXVT_NAME@@(7)
1075
1076=item What's with this bold/blink stuff?
1077
1078If no bold colour is set via C<colorBD:>, bold will invert text using the
1079standard foreground colour.
1080
1081For the standard background colour, blinking will actually make the
1082text blink when compiled with C<--enable-blinking>. with standard
1083colours. Without C<--enable-blinking>, the blink attribute will be
1084ignored.
1085
1086On ANSI colours, bold/blink attributes are used to set high-intensity
1087foreground/background colors.
1088
1089color0-7 are the low-intensity colors.
1090
1091color8-15 are the corresponding high-intensity colors.
1092
1093=item I don't like the screen colors. How do I change them?
1094
1095You can change the screen colors at run-time using F<~/.Xdefaults>
1096resources (or as long-options).
1097
1098Here are values that are supposed to resemble a VGA screen,
1099including the murky brown that passes for low-intensity yellow:
1100
1101 Rxvt*color0: #000000
1102 Rxvt*color1: #A80000
1103 Rxvt*color2: #00A800
1104 Rxvt*color3: #A8A800
1105 Rxvt*color4: #0000A8
1106 Rxvt*color5: #A800A8
1107 Rxvt*color6: #00A8A8
1108 Rxvt*color7: #A8A8A8
1109
1110 Rxvt*color8: #000054
1111 Rxvt*color9: #FF0054
1112 Rxvt*color10: #00FF54
1113 Rxvt*color11: #FFFF54
1114 Rxvt*color12: #0000FF
1115 Rxvt*color13: #FF00FF
1116 Rxvt*color14: #00FFFF
1117 Rxvt*color15: #FFFFFF
1118
1119=item What's with the strange Backspace/Delete key behaviour?
1120
1121Assuming that the physical Backspace key corresponds to the
1122BackSpace keysym (not likely for Linux ... see the following
1123question) there are two standard values that can be used for
1124Backspace: C<^H> and C<^?>.
1125
1126Historically, either value is correct, but rxvt-unicode adopts the debian
1127policy of using C<^?> when unsure, because it's the one only only correct
1128choice :).
1129
1130Rxvt-unicode tries to inherit the current stty settings and uses the value
1131of `erase' to guess the value for backspace. If rxvt-unicode wasn't
1132started from a terminal (say, from a menu or by remote shell), then the
1133system value of `erase', which corresponds to CERASE in <termios.h>, will
1134be used (which may not be the same as your stty setting).
1135
1136For starting a new rxvt-unicode:
1137
1138 # use Backspace = ^H
1139 $ stty erase ^H
1140 $ @@RXVT_NAME@@ 1191@@RXVT_NAME@@.
1141
1142 # use Backspace = ^?
1143 $ stty erase ^?
1144 $ @@RXVT_NAME@@
1145
1146Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7).
1147
1148For an existing rxvt-unicode:
1149
1150 # use Backspace = ^H
1151 $ stty erase ^H
1152 $ echo -n "^[[36h"
1153
1154 # use Backspace = ^?
1155 $ stty erase ^?
1156 $ echo -n "^[[36l"
1157
1158This helps satisfy some of the Backspace discrepancies that occur, but
1159if you use Backspace = C<^H>, make sure that the termcap/terminfo value
1160properly reflects that.
1161
1162The Delete key is a another casualty of the ill-defined Backspace problem.
1163To avoid confusion between the Backspace and Delete keys, the Delete
1164key has been assigned an escape sequence to match the vt100 for Execute
1165(ESC[3~) and is in the supplied termcap/terminfo.
1166
1167Some other Backspace problems:
1168
1169some editors use termcap/terminfo,
1170some editors (vim I'm told) expect Backspace = ^H,
1171GNU Emacs (and Emacs-like editors) use ^H for help.
1172
1173Perhaps someday this will all be resolved in a consistent manner.
1174
1175=item I don't like the key-bindings. How do I change them?
1176
1177There are some compile-time selections available via configure. Unless
1178you have run "configure" with the C<--disable-resources> option you can
1179use the `keysym' resource to alter the keystrings associated with keysym
11800xFF00 - 0xFFFF (function, cursor keys, etc).
1181
1182Here's an example for a tn3270 session started using `@@RXVT_NAME@@ -name tn3270'
1183
1184 !# ----- special uses ------:
1185 ! tn3270 login, remap function and arrow keys.
1186 tn3270*font: *clean-bold-*-*--15-*
1187
1188 ! keysym - used by rxvt only
1189 ! Delete - ^D
1190 tn3270*keysym.0xFFFF: \004
1191
1192 ! Home - ^A
1193 tn3270*keysym.0xFF50: \001
1194 ! Left - ^B
1195 tn3270*keysym.0xFF51: \002
1196 ! Up - ^P
1197 tn3270*keysym.0xFF52: \020
1198 ! Right - ^F
1199 tn3270*keysym.0xFF53: \006
1200 ! Down - ^N
1201 tn3270*keysym.0xFF54: \016
1202 ! End - ^E
1203 tn3270*keysym.0xFF57: \005
1204
1205 ! F1 - F12
1206 tn3270*keysym.0xFFBE: \e1
1207 tn3270*keysym.0xFFBF: \e2
1208 tn3270*keysym.0xFFC0: \e3
1209 tn3270*keysym.0xFFC1: \e4
1210 tn3270*keysym.0xFFC2: \e5
1211 tn3270*keysym.0xFFC3: \e6
1212 tn3270*keysym.0xFFC4: \e7
1213 tn3270*keysym.0xFFC5: \e8
1214 tn3270*keysym.0xFFC6: \e9
1215 tn3270*keysym.0xFFC7: \e0
1216 tn3270*keysym.0xFFC8: \e-
1217 tn3270*keysym.0xFFC9: \e=
1218
1219 ! map Prior/Next to F7/F8
1220 tn3270*keysym.0xFF55: \e7
1221 tn3270*keysym.0xFF56: \e8
1222
1223=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
1224How do I make use of them? For example, the Sun Keyboard type 4
1225has the following mappings that rxvt-unicode doesn't recognize.
1226
1227 KP_Insert == Insert
1228 F22 == Print
1229 F27 == Home
1230 F29 == Prior
1231 F33 == End
1232 F35 == Next
1233
1234Rather than have rxvt-unicode try to accomodate all the various possible keyboard
1235mappings, it is better to use `xmodmap' to remap the keys as required for
1236your particular machine.
1237
1238=item How do I distinguish if I'm running rxvt-unicode or a regular xterm?
1239I need this to decide about setting colors etc.
1240
1241rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
1242check and see if that is set. Note that several programs, JED, slrn,
1243Midnight Commander automatically check this variable to decide whether or
1244not to use color.
1245
1246=item How do I set the correct, full IP address for the DISPLAY variable?
1247
1248If you've compiled rxvt-unicode with DISPLAY_IS_IP and ahve enabled
1249insecure mode then it is possible to use the following shell script
1250snippets to correctly set the display. If your version of rxvt-unicode
1251wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
1252the COLORTERM variable can be used to distinguish rxvt-unicode from a
1253regular xterm.
1254
1255Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
1256snippets:
1257
1258 # Bourne/Korn/POSIX family of shells:
1259 [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
1260 if [ ${TERM:-foo} = xterm ]; then
1261 stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
1262 echo -n '^[Z'
1263 read term_id
1264 stty icanon echo
1265 if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
1266 echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
1267 read DISPLAY # set it in our local shell
1268 fi
1269 fi
1270
1271=item How do I compile the manual pages for myself?
1272
1273You need to have a recent version of perl installed as F</usr/bin/perl>,
1274one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
1275the doc subdirectory and enter C<make alldoc>.
1276 1192
1277=back 1193=back
1278 1194
1279=head1 ENVIRONMENT
1280
1281B<@@RXVT_NAME@@> sets the environment variables B<TERM>, B<COLORTERM>
1282and B<COLORFGBG>. The environment variable B<WINDOWID> is set to the X
1283window id number of the B<@@RXVT_NAME@@> window and it also uses and
1284sets the environment variable B<DISPLAY> to specify which display
1285terminal to use. B<@@RXVT_NAME@@> uses the environment variables
1286B<RXVTPATH> and B<PATH> to find XPM files.
1287
1288=head1 FILES 1195=head1 FILES
1289 1196
1290=over 4 1197=over 4
1291 1198
1292=item B</etc/utmp>
1293
1294System file for login records.
1295
1296=item B</usr/lib/X11/rgb.txt> 1199=item B</usr/lib/X11/rgb.txt>
1297 1200
1298Color names. 1201Color names.
1299 1202
1300=back 1203=back
1316=over 4 1219=over 4
1317 1220
1318=item Project Coordinator 1221=item Project Coordinator
1319 1222
1320@@RXVT_MAINT@@ L<@@RXVT_MAINTEMAIL@@> 1223@@RXVT_MAINT@@ L<@@RXVT_MAINTEMAIL@@>
1321
1322=item Web page maintainter
1323
1324@@RXVT_WEBMAINT@@ L<@@RXVT_WEBMAINTEMAIL@@>
1325 1224
1326L<@@RXVT_WEBPAGE@@> 1225L<@@RXVT_WEBPAGE@@>
1327 1226
1328=back 1227=back
1329 1228

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines