| … | |
… | |
| 47 | <p><strong>rxvt</strong> [options] [-e command [ args ]]</p> |
47 | <p><strong>rxvt</strong> [options] [-e command [ args ]]</p> |
| 48 | <p> |
48 | <p> |
| 49 | </p> |
49 | </p> |
| 50 | <hr /> |
50 | <hr /> |
| 51 | <h1><a name="description">DESCRIPTION</a></h1> |
51 | <h1><a name="description">DESCRIPTION</a></h1> |
| 52 | <p><strong>rxvt-unicode</strong>, version <strong>5.1</strong>, is a colour vt102 terminal |
52 | <p><strong>rxvt-unicode</strong>, version <strong>5.2</strong>, is a colour vt102 terminal |
| 53 | emulator intended as an <em>xterm</em>(1) replacement for users who do not |
53 | emulator intended as an <em>xterm</em>(1) replacement for users who do not |
| 54 | require features such as Tektronix 4014 emulation and toolkit-style |
54 | require features such as Tektronix 4014 emulation and toolkit-style |
| 55 | configurability. As a result, <strong>rxvt-unicode</strong> uses much less swap space -- |
55 | configurability. As a result, <strong>rxvt-unicode</strong> uses much less swap space -- |
| 56 | a significant advantage on a machine serving many X sessions.</p> |
56 | a significant advantage on a machine serving many X sessions.</p> |
| 57 | <p> |
57 | <p> |
| … | |
… | |
| 530 | shouldn't be a top-level window. rxvt will also reconfigure it |
530 | shouldn't be a top-level window. rxvt will also reconfigure it |
| 531 | quite a bit, so don't expect it to keep some specific state. It's best to |
531 | quite a bit, so don't expect it to keep some specific state. It's best to |
| 532 | create an extra subwindow for rxvt and leave it alone.</p> |
532 | create an extra subwindow for rxvt and leave it alone.</p> |
| 533 | </dd> |
533 | </dd> |
| 534 | <dd> |
534 | <dd> |
|
|
535 | <p>The window will not be destroyed when rxvt exits.</p> |
|
|
536 | </dd> |
|
|
537 | <dd> |
| 535 | <p>It might be useful to know that rxvt will not close file |
538 | <p>It might be useful to know that rxvt will not close file |
| 536 | descriptors passed to it (except for stdin/out/err, of course), so you |
539 | descriptors passed to it (except for stdin/out/err, of course), so you |
| 537 | can use file descriptors to communicate with the programs within the |
540 | can use file descriptors to communicate with the programs within the |
| 538 | terminal. This works regardless of wether the <code>-embed</code> option was used or |
541 | terminal. This works regardless of wether the <code>-embed</code> option was used or |
| 539 | not.</p> |
542 | not.</p> |
| … | |
… | |
| 938 | <p></p> |
941 | <p></p> |
| 939 | <dt><strong><a name="item_scrollwithbuffer_3a_boolean"><strong>scrollWithBuffer:</strong> <em>boolean</em></a></strong><br /> |
942 | <dt><strong><a name="item_scrollwithbuffer_3a_boolean"><strong>scrollWithBuffer:</strong> <em>boolean</em></a></strong><br /> |
| 940 | </dt> |
943 | </dt> |
| 941 | <dd> |
944 | <dd> |
| 942 | <strong>True</strong>: scroll with scrollback buffer when tty receives new lines (and |
945 | <strong>True</strong>: scroll with scrollback buffer when tty receives new lines (and |
| 943 | <strong>scrollTtyOutput</strong> is False); option <strong>+sw</strong>. <strong>False</strong>: do not scroll |
946 | <strong>scrollTtyOutput</strong> is False); option <strong>-sw</strong>. <strong>False</strong>: do not scroll |
| 944 | with scrollback buffer when tty recieves new lines; option <strong>-sw</strong>. |
947 | with scrollback buffer when tty recieves new lines; option <strong>+sw</strong>. |
| 945 | </dd> |
948 | </dd> |
| 946 | <p></p> |
949 | <p></p> |
| 947 | <dt><strong><a name="item_scrollttykeypress_3a_boolean"><strong>scrollTtyKeypress:</strong> <em>boolean</em></a></strong><br /> |
950 | <dt><strong><a name="item_scrollttykeypress_3a_boolean"><strong>scrollTtyKeypress:</strong> <em>boolean</em></a></strong><br /> |
| 948 | </dt> |
951 | </dt> |
| 949 | <dd> |
952 | <dd> |
