… | |
… | |
2 | |
2 | |
3 | rxvt-unicode (ouR XVT, unicode) - (a VT102 emulator for the X window system) |
3 | rxvt-unicode (ouR XVT, unicode) - (a VT102 emulator for the X window system) |
4 | |
4 | |
5 | =head1 SYNOPSIS |
5 | =head1 SYNOPSIS |
6 | |
6 | |
7 | B<@@RXVTNAME@@> [options] [-e command [ args ]] |
7 | B<@@RXVT_NAME@@> [options] [-e command [ args ]] |
8 | |
8 | |
9 | =head1 DESCRIPTION |
9 | =head1 DESCRIPTION |
10 | |
10 | |
11 | B<rxvt-unicode>, version B<@@RXVTVERSION@@>, is a colour vt102 terminal |
11 | B<rxvt-unicode>, version B<@@RXVT_VERSION@@>, is a colour vt102 terminal |
12 | emulator intended as an I<xterm>(1) replacement for users who do not |
12 | emulator intended as an I<xterm>(1) replacement for users who do not |
13 | require features such as Tektronix 4014 emulation and toolkit-style |
13 | require features such as Tektronix 4014 emulation and toolkit-style |
14 | configurability. As a result, B<rxvt-unicode> uses much less swap space -- |
14 | configurability. As a result, B<rxvt-unicode> uses much less swap space -- |
15 | a significant advantage on a machine serving many X sessions. |
15 | a significant advantage on a machine serving many X sessions. |
16 | |
16 | |
|
|
17 | =head1 RXVT-UNICODE VS. RXVT |
|
|
18 | |
|
|
19 | Unlike the original rxvt, B<rxvt-unicode> stores all text in Unicode |
|
|
20 | internally. That means it can store and display most scripts in the |
|
|
21 | world. Being a terminal emulator, however, some things are very difficult, |
|
|
22 | especially cursive scripts such as arabic, vertically written scripts |
|
|
23 | like mongolian or scripts requiring extremely complex combining rules, |
|
|
24 | like tibetan or devenagari. Don't expect pretty output when using these |
|
|
25 | scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work |
|
|
26 | fine, though. A somewhat difficult case are left-to-right scripts, such |
|
|
27 | as hebrew: B<rxvt-unicode> adopts the view that bidirectional algorithms |
|
|
28 | belong into the application, not the terminal emulator (too many things -- |
|
|
29 | such as cursor-movement while editing -- break othwerwise), but that might |
|
|
30 | change. |
|
|
31 | |
|
|
32 | If you are looking for a terminal that supports more exotic scripts, let |
|
|
33 | me recommend C<mlterm>, which is a very userfriendly, lean and clean |
|
|
34 | terminal emulator. In fact, the reason rxvt-unicode was born was solely |
|
|
35 | because the author couldn't get C<mlterm> to use one font for latin1 and |
|
|
36 | another for japanese. |
|
|
37 | |
|
|
38 | Therefore another design rationale was the use of multiple fonts to |
|
|
39 | display characters: The idea of a single unicode font which many other |
|
|
40 | programs force onto it's users never made sense to me: You should be able |
|
|
41 | to choose any font for any script freely. |
|
|
42 | |
|
|
43 | Apart from that, rxvt-unicode is also much better internationalised than |
|
|
44 | it's predecessor, supports things such as XFT and ISO 14755 that are handy |
|
|
45 | in i18n-environments, is faster, and has a lot less bugs than the original |
|
|
46 | rxvt. This all in addition to dozens of other small improvements. |
|
|
47 | |
|
|
48 | It is still faithfully following the original rxvt idea of being lean |
|
|
49 | and nice on resources: for example, you can still configure rxvt-unicode |
|
|
50 | without most of it's features to get a lean binary. It also comes with |
|
|
51 | a client/daemon pair that lets you open any number of terminal windows |
|
|
52 | from within a single process, which makes startup time very fast and |
|
|
53 | drastically reduces memory usage. See @@RXVT_NAME@@d(1) (daemon) and |
|
|
54 | @@RXVT_NAME@@c(1) (client). |
|
|
55 | |
|
|
56 | It also makes technical information about escape sequences (which have |
|
|
57 | been extended) easier accessible: see @@RXVT_NAME@@(7) for technical |
|
|
58 | reference documentation (escape sequences etc.) and the FAQ section at the |
|
|
59 | end of this document. |
|
|
60 | |
17 | =head1 OPTIONS |
61 | =head1 OPTIONS |
18 | |
62 | |
19 | The B<@@RXVTNAME@@> options (mostly a subset of I<xterm>'s) are listed |
63 | The B<@@RXVT_NAME@@> options (mostly a subset of I<xterm>'s) are listed |
20 | below. In keeping with the smaller-is-better philosophy, options may be |
64 | below. In keeping with the smaller-is-better philosophy, options may be |
21 | eliminated or default values chosen at compile-time, so options and |
65 | eliminated or default values chosen at compile-time, so options and |
22 | defaults listed may not accurately reflect the version installed on |
66 | defaults listed may not accurately reflect the version installed on |
23 | your system. `rxvt -h' gives a list of major compile-time options on |
67 | your system. `@@RXVT_NAME@@ -h' gives a list of major compile-time options on |
24 | the I<Options> line. Option descriptions may be prefixed with which |
68 | the I<Options> line. Option descriptions may be prefixed with which |
25 | compile option each is dependent upon. e.g. `Compile I<XIM>:' requires |
69 | compile option each is dependent upon. e.g. `Compile I<XIM>:' requires |
26 | I<XIM> on the I<Options> line. Note: `rxvt -help' gives a list of all |
70 | I<XIM> on the I<Options> line. Note: `@@RXVT_NAME@@ -help' gives a list of all |
27 | command-line options compiled into your version. |
71 | command-line options compiled into your version. |
28 | |
72 | |
29 | Note that B<@@RXVTNAME@@> permits the resource name to be used as a |
73 | Note that B<@@RXVT_NAME@@> permits the resource name to be used as a |
30 | long-option (--/++ option) so the potential command-line options are |
74 | long-option (--/++ option) so the potential command-line options are |
31 | far greater than those listed. For example: `rxvt --loginShell --color1 |
75 | far greater than those listed. For example: `@@RXVT_NAME@@ --loginShell --color1 |
32 | Orange'. |
76 | Orange'. |
33 | |
77 | |
34 | The following options are available: |
78 | The following options are available: |
35 | |
79 | |
36 | =over 4 |
80 | =over 4 |
… | |
… | |
106 | |
150 | |
107 | The mouse pointer background colour; resource B<pointerColor2>. |
151 | The mouse pointer background colour; resource B<pointerColor2>. |
108 | |
152 | |
109 | =item B<-bd> I<colour> |
153 | =item B<-bd> I<colour> |
110 | |
154 | |
111 | The colour of the border between the xterm scrollbar and the text; |
155 | The colour of the border around the text area and between the scrollbar and the text; |
112 | resource B<borderColor>. |
156 | resource B<borderColor>. |
113 | |
157 | |
114 | =item B<-fn> I<fontname> |
158 | =item B<-fn> I<fontlist> |
115 | |
159 | |
116 | Select the fonts to be used. This is a comma seperated list of font |
160 | Select the fonts to be used. This is a comma separated list of font names |
117 | names that are used in turn when trying to display Unicode characters. |
161 | that are used in turn when trying to display Unicode characters. The |
118 | The first font defines the cell size for characters; other fonts might |
162 | first font defines the cell size for characters; other fonts might be |
119 | be smaller, but not larger. A reasonable default font list is always |
163 | smaller, but not (in general) larger. A reasonable default font list is |
120 | appended to it. resource B<font>. |
164 | always appended to it. See resource B<font> for details. |
121 | |
165 | |
122 | =item B<-rb>|B<+rb> |
166 | See also the question "How does rxvt-unicode choose fonts?" in the FAQ |
|
|
167 | section. |
123 | |
168 | |
124 | Enable "real bold" support. When this option is on, bold text will be |
169 | =item B<-fb> I<fontlist> |
125 | displayed using the first available bold font in the font list. Bold |
170 | |
126 | fonts should thus be specified in the font list after their |
171 | Compile font-styles: The bold font list to use when bold characters are to |
127 | corresponding regular fonts. If no bold font can be found, a regular |
172 | be printed. See resource B<boldFont> for details. |
128 | font will be used. resource B<realBold>. |
173 | |
|
|
174 | =item B<-fi> I<fontlist> |
|
|
175 | |
|
|
176 | Compile font-styles: The italic font list to use when bold characters are to |
|
|
177 | be printed. See resource B<italicFont> for details. |
|
|
178 | |
|
|
179 | =item B<-fbi> I<fontlist> |
|
|
180 | |
|
|
181 | Compile font-styles: The bold italic font list to use when bold characters are to |
|
|
182 | be printed. See resource B<boldItalicFont> for details. |
129 | |
183 | |
130 | =item B<-name> I<name> |
184 | =item B<-name> I<name> |
131 | |
185 | |
132 | Specify the application name under which resources are to be obtained, |
186 | Specify the application name under which resources are to be obtained, |
133 | rather than the default executable file name. Name should not contain |
187 | rather than the default executable file name. Name should not contain |
… | |
… | |
202 | B<externalBorder>. |
256 | B<externalBorder>. |
203 | |
257 | |
204 | =item B<-bl> |
258 | =item B<-bl> |
205 | |
259 | |
206 | Compile I<frills>: Set MWM hints to request a borderless window, i.e. |
260 | Compile I<frills>: Set MWM hints to request a borderless window, i.e. |
207 | if honoured by the WM, the rxvt window will not have window |
261 | if honoured by the WM, the rxvt-unicode window will not have window |
208 | decorations; resource B<borderLess>. |
262 | decorations; resource B<borderLess>. |
209 | |
263 | |
210 | =item B<-lsp> I<number> |
264 | =item B<-lsp> I<number> |
211 | |
265 | |
212 | Compile I<linespace>: Lines (pixel height) to insert between each row |
266 | Compile I<linespace>: Lines (pixel height) to insert between each row |
… | |
… | |
219 | I<termcap(5)> database and should have I<li#> and I<co#> entries; |
273 | I<termcap(5)> database and should have I<li#> and I<co#> entries; |
220 | resource B<termName>. |
274 | resource B<termName>. |
221 | |
275 | |
222 | =item B<-e> I<command [arguments]> |
276 | =item B<-e> I<command [arguments]> |
223 | |
277 | |
224 | Run the command with its command-line arguments in the B<@@RXVTNAME@@> |
278 | Run the command with its command-line arguments in the B<@@RXVT_NAME@@> |
225 | window; also sets the window title and icon name to be the basename of |
279 | window; also sets the window title and icon name to be the basename of |
226 | the program being executed if neither I<-title> (I<-T>) nor I<-n> are |
280 | the program being executed if neither I<-title> (I<-T>) nor I<-n> are |
227 | given on the command line. If this option is used, it must be the last |
281 | given on the command line. If this option is used, it must be the last |
228 | on the command-line. If there is no B<-e> option then the default is to |
282 | on the command-line. If there is no B<-e> option then the default is to |
229 | run the program specified by the B<SHELL> environment variable or, |
283 | run the program specified by the B<SHELL> environment variable or, |
… | |
… | |
283 | Turn on/off secondary screen scroll (default enabled); resource |
337 | Turn on/off secondary screen scroll (default enabled); resource |
284 | B<secondaryScroll>. |
338 | B<secondaryScroll>. |
285 | |
339 | |
286 | =item B<-xrm> I<resourcestring> |
340 | =item B<-xrm> I<resourcestring> |
287 | |
341 | |
288 | No effect on rxvt. Simply passes through an argument to be made |
342 | No effect on rxvt-unicode. Simply passes through an argument to be made |
289 | available in the instance's argument list. Appears in I<WM_COMMAND> in |
343 | available in the instance's argument list. Appears in I<WM_COMMAND> in |
290 | some window managers. |
344 | some window managers. |
291 | |
345 | |
292 | =back |
346 | =back |
293 | |
347 | |
294 | =head1 RESOURCES (available also as long-options) |
348 | =head1 RESOURCES (available also as long-options) |
295 | |
349 | |
296 | Note: `@@RXVTNAME@@ --help' gives a list of all resources (long |
350 | Note: `@@RXVT_NAME@@ --help' gives a list of all resources (long |
297 | options) compiled into your version. |
351 | options) compiled into your version. |
298 | |
352 | |
299 | There are two different methods that @@RXVTNAME@@ can use to get the |
353 | There are two different methods that @@RXVT_NAME@@ can use to get the |
300 | Xresource data: using the X libraries (Xrm*-functions) or internal |
354 | Xresource data: using the X libraries (Xrm*-functions) or internal |
301 | Xresources reader (B<~/.Xdefaults>). For the first method (ie. |
355 | Xresources reader (B<~/.Xdefaults>). For the first method (ie. |
302 | B<@@RXVTNAME@@ -h> lists B<XGetDefaults>), you can set and change the |
356 | B<@@RXVT_NAME@@ -h> lists B<XGetDefaults>), you can set and change the |
303 | resources using X11 tools like B<xset>. Many distribution do also load |
357 | resources using X11 tools like B<xset>. Many distribution do also load |
304 | settings from the B<~/.Xresources> file when X starts. |
358 | settings from the B<~/.Xresources> file when X starts. |
305 | |
359 | |
306 | If compiled with internal Xresources support (i.e. B<@@RXVTNAME@@ -h> |
360 | If compiled with internal Xresources support (i.e. B<@@RXVT_NAME@@ -h> |
307 | lists B<.Xdefaults>) then B<@@RXVTNAME@@> accepts application defaults |
361 | lists B<.Xdefaults>) then B<@@RXVT_NAME@@> accepts application defaults |
308 | set in XAPPLOADDIR/URxvt (compile-time defined: usually |
362 | set in XAPPLOADDIR/URxvt (compile-time defined: usually |
309 | B</usr/lib/X11/app-defaults/URxvt>) and resources set in |
363 | B</usr/lib/X11/app-defaults/URxvt>) and resources set in |
310 | B<~/.Xdefaults>, or B<~/.Xresources> if B<~/.Xdefaults> does not exist. |
364 | B<~/.Xdefaults>, or B<~/.Xresources> if B<~/.Xdefaults> does not exist. |
311 | Note that when reading X resources, B<@@RXVTNAME@@> recognizes two |
365 | Note that when reading X resources, B<@@RXVT_NAME@@> recognizes two |
312 | class names: B<XTerm> and B<URxvt>. The class name B<Rxvt> allows |
366 | class names: B<XTerm> and B<URxvt>. The class name B<Rxvt> allows |
313 | resources common to both B<@@RXVTNAME@@> and the original I<rxvt> to be |
367 | resources common to both B<@@RXVT_NAME@@> and the original I<rxvt> to be |
314 | easily configured, while the class name B<URxvt> allows resources |
368 | easily configured, while the class name B<URxvt> allows resources |
315 | unique to B<@@RXVTNAME@@>, notably colours and key-handling, to be |
369 | unique to B<@@RXVT_NAME@@>, notably colours and key-handling, to be |
316 | shared between different B<@@RXVTNAME@@> configurations. If no |
370 | shared between different B<@@RXVT_NAME@@> configurations. If no |
317 | resources are specified, suitable defaults will be used. Command-line |
371 | resources are specified, suitable defaults will be used. Command-line |
318 | arguments can be used to override resource settings. The following |
372 | arguments can be used to override resource settings. The following |
319 | resources are allowed: |
373 | resources are allowed: |
320 | |
374 | |
321 | =over 4 |
375 | =over 4 |
… | |
… | |
342 | high-intensity (bold = bright foreground, blink = bright background) |
396 | high-intensity (bold = bright foreground, blink = bright background) |
343 | colours. The canonical names are as follows: 0=black, 1=red, 2=green, |
397 | colours. The canonical names are as follows: 0=black, 1=red, 2=green, |
344 | 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour |
398 | 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour |
345 | names used are listed in the B<COLORS AND GRAPHICS> section. |
399 | names used are listed in the B<COLORS AND GRAPHICS> section. |
346 | |
400 | |
|
|
401 | Colours higher than 15 cannot be set using resources (yet), but can be |
|
|
402 | changed using an escape command (see @@RXVT_NAME@@(7)). |
|
|
403 | |
|
|
404 | Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with |
|
|
405 | 88 colour support). Colours 80-87 are evenly spaces grey steps. |
|
|
406 | |
347 | =item B<colorBD:> I<colour> |
407 | =item B<colorBD:> I<colour> |
348 | |
408 | |
|
|
409 | =item B<colorIT:> I<colour> |
|
|
410 | |
349 | Use the specified colour to display bold characters when the foreground |
411 | Use the specified colour to display bold or italic characters when the |
350 | colour is the default. This option will be ignored if B<realBold> is |
412 | foreground colour is the default. If font styles are not available |
351 | enabled. |
413 | (Compile styles) and this option is unset, reverse video is used instead. |
352 | |
414 | |
353 | =item B<colorUL:> I<colour> |
415 | =item B<colorUL:> I<colour> |
354 | |
416 | |
355 | Use the specified colour to display underlined characters when the |
417 | Use the specified colour to display underlined characters when the |
356 | foreground colour is the default. |
418 | foreground colour is the default. |
… | |
… | |
412 | |
474 | |
413 | =item B<troughColor:> I<colour> |
475 | =item B<troughColor:> I<colour> |
414 | |
476 | |
415 | Use the specified colour for the scrollbar's trough area [default |
477 | Use the specified colour for the scrollbar's trough area [default |
416 | #969696]. Only relevant for normal (non XTerm/NeXT) scrollbar. |
478 | #969696]. Only relevant for normal (non XTerm/NeXT) scrollbar. |
|
|
479 | |
|
|
480 | =item B<borderColor:> I<colour> |
|
|
481 | |
|
|
482 | The colour of the border around the text area and between the scrollbar |
|
|
483 | and the text. |
417 | |
484 | |
418 | =item B<backgroundPixmap:> I<file[;geom]> |
485 | =item B<backgroundPixmap:> I<file[;geom]> |
419 | |
486 | |
420 | Use the specified XPM file (note the `.xpm' extension is optional) for |
487 | Use the specified XPM file (note the `.xpm' extension is optional) for |
421 | the background and also optionally specify its scaling with a geometry |
488 | the background and also optionally specify its scaling with a geometry |
… | |
… | |
437 | |
504 | |
438 | Specify the colon-delimited search path for finding files (XPM and |
505 | Specify the colon-delimited search path for finding files (XPM and |
439 | menus), in addition to the paths specified by the B<RXVTPATH> and |
506 | menus), in addition to the paths specified by the B<RXVTPATH> and |
440 | B<PATH> environment variables. |
507 | B<PATH> environment variables. |
441 | |
508 | |
442 | =item B<font:> I<fontname> |
509 | =item B<font:> I<fontlist> |
443 | |
510 | |
444 | Select the fonts to be used. This is a comma seperated list of font |
511 | Select the fonts to be used. This is a comma separated list of font |
445 | names that are used in turn when trying to display Unicode characters. |
512 | names that are used in turn when trying to display Unicode characters. |
446 | The first font defines the cell size for characters; other fonts might |
513 | The first font defines the cell size for characters; other fonts might |
447 | be smaller, but not larger. A reasonable default font list is always |
514 | be smaller, but not larger. A reasonable default font list is always |
448 | appended to it. option B<-fn>. |
515 | appended to it. option B<-fn>. |
449 | |
516 | |
450 | =item B<realBold:> I<boolean> |
517 | Each font can either be a standard X11 core font (XLFD) name, with |
|
|
518 | optional prefix C<x:> or a Xft font (Compile xft), prefixed with C<xft:>. |
451 | |
519 | |
452 | B<True>: Enable "real bold" support. When this option is on, bold text |
520 | In addition, each font can be prefixed with additional hints and |
453 | will be displayed using the first available bold font in the font list. |
521 | specifications enclosed in square brackets (C<[]>). The only available |
454 | Bold fonts should thus be specified in the font list after their |
522 | hint currently is C<codeset=codeset-name>, and this is only used for Xft |
455 | corresponding regular fonts. If no bold font can be found, a regular |
523 | fonts. |
456 | font will be used. option B<-rb>. B<False>: Display bold text in a |
524 | |
457 | regular font, using the color specified with B<colorBD>; option B<+rb>. |
525 | For example, this font resource |
|
|
526 | |
|
|
527 | URxvt*font: 9x15bold,\ |
|
|
528 | -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\ |
|
|
529 | -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \ |
|
|
530 | [codeset=JISX0208]xft:Kochi Gothic:antialias=false, \ |
|
|
531 | xft:Code2000:antialias=false |
|
|
532 | |
|
|
533 | specifies five fonts to be used. The first one is C<9x15bold> (actually |
|
|
534 | the iso8859-1 version of the second font), which is the base font (because |
|
|
535 | it is named first) and thus defines the character cell grid to be 9 pixels |
|
|
536 | wide and 15 pixels high. |
|
|
537 | |
|
|
538 | the second font is just used to add additional unicode characters not in |
|
|
539 | the base font, likewise the third, which is unfortunately non-bold, but |
|
|
540 | the bold version of the font does contain less characters, so this is a |
|
|
541 | useful supplement. |
|
|
542 | |
|
|
543 | The third font is an Xft font with aliasing turned off, and the characters |
|
|
544 | are limited to the B<JIS 0208> codeset (i.e. japanese kanji). The font |
|
|
545 | contains other characters, but we are not interested in them. |
|
|
546 | |
|
|
547 | The last font is a useful catch-all font that supplies most of the |
|
|
548 | remaining unicode characters. |
|
|
549 | |
|
|
550 | =item B<boldFont:> I<fontlist> |
|
|
551 | |
|
|
552 | =item B<italicFont:> I<fontlist> |
|
|
553 | |
|
|
554 | =item B<boldItalicFont:> I<fontlist> |
|
|
555 | |
|
|
556 | The font list to use for displaying B<bold>, I<italic> or B<< I<bold |
|
|
557 | italic> >> characters, respectively. |
|
|
558 | |
|
|
559 | If specified and non-empty, then the syntax is the same as for the |
|
|
560 | B<font>-resource, and the given font list will be used as is, which makes |
|
|
561 | it possible to substitute completely different font styles for bold and |
|
|
562 | italic. |
|
|
563 | |
|
|
564 | If unset (the default), a suitable font list will be synthesized by |
|
|
565 | "morphing" the normal text font list into the desired shape. If that is |
|
|
566 | not possible, replacement fonts of the desired shape will be tried. |
|
|
567 | |
|
|
568 | If set, but empty, then this specific style is disabled and the normal |
|
|
569 | text font will being used for the given style. |
458 | |
570 | |
459 | =item B<selectstyle:> I<mode> |
571 | =item B<selectstyle:> I<mode> |
460 | |
572 | |
461 | Set mouse selection style to B<old> which is 2.20, B<oldword> which is |
573 | Set mouse selection style to B<old> which is 2.20, B<oldword> which is |
462 | xterm style with 2.20 old word selection, or anything else which gives |
574 | xterm style with 2.20 old word selection, or anything else which gives |
463 | xterm style selection. |
575 | xterm style selection. |
464 | |
576 | |
465 | =item B<scrollstyle:> I<mode> |
577 | =item B<scrollstyle:> I<mode> |
466 | |
578 | |
467 | Set scrollbar style to B<@@RXVTNAME@@>, B<rxvt>, B<plain>, B<next> or |
579 | Set scrollbar style to B<rxvt>, B<plain>, B<next> or B<xterm>. B<plain> is |
468 | B<xterm> |
580 | the author's favourite.. |
469 | |
581 | |
470 | =item B<title:> I<string> |
582 | =item B<title:> I<string> |
471 | |
583 | |
472 | Set window title string, the default title is the command-line |
584 | Set window title string, the default title is the command-line |
473 | specified after the B<-e> option, if any, otherwise the application |
585 | specified after the B<-e> option, if any, otherwise the application |
… | |
… | |
527 | Align the B<top>, B<bottom> or B<centre> [default] of the scrollbar |
639 | Align the B<top>, B<bottom> or B<centre> [default] of the scrollbar |
528 | thumb with the pointer on middle button press/drag. |
640 | thumb with the pointer on middle button press/drag. |
529 | |
641 | |
530 | =item B<scrollTtyOutput:> I<boolean> |
642 | =item B<scrollTtyOutput:> I<boolean> |
531 | |
643 | |
532 | B<True>: scroll to bottom when tty receives output; option B<+si>. |
644 | B<True>: scroll to bottom when tty receives output; option B<-si>. |
533 | B<False>: do not scroll to bottom when tty receives output; option |
645 | B<False>: do not scroll to bottom when tty receives output; option |
534 | B<-si>. |
646 | B<+si>. |
535 | |
647 | |
536 | =item B<scrollWithBuffer:> I<boolean> |
648 | =item B<scrollWithBuffer:> I<boolean> |
537 | |
649 | |
538 | B<True>: scroll with scrollback buffer when tty recieves new lines (and |
650 | B<True>: scroll with scrollback buffer when tty recieves new lines (and |
539 | B<scrollTtyOutput> is False); option B<+sw>. B<False>: do not scroll |
651 | B<scrollTtyOutput> is False); option B<+sw>. B<False>: do not scroll |
540 | with scrollback buffer when tty recieves new lines; option B<-sw>. |
652 | with scrollback buffer when tty recieves new lines; option B<-sw>. |
541 | |
653 | |
542 | =item B<scrollTtyKeypress:> I<boolean> |
654 | =item B<scrollTtyKeypress:> I<boolean> |
543 | |
655 | |
544 | B<True>: scroll to bottom when a non-special key is pressed. Special |
656 | B<True>: scroll to bottom when a non-special key is pressed. Special keys |
545 | keys are those which are intercepted by rxvt for special handling and |
657 | are those which are intercepted by rxvt-unicode for special handling and |
546 | are not passed onto the shell; option B<-sk>. B<False>: do not scroll |
658 | are not passed onto the shell; option B<-sk>. B<False>: do not scroll to |
547 | to bottom when a non-special key is pressed; option B<+sk>. |
659 | bottom when a non-special key is pressed; option B<+sk>. |
548 | |
|
|
549 | =item B<smallfont_key:> I<keysym> |
|
|
550 | |
|
|
551 | If enabled, use B<@@HOTKEY@@->I<keysym> to toggle to a smaller font |
|
|
552 | [default B<@@HOTKEY@@-@@SMALLFONT@@>] |
|
|
553 | |
|
|
554 | =item B<bigfont_key:> I<keysym> |
|
|
555 | |
|
|
556 | If enabled, use B<@@HOTKEY@@->I<keysym> to toggle to a bigger font |
|
|
557 | [default B<@@HOTKEY@@-@@BIGFONT@@>] |
|
|
558 | |
660 | |
559 | =item B<saveLines:> I<number> |
661 | =item B<saveLines:> I<number> |
560 | |
662 | |
561 | Save I<number> lines in the scrollback buffer [default 64]. This |
663 | Save I<number> lines in the scrollback buffer [default 64]. This |
562 | resource is limited on most machines to 65535; option B<-sl>. |
664 | resource is limited on most machines to 65535; option B<-sl>. |
… | |
… | |
572 | option B<-w>, B<-bw>, B<-borderwidth>. |
674 | option B<-w>, B<-bw>, B<-borderwidth>. |
573 | |
675 | |
574 | =item B<borderLess:> I<boolean> |
676 | =item B<borderLess:> I<boolean> |
575 | |
677 | |
576 | Set MWM hints to request a borderless window, i.e. if honoured by the |
678 | Set MWM hints to request a borderless window, i.e. if honoured by the |
577 | WM, the rxvt window will not have window decorations; option B<-bl>. |
679 | WM, the rxvt-unicode window will not have window decorations; option B<-bl>. |
578 | |
680 | |
579 | =item B<termName:> I<termname> |
681 | =item B<termName:> I<termname> |
580 | |
682 | |
581 | Specifies the terminal type name to be set in the B<TERM> environment |
683 | Specifies the terminal type name to be set in the B<TERM> environment |
582 | variable; option B<-tn>. |
684 | variable; option B<-tn>. |
… | |
… | |
652 | The locale to use for opening the IM. You can use an LC_CTYPE of e.g. |
754 | The locale to use for opening the IM. You can use an LC_CTYPE of e.g. |
653 | de_DE.UTF-8 for normal text processing but ja_JP.EUC-JP for the input |
755 | de_DE.UTF-8 for normal text processing but ja_JP.EUC-JP for the input |
654 | extension to be able to input japanese characters while staying in |
756 | extension to be able to input japanese characters while staying in |
655 | another locale. option B<-imlocale>. |
757 | another locale. option B<-imlocale>. |
656 | |
758 | |
657 | =item B<insecure> |
759 | =item B<insecure:> I<boolean> |
658 | |
760 | |
659 | Enables "insecure" mode. Rxvt-unicode offers some escape sequences that |
761 | Enables "insecure" mode. Rxvt-unicode offers some escape sequences that |
660 | echo arbitrary strings like the icon name or the locale. This could be |
762 | echo arbitrary strings like the icon name or the locale. This could be |
661 | abused if somebody gets 8-bit-clean access to your display, wether |
763 | abused if somebody gets 8-bit-clean access to your display, wether |
662 | throuh a mail client displaying mail bodies unfiltered or though |
764 | throuh a mail client displaying mail bodies unfiltered or though |
… | |
… | |
673 | B<hyper>, B<super>, B<mod1>, B<mod2>, B<mod3>, B<mod4>, B<mod5>; option |
775 | B<hyper>, B<super>, B<mod1>, B<mod2>, B<mod3>, B<mod4>, B<mod5>; option |
674 | B<-mod>. |
776 | B<-mod>. |
675 | |
777 | |
676 | =item B<answerbackString:> I<string> |
778 | =item B<answerbackString:> I<string> |
677 | |
779 | |
678 | Specify the reply rxvt sends to the shell when an ENQ (control-E) |
780 | Specify the reply rxvt-unicode sends to the shell when an ENQ (control-E) |
679 | character is passed through. It may contain escape values as described |
781 | character is passed through. It may contain escape values as described |
680 | in the entry on B<keysym> following. |
782 | in the entry on B<keysym> following. |
681 | |
783 | |
682 | =item B<secondaryScreen:> I<bool> |
784 | =item B<secondaryScreen:> I<bool> |
683 | |
785 | |
… | |
… | |
703 | |
805 | |
704 | =back |
806 | =back |
705 | |
807 | |
706 | =head1 THE SCROLLBAR |
808 | =head1 THE SCROLLBAR |
707 | |
809 | |
708 | Lines of text that scroll off the top of the B<@@RXVTNAME@@> window |
810 | Lines of text that scroll off the top of the B<@@RXVT_NAME@@> window |
709 | (resource: B<saveLines>) and can be scrolled back using the scrollbar |
811 | (resource: B<saveLines>) and can be scrolled back using the scrollbar |
710 | or by keystrokes. The normal B<@@RXVTNAME@@> scrollbar has arrows and |
812 | or by keystrokes. The normal B<@@RXVT_NAME@@> scrollbar has arrows and |
711 | its behaviour is fairly intuitive. The B<xterm-scrollbar> is without |
813 | its behaviour is fairly intuitive. The B<xterm-scrollbar> is without |
712 | arrows and its behaviour mimics that of I<xterm> |
814 | arrows and its behaviour mimics that of I<xterm> |
713 | |
815 | |
714 | Scroll down with B<Button1> (B<xterm-scrollbar>) or B<Shift-Next>. |
816 | Scroll down with B<Button1> (B<xterm-scrollbar>) or B<Shift-Next>. |
715 | Scroll up with B<Button3> (B<xterm-scrollbar>) or B<Shift-Prior>. |
817 | Scroll up with B<Button3> (B<xterm-scrollbar>) or B<Shift-Prior>. |
… | |
… | |
743 | line. |
845 | line. |
744 | |
846 | |
745 | =item B<Insertion>: |
847 | =item B<Insertion>: |
746 | |
848 | |
747 | Pressing and releasing the Middle mouse button (or B<Shift-Insert>) in |
849 | Pressing and releasing the Middle mouse button (or B<Shift-Insert>) in |
748 | an B<@@RXVTNAME@@> window causes the current text selection to be |
850 | an B<@@RXVT_NAME@@> window causes the current text selection to be |
749 | inserted as if it had been typed on the keyboard. |
851 | inserted as if it had been typed on the keyboard. |
750 | |
852 | |
751 | =back |
853 | =back |
752 | |
854 | |
753 | =head1 CHANGING FONTS |
855 | =head1 CHANGING FONTS |
754 | |
856 | |
755 | You can change fonts on-the-fly, which is to say cycle through the |
857 | Changing fonts (or font sizes, respectively) via the keypad is not yet |
756 | default font and others of various sizes, by using B<Shift-KP_Add> and |
858 | supported in rxvt-unicode. Bug me if you need this. |
757 | B<Shift-KP_Subtract>. Or, alternatively (if enabled) with |
859 | |
758 | B<@@HOTKEY@@-@@BIGFONT@@> and B<@@HOTKEY@@-@@SMALLFONT@@>, where the |
860 | You can, however, switch fonts at runtime using escape sequences (and |
759 | actual key can be selected using resources |
861 | therefore using the menubar), e.g.: |
760 | B<smallfont_key>/B<bigfont_key>. |
862 | |
|
|
863 | printf '\e]701;%s\007' "9x15bold,xft:Kochi Gothic" |
|
|
864 | |
|
|
865 | rxvt-unicode will automatically re-apply these fonts to the output so far. |
|
|
866 | |
|
|
867 | =head1 ISO 14755 SUPPORT |
|
|
868 | |
|
|
869 | ISO 14755 is a standard for entering and viewing unicode characters |
|
|
870 | and character codes using the keyboard. It consists of 4 parts. The |
|
|
871 | first part is available rxvt-unicode has been compiled with |
|
|
872 | C<--enable-frills>, the rest is available when rxvt-unicode was compiled |
|
|
873 | with C<--enable-iso14755>. |
|
|
874 | |
|
|
875 | =over 4 |
|
|
876 | |
|
|
877 | =item 5.1: Basic method |
|
|
878 | |
|
|
879 | This allows you to enter unicode characters using their hexcode. |
|
|
880 | |
|
|
881 | Start by pressing and holding both C<Control> and C<Shift>, then enter |
|
|
882 | hex-digits (between one and six). Releasing C<Control> and C<Shift> will |
|
|
883 | commit the character as if it were typed directly. While holding down |
|
|
884 | C<Control> and C<Shift> you can also enter multiple characters by pressing |
|
|
885 | C<Space>, which will commit the current character and lets you start a new |
|
|
886 | one. |
|
|
887 | |
|
|
888 | As an example of use, imagine a business card with a japanese e-mail |
|
|
889 | address, which you cannot type. Fortunately, the card has the e-mail |
|
|
890 | address printed as hexcodes, e.g. C<671d 65e5>. You can enter this easily |
|
|
891 | by pressing C<Control> and C<Shift>, followed by C<6-7-1-D-SPACE-6-5-E-5>, |
|
|
892 | followed by releasing the modifier keys. |
|
|
893 | |
|
|
894 | =item 5.2: Keyboard symbols entry method |
|
|
895 | |
|
|
896 | This mode lets you input characters representing the keycap symbols of |
|
|
897 | your keyboard, if representable in the current locale encoding. |
|
|
898 | |
|
|
899 | Start by pressing C<Control> and C<Shift> together, then releasing |
|
|
900 | them. The next special key (cursor keys, home etc.) you enter will not |
|
|
901 | invoke it's usual function but instead will insert the corresponding |
|
|
902 | keycap symbol. The symbol will only be entered when the key has been |
|
|
903 | released, otherwise pressing e.g. C<Shift> would enter the symbol for |
|
|
904 | C<ISO Level 2 Switch>, although your intention might have beenm to enter a |
|
|
905 | reverse tab (Shift-Tab). |
|
|
906 | |
|
|
907 | =item 5.3: Screen-selection entry method |
|
|
908 | |
|
|
909 | While this is implemented already (it's basically the selection |
|
|
910 | mechanism), it could be extended by displaying a unicode character map. |
|
|
911 | |
|
|
912 | =item 5.4: Feedback method for identifying displayed characters for later input |
|
|
913 | |
|
|
914 | This method lets you display the unicode character code associated with |
|
|
915 | characters already displayed. |
|
|
916 | |
|
|
917 | You enter this mode by holding down C<Control> and C<Shift> together, then |
|
|
918 | pressing and holding the left mouse button and moving around. The unicode |
|
|
919 | hex code(s) (it might be a combining character) of the character under the |
|
|
920 | pointer is displayed until you release C<Control> and C<Shift>. |
|
|
921 | |
|
|
922 | In addition to the hex codes it will display the font used to draw this |
|
|
923 | character - due to implementation reasons, characters combined with |
|
|
924 | combining characters, line drawing characters and unknown characters will |
|
|
925 | always be drawn using the built-in support font. |
|
|
926 | |
|
|
927 | =back |
|
|
928 | |
|
|
929 | With respect to conformance, rxvt-unicode is supposed to be compliant to |
|
|
930 | both scenario A and B of ISO 14755, including part 5.2. |
761 | |
931 | |
762 | =head1 LOGIN STAMP |
932 | =head1 LOGIN STAMP |
763 | |
933 | |
764 | B<@@RXVTNAME@@> tries to write an entry into the I<utmp>(5) file so |
934 | B<@@RXVT_NAME@@> tries to write an entry into the I<utmp>(5) file so |
765 | that it can be seen via the I<who(1)> command, and can accept messages. |
935 | that it can be seen via the I<who(1)> command, and can accept messages. |
766 | To allow this feature, B<@@RXVTNAME@@> must be installed setuid root on |
936 | To allow this feature, B<@@RXVT_NAME@@> must be installed setuid root on |
767 | some systems. |
937 | some systems. |
768 | |
938 | |
769 | =head1 COLORS AND GRAPHICS |
939 | =head1 COLORS AND GRAPHICS |
770 | |
940 | |
771 | In addition to the default foreground and background colours, |
941 | In addition to the default foreground and background colours, |
772 | B<@@RXVTNAME@@> can display up to 16 colours (8 ANSI colours plus |
942 | B<@@RXVT_NAME@@> can display up to 16 colours (8 ANSI colours plus |
773 | high-intensity bold/blink versions of the same). Here is a list of the |
943 | high-intensity bold/blink versions of the same). Here is a list of the |
774 | colours with their B<rgb.txt> names. |
944 | colours with their B<rgb.txt> names. |
775 | |
945 | |
776 | =begin table |
946 | =begin table |
777 | |
947 | |
… | |
… | |
806 | I<xterm>(1) where the colours are only swapped if they have not otherwise |
976 | I<xterm>(1) where the colours are only swapped if they have not otherwise |
807 | been specified. For example, |
977 | been specified. For example, |
808 | |
978 | |
809 | =over 4 |
979 | =over 4 |
810 | |
980 | |
811 | =item B<rxvt -fg Black -bg White -rv> |
981 | =item B<@@RXVT_NAME@@ -fg Black -bg White -rv> |
812 | |
982 | |
813 | would yield White on Black, while on I<xterm>(1) it would yield Black |
983 | would yield White on Black, while on I<xterm>(1) it would yield Black |
814 | on White. |
984 | on White. |
815 | |
985 | |
816 | =back |
986 | =back |
817 | |
987 | |
|
|
988 | =head1 FREQUENTLY ASKED QUESTIONS (FAQ) |
|
|
989 | |
|
|
990 | =over 4 |
|
|
991 | |
|
|
992 | =item How do I know which rxvt-unicode version I'm using? |
|
|
993 | |
|
|
994 | The version number is displayed with the usage (-h). Also the escape |
|
|
995 | sequence C<ESC[8n> sets the window title to the version number. |
|
|
996 | |
|
|
997 | =item When I log-in to another system it tells me about missing terminfo data? |
|
|
998 | |
|
|
999 | The terminal description used by rxvt-unicode is not as widely available |
|
|
1000 | as that for xterm, or even rxvt (for which the same problem often arises). |
|
|
1001 | |
|
|
1002 | The correct solution for this problem is to install the terminfo, this can be done |
|
|
1003 | like this: |
|
|
1004 | |
|
|
1005 | infocmp rxvt-unicode >rxvt.unicode.tic |
|
|
1006 | scp rxvt-unicode.tic remotesystem: |
|
|
1007 | ssh remotesystem tic rxvt-unicode.tic |
|
|
1008 | |
|
|
1009 | ... or by installing rxvt-unicode normally on the remote system, |
|
|
1010 | |
|
|
1011 | If you cannot or do not want to do this, then you can simply set |
|
|
1012 | C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of |
|
|
1013 | problems arising, which includes wrong keymapping, less and different |
|
|
1014 | colours and some refresh errors in fullscreen applications. It's a nice |
|
|
1015 | quick-and-dirty workaround for rare cases, though. |
|
|
1016 | |
|
|
1017 | If you always want to do this you can either recompile rxvt-unicode with |
|
|
1018 | the desired TERM value or use a resource to set it: |
|
|
1019 | |
|
|
1020 | URxvt.termName: rxvt |
|
|
1021 | |
|
|
1022 | =item How can I configure rxvt-unicode so that it looks similar to the original rxvt? |
|
|
1023 | |
|
|
1024 | Felix von Leitner says that these two lines, in your F<.Xdefaults>, will make rxvt-unicode |
|
|
1025 | behave similar to the original rxvt: |
|
|
1026 | |
|
|
1027 | URxvt.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1 |
|
|
1028 | URxvt.boldFont: -misc-fixed-bold-r-semicondensed--13-120-75-75-c-60-iso8859-1 |
|
|
1029 | |
|
|
1030 | =item Rxvt-unicode does not seem to understand the selected encoding? |
|
|
1031 | |
|
|
1032 | =item Unicode does not seem to work? |
|
|
1033 | |
|
|
1034 | If you encounter strange problems like typing an accented character but |
|
|
1035 | getting two unrelated other characters or similar, or if program output is |
|
|
1036 | subtly garbled, then you should check your locale settings. |
|
|
1037 | |
|
|
1038 | Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the |
|
|
1039 | programs. Often rxvt-unicode is started in the C<C> locale, while the |
|
|
1040 | login script running within the rxvt-unicode window changes the locale to |
|
|
1041 | sth. else, e.h. C<en_GB.UTF-8>. Needless to say, this is not going to work. |
|
|
1042 | |
|
|
1043 | The best thing is to fix your startup environment, as you will likely run |
|
|
1044 | into other problems. If nothing works you can try this in your .profile. |
|
|
1045 | |
|
|
1046 | printf '\e]701;%s\007' "$LC_CTYPE" |
|
|
1047 | |
|
|
1048 | If this doesn't work, then maybe you use a C<LC_CTYPE> specification not |
|
|
1049 | supported on your systems. Some systems have a C<locale> comamnd which |
|
|
1050 | displays this. If it displays sth. like: |
|
|
1051 | |
|
|
1052 | locale: Cannot set LC_CTYPE to default locale: ... |
|
|
1053 | |
|
|
1054 | Then the locale you specified is not supported on your system. |
|
|
1055 | |
|
|
1056 | If nothing works and you are sure that everything is set correctly then |
|
|
1057 | you will need to remember a little known fact: Some programs just don't |
|
|
1058 | support locales :( |
|
|
1059 | |
|
|
1060 | =item Why do the characters look ugly? |
|
|
1061 | |
|
|
1062 | =item How does rxvt-unicode choose fonts? |
|
|
1063 | |
|
|
1064 | Most fonts do not contain the full range of Unicode, which is |
|
|
1065 | fine. Chances are that the font you (or the admin/package maintainer of |
|
|
1066 | your system/os) have specified does not cover all the characters you want |
|
|
1067 | to display. |
|
|
1068 | |
|
|
1069 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
|
|
1070 | font. Often the result is fine, but sometimes the chosen font looks |
|
|
1071 | bad. Many fonts have totally strange characters that don't resemble the |
|
|
1072 | correct glyph at all, and rxvt-unicode lacks the artificial intelligence |
|
|
1073 | to detetc that a specific glyph is wrong: it has to believe the font that |
|
|
1074 | the characters it contains indeed look correct. |
|
|
1075 | |
|
|
1076 | In that case, select a font of your taste and add it to the font list, |
|
|
1077 | e.g.: |
|
|
1078 | |
|
|
1079 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
|
|
1080 | |
|
|
1081 | When rxvt-unicode sees a character, it will first look at the base |
|
|
1082 | font. If the base font does not contain the character, it will go to the |
|
|
1083 | next font, and so on. Specifying your own fonts will also speed up this |
|
|
1084 | search and use less resources within rxvt-unicode and the X-server. |
|
|
1085 | |
|
|
1086 | The only limitation is that all the fonts must not be larger than the base |
|
|
1087 | font, as the base font defines the principial cell size, which must be the |
|
|
1088 | same due to the way terminals work. |
|
|
1089 | |
|
|
1090 | =item Why do some chinese characters look so different than others? |
|
|
1091 | |
|
|
1092 | This is because there is a difference between script and language -- |
|
|
1093 | rxvt-unicode does not know which language the text that is output |
|
|
1094 | is, as it only knows the unicode character codes. If rxvt-unicode |
|
|
1095 | first sees a japanese character, it might choose a japanese font for |
|
|
1096 | it. Subseqzuent japanese characters will take that font. Now, many chinese |
|
|
1097 | characters aren't represented in japanese fonts, so when the first |
|
|
1098 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
1099 | -- unfortunately at this point, it will still use the japanese font for |
|
|
1100 | japanese characters that are also chinese. |
|
|
1101 | |
|
|
1102 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
1103 | list (see the previous question). The key is to view the font list as |
|
|
1104 | a preference list: If you expect more japanese, list a japanese font |
|
|
1105 | first. If you expect more chinese, put a chinese font first. |
|
|
1106 | |
|
|
1107 | In the future it might be possible to switch preferences at runtime (the |
|
|
1108 | internal data structure has no problem with using different fonts for |
|
|
1109 | the same character at the same time, but no interface for this has been |
|
|
1110 | designed yet). |
|
|
1111 | |
|
|
1112 | =item How can I keep rxvt-unicode from using reverse video so much? |
|
|
1113 | |
|
|
1114 | First of all, make sure you are running with the right terminfo |
|
|
1115 | (C<urxvt>), which will get rid of most of these effects. Then make sure |
|
|
1116 | you have specified colours for italic and bold, as otherwise rxvt-unicode |
|
|
1117 | might use reverse video to simulate the effect: |
|
|
1118 | |
|
|
1119 | URxvt*colorBD: white |
|
|
1120 | URxvt*colorIT: green |
|
|
1121 | |
|
|
1122 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
|
|
1123 | |
|
|
1124 | For some unexplainable reason, some programs (i.e. irssi) assume a very |
|
|
1125 | weird colour palette when confronted with a terminal with more than the |
|
|
1126 | standard 8 colours (rxvt-unicode supports 88). The right fix is, of |
|
|
1127 | course, to fix these programs not to assume non-ISO colours without very |
|
|
1128 | good reasons. |
|
|
1129 | |
|
|
1130 | In the meantime, you can either edit your C<urxvt> terminfo definition to |
|
|
1131 | only claim 8 colour support or use C<TERM=rxvt>, which will fix colours |
|
|
1132 | but keep you from using other rxvt-unicode features. |
|
|
1133 | |
|
|
1134 | =item How does rxvt-unicode determine the encoding to use? |
|
|
1135 | |
|
|
1136 | =item Is there an option to switch encodings? |
|
|
1137 | |
|
|
1138 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
|
|
1139 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
|
|
1140 | UTF-8 or any other encodings with respect to terminal I/O. |
|
|
1141 | |
|
|
1142 | The reasons is that there exists a perfectly fine mechanism for selecting |
|
|
1143 | the encoding, doing I/O and (most important) communicating this to all |
|
|
1144 | applications so everybody agrees on character properties such as width and |
|
|
1145 | code number. This mechanism is the I<locale>. |
|
|
1146 | |
|
|
1147 | Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All |
|
|
1148 | programs doing the same (that is, most) will automatically agree in the |
|
|
1149 | interpretation of characters. |
|
|
1150 | |
|
|
1151 | Unfortunately, there is no system-independent way to select locales, nor |
|
|
1152 | is there a standard on how locale specifiers will look like. |
|
|
1153 | |
|
|
1154 | On most systems, the content of the C<LC_CTYPE> environment variable |
|
|
1155 | contains an arbitrary string which corresponds to an already-installed |
|
|
1156 | locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>, |
|
|
1157 | C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms |
|
|
1158 | (i.e. C<de> or C<german>) are also common. |
|
|
1159 | |
|
|
1160 | Rxvt-unicode ignores all other locale categories, and except for |
|
|
1161 | the encoding, ignores country or language-specific settings, |
|
|
1162 | i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the same for rxvt-unicode. |
|
|
1163 | |
|
|
1164 | If you want to use a specific encoding you have to make sure you start |
|
|
1165 | rxvt-unicode with the correct C<LC_CTYPE> category. |
|
|
1166 | |
|
|
1167 | =item Can I switch locales at runtime? |
|
|
1168 | |
|
|
1169 | Yes, using an escape sequence. Try sth. like this, which sets |
|
|
1170 | rxvt-unicode's idea of C<LC_CTYPE>. |
|
|
1171 | |
|
|
1172 | printf '\e]701;%s\007' ja_JP.SJIS |
|
|
1173 | |
|
|
1174 | See also the previous question. |
|
|
1175 | |
|
|
1176 | Sometimes this capability is rather handy when you want to work in one |
|
|
1177 | locale (e.g. C<de_DE.UTF-8>) but some programs don't support UTF-8. For |
|
|
1178 | example, I use this script to start C<xjdic>, which first switches to a |
|
|
1179 | locale supported by xjdic and back later: |
|
|
1180 | |
|
|
1181 | printf '\e]701;%s\007' ja_JP.SJIS |
|
|
1182 | xjdic -js |
|
|
1183 | printf '\e]701;%s\007' de_DE.UTF-8 |
|
|
1184 | |
|
|
1185 | =item Can I switch the fonts at runtime? |
|
|
1186 | |
|
|
1187 | Yes, using an escape sequence. Try sth. like this, which has the same |
|
|
1188 | effect as using the C<-fn> switch, and takes effect immediately: |
|
|
1189 | |
|
|
1190 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
|
|
1191 | |
|
|
1192 | This is useful if you e.g. work primarily with japanese (and prefer a |
|
|
1193 | japanese font), but you have to switch to chinese temporarily, where |
|
|
1194 | japanese fonts would only be in your way. |
|
|
1195 | |
|
|
1196 | You can think of this as a kind of manual ISO-2022 switching. |
|
|
1197 | |
|
|
1198 | =item Why do italic characters look as if clipped? |
|
|
1199 | |
|
|
1200 | Many fonts have difficulties with italic characters and hinting. For |
|
|
1201 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
|
|
1202 | Mono> completely fails in it's italic face. A workaround is to enable |
|
|
1203 | freetype autohinting, i.e. like this: |
|
|
1204 | |
|
|
1205 | URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
1206 | URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
1207 | |
|
|
1208 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
|
|
1209 | |
|
|
1210 | You cna specify separate locales for the input method and the rest of the |
|
|
1211 | terminal, using the resource C<imlocale>: |
|
|
1212 | |
|
|
1213 | URxvt*imlocale: ja_JP.EUC-JP |
|
|
1214 | |
|
|
1215 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
|
|
1216 | use your input method. Please note, however, that you will not be able to |
|
|
1217 | input characters outside C<EUC-JP> in a normal way then, as your input |
|
|
1218 | method limits you. |
|
|
1219 | |
|
|
1220 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
|
|
1221 | |
|
|
1222 | Rxvt-unicode tries to obey the rule of not charging you for sth. you |
|
|
1223 | don't use. One thing you should try is to configure out all settings that |
|
|
1224 | you don't need, for example, Xft support is a resource hog by design, |
|
|
1225 | when used. Compiling it out ensures that no Xft font will be loaded |
|
|
1226 | accidentally when rxvt-unicode tries to find a font for your characters. |
|
|
1227 | |
|
|
1228 | Also, many people (me included) like large windows and even larger |
|
|
1229 | scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use |
|
|
1230 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
|
|
1231 | kilobyte per line. A scorllback buffer of 10000 lines will then (if full) |
|
|
1232 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
|
|
1233 | rxvt-unicode then uses 8 bytes per screen cell. |
|
|
1234 | |
|
|
1235 | =item Can I speed up Xft rendering somehow? |
|
|
1236 | |
|
|
1237 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
|
|
1238 | it is simply slow. If you still want Xft fonts you might try to disable |
|
|
1239 | antialiasing (by appending C<:antialiasing=false>), which saves lots of |
|
|
1240 | memory and also speeds up rendering considerably. |
|
|
1241 | |
|
|
1242 | =item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
|
|
1243 | |
|
|
1244 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
|
|
1245 | fall back to it's default font search list it will prefer X11 core |
|
|
1246 | fonts, because they are small and fast, and then use Xft fonts. It has |
|
|
1247 | antialiaisng disabled for most of them, because the author thinks they |
|
|
1248 | look best that way. |
|
|
1249 | |
|
|
1250 | If you want antialiasing, you have to specify the fonts manually. |
|
|
1251 | |
|
|
1252 | =item Mouse cut/paste suddenly no longer works. |
|
|
1253 | |
|
|
1254 | Make sure that mouse reporting is actually turned off since killing |
|
|
1255 | some editors prematurely may leave the mouse in mouse report mode. I've |
|
|
1256 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
|
|
1257 | quick check is to see if cut/paste works when the Alt or Shift keys are |
|
|
1258 | depressed. See @@RXVT_NAME@@(7) |
|
|
1259 | |
|
|
1260 | =item What's with this bold/blink stuff? |
|
|
1261 | |
|
|
1262 | If no bold colour is set via C<colorBD:>, bold will invert text using the |
|
|
1263 | standard foreground colour. |
|
|
1264 | |
|
|
1265 | For the standard background colour, blinking will actually make the |
|
|
1266 | text blink when compiled with C<--enable-blinking>. with standard |
|
|
1267 | colours. Without C<--enable-blinking>, the blink attribute will be |
|
|
1268 | ignored. |
|
|
1269 | |
|
|
1270 | On ANSI colours, bold/blink attributes are used to set high-intensity |
|
|
1271 | foreground/background colors. |
|
|
1272 | |
|
|
1273 | color0-7 are the low-intensity colors. |
|
|
1274 | |
|
|
1275 | color8-15 are the corresponding high-intensity colors. |
|
|
1276 | |
|
|
1277 | =item I don't like the screen colors. How do I change them? |
|
|
1278 | |
|
|
1279 | You can change the screen colors at run-time using F<~/.Xdefaults> |
|
|
1280 | resources (or as long-options). |
|
|
1281 | |
|
|
1282 | Here are values that are supposed to resemble a VGA screen, |
|
|
1283 | including the murky brown that passes for low-intensity yellow: |
|
|
1284 | |
|
|
1285 | Rxvt*color0: #000000 |
|
|
1286 | Rxvt*color1: #A80000 |
|
|
1287 | Rxvt*color2: #00A800 |
|
|
1288 | Rxvt*color3: #A8A800 |
|
|
1289 | Rxvt*color4: #0000A8 |
|
|
1290 | Rxvt*color5: #A800A8 |
|
|
1291 | Rxvt*color6: #00A8A8 |
|
|
1292 | Rxvt*color7: #A8A8A8 |
|
|
1293 | |
|
|
1294 | Rxvt*color8: #000054 |
|
|
1295 | Rxvt*color9: #FF0054 |
|
|
1296 | Rxvt*color10: #00FF54 |
|
|
1297 | Rxvt*color11: #FFFF54 |
|
|
1298 | Rxvt*color12: #0000FF |
|
|
1299 | Rxvt*color13: #FF00FF |
|
|
1300 | Rxvt*color14: #00FFFF |
|
|
1301 | Rxvt*color15: #FFFFFF |
|
|
1302 | |
|
|
1303 | =item What's with the strange Backspace/Delete key behaviour? |
|
|
1304 | |
|
|
1305 | Assuming that the physical Backspace key corresponds to the |
|
|
1306 | BackSpace keysym (not likely for Linux ... see the following |
|
|
1307 | question) there are two standard values that can be used for |
|
|
1308 | Backspace: C<^H> and C<^?>. |
|
|
1309 | |
|
|
1310 | Historically, either value is correct, but rxvt-unicode adopts the debian |
|
|
1311 | policy of using C<^?> when unsure, because it's the one only only correct |
|
|
1312 | choice :). |
|
|
1313 | |
|
|
1314 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
|
|
1315 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
|
|
1316 | started from a terminal (say, from a menu or by remote shell), then the |
|
|
1317 | system value of `erase', which corresponds to CERASE in <termios.h>, will |
|
|
1318 | be used (which may not be the same as your stty setting). |
|
|
1319 | |
|
|
1320 | For starting a new rxvt-unicode: |
|
|
1321 | |
|
|
1322 | # use Backspace = ^H |
|
|
1323 | $ stty erase ^H |
|
|
1324 | $ @@RXVT_NAME@@ |
|
|
1325 | |
|
|
1326 | # use Backspace = ^? |
|
|
1327 | $ stty erase ^? |
|
|
1328 | $ @@RXVT_NAME@@ |
|
|
1329 | |
|
|
1330 | Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7). |
|
|
1331 | |
|
|
1332 | For an existing rxvt-unicode: |
|
|
1333 | |
|
|
1334 | # use Backspace = ^H |
|
|
1335 | $ stty erase ^H |
|
|
1336 | $ echo -n "^[[36h" |
|
|
1337 | |
|
|
1338 | # use Backspace = ^? |
|
|
1339 | $ stty erase ^? |
|
|
1340 | $ echo -n "^[[36l" |
|
|
1341 | |
|
|
1342 | This helps satisfy some of the Backspace discrepancies that occur, but |
|
|
1343 | if you use Backspace = C<^H>, make sure that the termcap/terminfo value |
|
|
1344 | properly reflects that. |
|
|
1345 | |
|
|
1346 | The Delete key is a another casualty of the ill-defined Backspace problem. |
|
|
1347 | To avoid confusion between the Backspace and Delete keys, the Delete |
|
|
1348 | key has been assigned an escape sequence to match the vt100 for Execute |
|
|
1349 | (ESC[3~) and is in the supplied termcap/terminfo. |
|
|
1350 | |
|
|
1351 | Some other Backspace problems: |
|
|
1352 | |
|
|
1353 | some editors use termcap/terminfo, |
|
|
1354 | some editors (vim I'm told) expect Backspace = ^H, |
|
|
1355 | GNU Emacs (and Emacs-like editors) use ^H for help. |
|
|
1356 | |
|
|
1357 | Perhaps someday this will all be resolved in a consistent manner. |
|
|
1358 | |
|
|
1359 | =item I don't like the key-bindings. How do I change them? |
|
|
1360 | |
|
|
1361 | There are some compile-time selections available via configure. Unless |
|
|
1362 | you have run "configure" with the C<--disable-resources> option you can |
|
|
1363 | use the `keysym' resource to alter the keystrings associated with keysym |
|
|
1364 | 0xFF00 - 0xFFFF (function, cursor keys, etc). |
|
|
1365 | |
|
|
1366 | Here's an example for a tn3270 session started using `@@RXVT_NAME@@ -name tn3270' |
|
|
1367 | |
|
|
1368 | !# ----- special uses ------: |
|
|
1369 | ! tn3270 login, remap function and arrow keys. |
|
|
1370 | tn3270*font: *clean-bold-*-*--15-* |
|
|
1371 | |
|
|
1372 | ! keysym - used by rxvt only |
|
|
1373 | ! Delete - ^D |
|
|
1374 | tn3270*keysym.0xFFFF: \004 |
|
|
1375 | |
|
|
1376 | ! Home - ^A |
|
|
1377 | tn3270*keysym.0xFF50: \001 |
|
|
1378 | ! Left - ^B |
|
|
1379 | tn3270*keysym.0xFF51: \002 |
|
|
1380 | ! Up - ^P |
|
|
1381 | tn3270*keysym.0xFF52: \020 |
|
|
1382 | ! Right - ^F |
|
|
1383 | tn3270*keysym.0xFF53: \006 |
|
|
1384 | ! Down - ^N |
|
|
1385 | tn3270*keysym.0xFF54: \016 |
|
|
1386 | ! End - ^E |
|
|
1387 | tn3270*keysym.0xFF57: \005 |
|
|
1388 | |
|
|
1389 | ! F1 - F12 |
|
|
1390 | tn3270*keysym.0xFFBE: \e1 |
|
|
1391 | tn3270*keysym.0xFFBF: \e2 |
|
|
1392 | tn3270*keysym.0xFFC0: \e3 |
|
|
1393 | tn3270*keysym.0xFFC1: \e4 |
|
|
1394 | tn3270*keysym.0xFFC2: \e5 |
|
|
1395 | tn3270*keysym.0xFFC3: \e6 |
|
|
1396 | tn3270*keysym.0xFFC4: \e7 |
|
|
1397 | tn3270*keysym.0xFFC5: \e8 |
|
|
1398 | tn3270*keysym.0xFFC6: \e9 |
|
|
1399 | tn3270*keysym.0xFFC7: \e0 |
|
|
1400 | tn3270*keysym.0xFFC8: \e- |
|
|
1401 | tn3270*keysym.0xFFC9: \e= |
|
|
1402 | |
|
|
1403 | ! map Prior/Next to F7/F8 |
|
|
1404 | tn3270*keysym.0xFF55: \e7 |
|
|
1405 | tn3270*keysym.0xFF56: \e8 |
|
|
1406 | |
|
|
1407 | =item I'm using keyboard model XXX that has extra Prior/Next/Insert keys. |
|
|
1408 | How do I make use of them? For example, the Sun Keyboard type 4 |
|
|
1409 | has the following mappings that rxvt-unicode doesn't recognize. |
|
|
1410 | |
|
|
1411 | KP_Insert == Insert |
|
|
1412 | F22 == Print |
|
|
1413 | F27 == Home |
|
|
1414 | F29 == Prior |
|
|
1415 | F33 == End |
|
|
1416 | F35 == Next |
|
|
1417 | |
|
|
1418 | Rather than have rxvt-unicode try to accomodate all the various possible keyboard |
|
|
1419 | mappings, it is better to use `xmodmap' to remap the keys as required for |
|
|
1420 | your particular machine. |
|
|
1421 | |
|
|
1422 | =item How do I distinguish if I'm running rxvt-unicode or a regular xterm? |
|
|
1423 | I need this to decide about setting colors etc. |
|
|
1424 | |
|
|
1425 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
|
|
1426 | check and see if that is set. Note that several programs, JED, slrn, |
|
|
1427 | Midnight Commander automatically check this variable to decide whether or |
|
|
1428 | not to use color. |
|
|
1429 | |
|
|
1430 | =item How do I set the correct, full IP address for the DISPLAY variable? |
|
|
1431 | |
|
|
1432 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and ahve enabled |
|
|
1433 | insecure mode then it is possible to use the following shell script |
|
|
1434 | snippets to correctly set the display. If your version of rxvt-unicode |
|
|
1435 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
|
|
1436 | the COLORTERM variable can be used to distinguish rxvt-unicode from a |
|
|
1437 | regular xterm. |
|
|
1438 | |
|
|
1439 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
|
|
1440 | snippets: |
|
|
1441 | |
|
|
1442 | # Bourne/Korn/POSIX family of shells: |
|
|
1443 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
|
|
1444 | if [ ${TERM:-foo} = xterm ]; then |
|
|
1445 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
|
|
1446 | echo -n '^[Z' |
|
|
1447 | read term_id |
|
|
1448 | stty icanon echo |
|
|
1449 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
|
|
1450 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
|
|
1451 | read DISPLAY # set it in our local shell |
|
|
1452 | fi |
|
|
1453 | fi |
|
|
1454 | |
|
|
1455 | =item How do I compile the manual pages for myself? |
|
|
1456 | |
|
|
1457 | You need to have a recent version of perl installed as F</usr/bin/perl>, |
|
|
1458 | one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to |
|
|
1459 | the doc subdirectory and enter C<make alldoc>. |
|
|
1460 | |
|
|
1461 | =back |
|
|
1462 | |
818 | =head1 ENVIRONMENT |
1463 | =head1 ENVIRONMENT |
819 | |
1464 | |
820 | B<@@RXVTNAME@@> sets the environment variables B<TERM>, B<COLORTERM> |
1465 | B<@@RXVT_NAME@@> sets the environment variables B<TERM>, B<COLORTERM> |
821 | and B<COLORFGBG>. The environment variable B<WINDOWID> is set to the X |
1466 | and B<COLORFGBG>. The environment variable B<WINDOWID> is set to the X |
822 | window id number of the B<@@RXVTNAME@@> window and it also uses and |
1467 | window id number of the B<@@RXVT_NAME@@> window and it also uses and |
823 | sets the environment variable B<DISPLAY> to specify which display |
1468 | sets the environment variable B<DISPLAY> to specify which display |
824 | terminal to use. B<@@RXVTNAME@@> uses the environment variables |
1469 | terminal to use. B<@@RXVT_NAME@@> uses the environment variables |
825 | B<RXVTPATH> and B<PATH> to find XPM files. |
1470 | B<RXVTPATH> and B<PATH> to find XPM files. |
826 | |
1471 | |
827 | =head1 FILES |
1472 | =head1 FILES |
828 | |
1473 | |
829 | =over 4 |
1474 | =over 4 |
… | |
… | |
836 | |
1481 | |
837 | Color names. |
1482 | Color names. |
838 | |
1483 | |
839 | =back |
1484 | =back |
840 | |
1485 | |
841 | =head1 SEEALSO |
1486 | =head1 SEE ALSO |
842 | |
1487 | |
843 | I<xterm>(1), I<sh>(1), I<resize>(1), I<X>(1), I<pty>(4), I<tty>(4), I<utmp>(5) |
1488 | @@RXVT_NAME@@(7), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5) |
844 | |
|
|
845 | See rxvtRef.html rxvtRef.txt for detailed information on recognized escape sequences and menuBar syntax, etc. |
|
|
846 | |
1489 | |
847 | =head1 BUGS |
1490 | =head1 BUGS |
848 | |
1491 | |
849 | Check the BUGS file for an up-to-date list. |
1492 | Check the BUGS file for an up-to-date list. |
850 | |
1493 | |
851 | Cursor change support is not yet implemented. |
1494 | Cursor change support is not yet implemented. |
852 | |
1495 | |
853 | Click-and-drag doesn't work with X11 mouse report overriding. |
1496 | Click-and-drag doesn't work with X11 mouse report overriding. |
854 | |
1497 | |
855 | =head1 FTP LOCATION |
|
|
856 | |
|
|
857 | rxvt-+@@RXVTVERSION@@.tar.gz can be found at the following ftp sites L<@@RXVTFTPSITE@@>(@@RXVTFTPSITE@@) |
|
|
858 | |
|
|
859 | =head1 CURRENT PROJECT COORDINATOR |
1498 | =head1 CURRENT PROJECT COORDINATOR |
860 | |
1499 | |
861 | =over 4 |
1500 | =over 4 |
862 | |
1501 | |
863 | =item Project Coordinator |
1502 | =item Project Coordinator |
864 | |
1503 | |
865 | @@RXVTMAINT@@ L<@@RXVTMAINTEMAIL@@> |
1504 | @@RXVT_MAINT@@ L<@@RXVT_MAINTEMAIL@@> |
866 | |
1505 | |
867 | =item Web page maintainter |
1506 | =item Web page maintainter |
868 | |
1507 | |
869 | @@RXVTWEBMAINT@@ L<@@RXVTWEBMAINTEMAIL@@> |
1508 | @@RXVT_WEBMAINT@@ L<@@RXVT_WEBMAINTEMAIL@@> |
870 | |
1509 | |
871 | L<@@RXVTWEBPAGE@@>(@@RXVTWEBPAGE@@) |
1510 | L<@@RXVT_WEBPAGE@@> |
872 | |
1511 | |
873 | =back |
1512 | =back |
874 | |
1513 | |
875 | =head1 AUTHORS |
1514 | =head1 AUTHORS |
876 | |
1515 | |