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