… | |
… | |
42 | because the author couldn't get C<mlterm> to use one font for latin1 and |
42 | because the author couldn't get C<mlterm> to use one font for latin1 and |
43 | another for japanese. |
43 | another for japanese. |
44 | |
44 | |
45 | Therefore another design rationale was the use of multiple fonts to |
45 | Therefore another design rationale was the use of multiple fonts to |
46 | display characters: The idea of a single unicode font which many other |
46 | display characters: The idea of a single unicode font which many other |
47 | programs force onto it's users never made sense to me: You should be able |
47 | programs force onto its users never made sense to me: You should be able |
48 | to choose any font for any script freely. |
48 | to choose any font for any script freely. |
49 | |
49 | |
50 | Apart from that, rxvt-unicode is also much better internationalised than |
50 | Apart from that, rxvt-unicode is also much better internationalised than |
51 | it's predecessor, supports things such as XFT and ISO 14755 that are handy |
51 | its predecessor, supports things such as XFT and ISO 14755 that are handy |
52 | in i18n-environments, is faster, and has a lot less bugs than the original |
52 | in i18n-environments, is faster, and has a lot less bugs than the original |
53 | rxvt. This all in addition to dozens of other small improvements. |
53 | rxvt. This all in addition to dozens of other small improvements. |
54 | |
54 | |
55 | It is still faithfully following the original rxvt idea of being lean |
55 | It is still faithfully following the original rxvt idea of being lean |
56 | and nice on resources: for example, you can still configure rxvt-unicode |
56 | and nice on resources: for example, you can still configure rxvt-unicode |
57 | without most of it's features to get a lean binary. It also comes with |
57 | without most of its features to get a lean binary. It also comes with |
58 | a client/daemon pair that lets you open any number of terminal windows |
58 | a client/daemon pair that lets you open any number of terminal windows |
59 | from within a single process, which makes startup time very fast and |
59 | from within a single process, which makes startup time very fast and |
60 | drastically reduces memory usage. See @@RXVT_NAME@@d(1) (daemon) and |
60 | drastically reduces memory usage. See @@RXVT_NAME@@d(1) (daemon) and |
61 | @@RXVT_NAME@@c(1) (client). |
61 | @@RXVT_NAME@@c(1) (client). |
62 | |
62 | |
… | |
… | |
185 | that are checked in order when trying to find glyphs for characters. The |
185 | that are checked in order when trying to find glyphs for characters. The |
186 | first font defines the cell size for characters; other fonts might be |
186 | first font defines the cell size for characters; other fonts might be |
187 | smaller, but not (in general) larger. A (hopefully) reasonable default |
187 | smaller, but not (in general) larger. A (hopefully) reasonable default |
188 | font list is always appended to it. See resource B<font> for more details. |
188 | font list is always appended to it. See resource B<font> for more details. |
189 | |
189 | |
190 | In short, to specify an X11 core font, just specify it's name or prefix it |
190 | In short, to specify an X11 core font, just specify its name or prefix it |
191 | with C<x:>. To specify an XFT-font, you need to prefix it with C<xft:>, |
191 | with C<x:>. To specify an XFT-font, you need to prefix it with C<xft:>, |
192 | e.g.: |
192 | e.g.: |
193 | |
193 | |
194 | @@RXVT_NAME@@ -fn "xft:Bitstream Vera Sans Mono:pixelsize=15" |
194 | @@RXVT_NAME@@ -fn "xft:Bitstream Vera Sans Mono:pixelsize=15" |
195 | @@RXVT_NAME@@ -fn "9x15bold,xft:Bitstream Vera Sans Mono" |
195 | @@RXVT_NAME@@ -fn "9x15bold,xft:Bitstream Vera Sans Mono" |
… | |
… | |
423 | |
423 | |
424 | Remap a key symbol. See resource B<keysym>. |
424 | Remap a key symbol. See resource B<keysym>. |
425 | |
425 | |
426 | =item B<-embed> I<windowid> |
426 | =item B<-embed> I<windowid> |
427 | |
427 | |
428 | Tells @@RXVT_NAME@@ to embed it's windows into an already-existing window, |
428 | Tells @@RXVT_NAME@@ to embed its windows into an already-existing window, |
429 | which enables applications to easily embed a terminal. |
429 | which enables applications to easily embed a terminal. |
430 | |
430 | |
431 | Right now, @@RXVT_NAME@@ will first unmap/map the specified window, so it |
431 | Right now, @@RXVT_NAME@@ will first unmap/map the specified window, so it |
432 | shouldn't be a top-level window. @@RXVT_NAME@@ will also reconfigure it |
432 | shouldn't be a top-level window. @@RXVT_NAME@@ will also reconfigure it |
433 | quite a bit, so don't expect it to keep some specific state. It's best to |
433 | quite a bit, so don't expect it to keep some specific state. It's best to |
… | |
… | |
1028 | C<\000>: octal number) or verbatim control characters (C<^?>: delete, |
1028 | C<\000>: octal number) or verbatim control characters (C<^?>: delete, |
1029 | C<^@>: null, C<^A> ...) and may be enclosed with double quotes so that it |
1029 | C<^@>: null, C<^A> ...) and may be enclosed with double quotes so that it |
1030 | can start or end with whitespace. |
1030 | can start or end with whitespace. |
1031 | |
1031 | |
1032 | Please note that you need to double the C<\> in resource files, as |
1032 | Please note that you need to double the C<\> in resource files, as |
1033 | Xlib itself does it's own de-escaping (you can use C<\033> instead of |
1033 | Xlib itself does its own de-escaping (you can use C<\033> instead of |
1034 | C<\e> (and so on), which will work with both Xt and @@RXVT_NAME@@'s own |
1034 | C<\e> (and so on), which will work with both Xt and @@RXVT_NAME@@'s own |
1035 | processing). |
1035 | processing). |
1036 | |
1036 | |
1037 | You can define a range of keysyms in one shot by providing a I<string> |
1037 | You can define a range of keysyms in one shot by providing a I<string> |
1038 | with pattern B<list/PREFIX/MIDDLE/SUFFIX>, where the delimeter `/' |
1038 | with pattern B<list/PREFIX/MIDDLE/SUFFIX>, where the delimeter `/' |
… | |
… | |
1273 | This mode lets you input characters representing the keycap symbols of |
1273 | This mode lets you input characters representing the keycap symbols of |
1274 | your keyboard, if representable in the current locale encoding. |
1274 | your keyboard, if representable in the current locale encoding. |
1275 | |
1275 | |
1276 | Start by pressing C<Control> and C<Shift> together, then releasing |
1276 | Start by pressing C<Control> and C<Shift> together, then releasing |
1277 | them. The next special key (cursor keys, home etc.) you enter will not |
1277 | them. The next special key (cursor keys, home etc.) you enter will not |
1278 | invoke it's usual function but instead will insert the corresponding |
1278 | invoke its usual function but instead will insert the corresponding |
1279 | keycap symbol. The symbol will only be entered when the key has been |
1279 | keycap symbol. The symbol will only be entered when the key has been |
1280 | released, otherwise pressing e.g. C<Shift> would enter the symbol for |
1280 | released, otherwise pressing e.g. C<Shift> would enter the symbol for |
1281 | C<ISO Level 2 Switch>, although your intention might have been to enter a |
1281 | C<ISO Level 2 Switch>, although your intention might have been to enter a |
1282 | reverse tab (Shift-Tab). |
1282 | reverse tab (Shift-Tab). |
1283 | |
1283 | |
… | |
… | |
1432 | C<--with-terminfo=PATH>. |
1432 | C<--with-terminfo=PATH>. |
1433 | |
1433 | |
1434 | =item B<DISPLAY> |
1434 | =item B<DISPLAY> |
1435 | |
1435 | |
1436 | Used by @@RXVT_NAME@@ to connect to the display and set to the correct |
1436 | Used by @@RXVT_NAME@@ to connect to the display and set to the correct |
1437 | display in it's child processes. |
1437 | display in its child processes. |
1438 | |
1438 | |
1439 | =item B<SHELL> |
1439 | =item B<SHELL> |
1440 | |
1440 | |
1441 | The shell to be used for command execution, defaults to C</bin/sh>. |
1441 | The shell to be used for command execution, defaults to C</bin/sh>. |
1442 | |
1442 | |