… | |
… | |
73 | <p> |
73 | <p> |
74 | </p> |
74 | </p> |
75 | <hr /> |
75 | <hr /> |
76 | <h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1> |
76 | <h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1> |
77 | <dl> |
77 | <dl> |
|
|
78 | <dt><strong><a name="item_isn_27t_rxvt_supposed_to_be_small_3f_don_27t_all_t">Isn't rxvt supposed to be small? Don't all those features bloat?</a></strong><br /> |
|
|
79 | </dt> |
|
|
80 | <dd> |
|
|
81 | I often get asked about this, and I think, no, they didn't cause extra |
|
|
82 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
|
|
83 | that the urxvt binary is larger (due to some encoding tables always being |
|
|
84 | compiled in), but it actually uses less memory (RSS) after startup. Even |
|
|
85 | with <code>--disable-everything</code>, this comparison is a bit unfair, as many |
|
|
86 | features unique to urxvt (locale, encoding conversion, iso14755 etc.) are |
|
|
87 | already in use in this mode. |
|
|
88 | </dd> |
|
|
89 | <dd> |
|
|
90 | <pre> |
|
|
91 | text data bss drs rss filename |
|
|
92 | 98398 1664 24 15695 1824 rxvt --disable-everything |
|
|
93 | 188985 9048 66616 18222 1788 urxvt --disable-everything</pre> |
|
|
94 | </dd> |
|
|
95 | <dd> |
|
|
96 | <p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which _is_ unfair, as this involves xft |
|
|
97 | and full locale/XIM support which are quite bloaty inside libX11 and my |
|
|
98 | libc), the two diverge, but not unreasnobaly so.</p> |
|
|
99 | </dd> |
|
|
100 | <dd> |
|
|
101 | <pre> |
|
|
102 | text data bss drs rss filename |
|
|
103 | 163431 2152 24 20123 2060 rxvt --enable-everything |
|
|
104 | 1035683 49680 66648 29096 3680 urxvt --enable-everything</pre> |
|
|
105 | </dd> |
|
|
106 | <dd> |
|
|
107 | <p>The very large size of the text section is explained by the east-asian |
|
|
108 | encoding tables, which, if unused, take up disk space but nothing else |
|
|
109 | and can be compiled out unless you rely on X11 core fonts that use those |
|
|
110 | encodings. The BSS size comes from the 64k emergency buffer that my c++ |
|
|
111 | compiler allocates (but of course doesn't use unless you are out of |
|
|
112 | memory). Also, using an xft font instead of a core font immediately adds a |
|
|
113 | few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when |
|
|
114 | not used.</p> |
|
|
115 | </dd> |
|
|
116 | <dd> |
|
|
117 | <p>Of course, due to every character using two or four bytes instead of one, |
|
|
118 | a large scrollback buffer will ultimately make rxvt-unicode use more |
|
|
119 | memory.</p> |
|
|
120 | </dd> |
|
|
121 | <dd> |
|
|
122 | <p>Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this |
|
|
123 | still fares rather well. And compared to some monsters like gnome-terminal |
|
|
124 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
|
|
125 | 43180k in daemons that stay around after exit, plus half aminute of |
|
|
126 | startup time, including the hundreds of warnings it spits out), it fares |
|
|
127 | extremely well *g*.</p> |
|
|
128 | </dd> |
|
|
129 | <p></p> |
|
|
130 | <dt><strong><a name="item_why_c_2b_2b_2c_isn_27t_that_unportable_2fbloated_2">Why C++, isn't that unportable/bloated/uncool?</a></strong><br /> |
|
|
131 | </dt> |
|
|
132 | <dd> |
|
|
133 | Is this a question? :) It comes up very often. The simple answer is: I had |
|
|
134 | to write it, and C++ allowed me to write and maintain it in a fraction |
|
|
135 | of the time and effort (which is a scarce resource for me). Put even |
|
|
136 | shorter: It simply wouldn't exist without C++. |
|
|
137 | </dd> |
|
|
138 | <dd> |
|
|
139 | <p>My personal stance on this is that C++ is less portable than C, but in |
|
|
140 | the case of rxvt-unicode this hardly matters, as its portability limits |
|
|
141 | are defined by things like X11, pseudo terminals, locale support and unix |
|
|
142 | domain sockets, which are all less portable than C++ itself.</p> |
|
|
143 | </dd> |
|
|
144 | <dd> |
|
|
145 | <p>Regarding the bloat, see the above question: It's easy to write programs |
|
|
146 | in C that use gobs of memory, an certainly possible to write programs in |
|
|
147 | C++ that don't. C++ also often comes with large libraries, but this is |
|
|
148 | not necessarily the case with GCC. Here is what rxvt links against on my |
|
|
149 | system with a minimal config:</p> |
|
|
150 | </dd> |
|
|
151 | <dd> |
|
|
152 | <pre> |
|
|
153 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
|
|
154 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
|
|
155 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
|
|
156 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> |
|
|
157 | </dd> |
|
|
158 | <dd> |
|
|
159 | <p>And here is rxvt-unicode:</p> |
|
|
160 | </dd> |
|
|
161 | <dd> |
|
|
162 | <pre> |
|
|
163 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
|
|
164 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
|
|
165 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
|
|
166 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
|
|
167 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> |
|
|
168 | </dd> |
|
|
169 | <dd> |
|
|
170 | <p>No large bloated libraries (of course, none were linked in statically), |
|
|
171 | except maybe libX11 :)</p> |
|
|
172 | </dd> |
|
|
173 | <p></p> |
|
|
174 | <dt><strong><a name="item_does_it_support_tabs_2c_can_i_have_a_tabbed_rxvt_2">Does it support tabs, can I have a tabbed rxvt-unicode?</a></strong><br /> |
|
|
175 | </dt> |
|
|
176 | <dd> |
|
|
177 | rxvt-unicode does not directly support tabs. It will work fine with |
|
|
178 | tabbing functionality of many window managers or similar tabbing programs, |
|
|
179 | and its embedding-features allow it to be embedded into other programs, |
|
|
180 | as witnessed by <em>doc/rxvt-tabbed</em> or the upcoming <code>Gtk2::URxvt</code> perl |
|
|
181 | module, which features a tabbed urxvt (murxvt) terminal as an example |
|
|
182 | embedding application. |
|
|
183 | </dd> |
|
|
184 | <p></p> |
78 | <dt><strong><a name="item_how_do_i_know_which_rxvt_2dunicode_version_i_27m_u">How do I know which rxvt-unicode version I'm using?</a></strong><br /> |
185 | <dt><strong><a name="item_how_do_i_know_which_rxvt_2dunicode_version_i_27m_u">How do I know which rxvt-unicode version I'm using?</a></strong><br /> |
79 | </dt> |
186 | </dt> |
80 | <dd> |
187 | <dd> |
81 | The version number is displayed with the usage (-h). Also the escape |
188 | The version number is displayed with the usage (-h). Also the escape |
82 | sequence <code>ESC [ 8 n</code> sets the window title to the version number. |
189 | sequence <code>ESC [ 8 n</code> sets the window title to the version number. When |
|
|
190 | using the urxvtc client, the version displayed is that of the |
|
|
191 | daemon. |
83 | </dd> |
192 | </dd> |
84 | <p></p> |
193 | <p></p> |
85 | <dt><strong><a name="item_i_am_using_debian_gnu_2flinux_and_have_a_problem_2">I am using Debian GNU/Linux and have a problem...</a></strong><br /> |
194 | <dt><strong><a name="item_i_am_using_debian_gnu_2flinux_and_have_a_problem_2">I am using Debian GNU/Linux and have a problem...</a></strong><br /> |
86 | </dt> |
195 | </dt> |
87 | <dd> |
196 | <dd> |
… | |
… | |
145 | <dd> |
254 | <dd> |
146 | Most likely it's the empty definition for <code>enacs=</code>. Just replace it by |
255 | Most likely it's the empty definition for <code>enacs=</code>. Just replace it by |
147 | <code>enacs=\E[0@</code> and try again. |
256 | <code>enacs=\E[0@</code> and try again. |
148 | </dd> |
257 | </dd> |
149 | <p></p> |
258 | <p></p> |
150 | <dt><strong><a name="item_bash_27s_readline_does_not_work_correctly_under_rx"><code>bash</code>'s readline does not work correctly under rxvt.</a></strong><br /> |
259 | <dt><strong><a name="item_bash_27s_readline_does_not_work_correctly_under_ur"><code>bash</code>'s readline does not work correctly under urxvt.</a></strong><br /> |
151 | </dt> |
260 | </dt> |
152 | <dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br /> |
261 | <dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br /> |
153 | </dt> |
262 | </dt> |
154 | <dd> |
263 | <dd> |
155 | One reason you might want this is that some distributions or operating |
264 | One reason you might want this is that some distributions or operating |
… | |
… | |
309 | <p>In that case, select a font of your taste and add it to the font list, |
418 | <p>In that case, select a font of your taste and add it to the font list, |
310 | e.g.:</p> |
419 | e.g.:</p> |
311 | </dd> |
420 | </dd> |
312 | <dd> |
421 | <dd> |
313 | <pre> |
422 | <pre> |
314 | rxvt -fn basefont,font2,font3...</pre> |
423 | urxvt -fn basefont,font2,font3...</pre> |
315 | </dd> |
424 | </dd> |
316 | <dd> |
425 | <dd> |
317 | <p>When rxvt-unicode sees a character, it will first look at the base |
426 | <p>When rxvt-unicode sees a character, it will first look at the base |
318 | font. If the base font does not contain the character, it will go to the |
427 | font. If the base font does not contain the character, it will go to the |
319 | next font, and so on. Specifying your own fonts will also speed up this |
428 | next font, and so on. Specifying your own fonts will also speed up this |
… | |
… | |
693 | <dd> |
802 | <dd> |
694 | Make sure that mouse reporting is actually turned off since killing |
803 | Make sure that mouse reporting is actually turned off since killing |
695 | some editors prematurely may leave the mouse in mouse report mode. I've |
804 | some editors prematurely may leave the mouse in mouse report mode. I've |
696 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
805 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
697 | quick check is to see if cut/paste works when the Alt or Shift keys are |
806 | quick check is to see if cut/paste works when the Alt or Shift keys are |
698 | depressed. See <code>rxvt(7)</code> |
807 | depressed. See <code>urxvt(7)</code> |
699 | </dd> |
808 | </dd> |
700 | <p></p> |
809 | <p></p> |
701 | <dt><strong><a name="item_what_27s_with_this_bold_2fblink_stuff_3f">What's with this bold/blink stuff?</a></strong><br /> |
810 | <dt><strong><a name="item_what_27s_with_this_bold_2fblink_stuff_3f">What's with this bold/blink stuff?</a></strong><br /> |
702 | </dt> |
811 | </dt> |
703 | <dd> |
812 | <dd> |
… | |
… | |
777 | URxvt.color14: #73f7ff |
886 | URxvt.color14: #73f7ff |
778 | URxvt.color7: #e1dddd |
887 | URxvt.color7: #e1dddd |
779 | URxvt.color15: #e1dddd</pre> |
888 | URxvt.color15: #e1dddd</pre> |
780 | </dd> |
889 | </dd> |
781 | <p></p> |
890 | <p></p> |
782 | <dt><strong><a name="item_how_can_i_start_rxvtd_in_a_race_2dfree_way_3f">How can I start rxvtd in a race-free way?</a></strong><br /> |
891 | <dt><strong><a name="item_how_can_i_start_urxvtd_in_a_race_2dfree_way_3f">How can I start urxvtd in a race-free way?</a></strong><br /> |
783 | </dt> |
892 | </dt> |
784 | <dd> |
893 | <dd> |
785 | Try <code>rxvtd -f -o</code>, which tells rxvtd to open the |
894 | Try <code>urxvtd -f -o</code>, which tells urxvtd to open the |
786 | display, create the listening socket and then fork. |
895 | display, create the listening socket and then fork. |
787 | </dd> |
896 | </dd> |
788 | <p></p> |
897 | <p></p> |
789 | <dt><strong><a name="item_what_27s_with_the_strange_backspace_2fdelete_key_b">What's with the strange Backspace/Delete key behaviour?</a></strong><br /> |
898 | <dt><strong><a name="item_what_27s_with_the_strange_backspace_2fdelete_key_b">What's with the strange Backspace/Delete key behaviour?</a></strong><br /> |
790 | </dt> |
899 | </dt> |
… | |
… | |
811 | </dd> |
920 | </dd> |
812 | <dd> |
921 | <dd> |
813 | <pre> |
922 | <pre> |
814 | # use Backspace = ^H |
923 | # use Backspace = ^H |
815 | $ stty erase ^H |
924 | $ stty erase ^H |
816 | $ rxvt</pre> |
925 | $ urxvt</pre> |
817 | </dd> |
926 | </dd> |
818 | <dd> |
927 | <dd> |
819 | <pre> |
928 | <pre> |
820 | # use Backspace = ^? |
929 | # use Backspace = ^? |
821 | $ stty erase ^? |
930 | $ stty erase ^? |
822 | $ rxvt</pre> |
931 | $ urxvt</pre> |
823 | </dd> |
|
|
824 | <dd> |
932 | </dd> |
|
|
933 | <dd> |
825 | <p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code> as documented in rxvt(7).</p> |
934 | <p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code> as documented in urxvt(7).</p> |
826 | </dd> |
935 | </dd> |
827 | <dd> |
936 | <dd> |
828 | <p>For an existing rxvt-unicode:</p> |
937 | <p>For an existing rxvt-unicode:</p> |
829 | </dd> |
938 | </dd> |
830 | <dd> |
939 | <dd> |
… | |
… | |
868 | There are some compile-time selections available via configure. Unless |
977 | There are some compile-time selections available via configure. Unless |
869 | you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can |
978 | you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can |
870 | use the `keysym' resource to alter the keystrings associated with keysyms. |
979 | use the `keysym' resource to alter the keystrings associated with keysyms. |
871 | </dd> |
980 | </dd> |
872 | <dd> |
981 | <dd> |
873 | <p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p> |
982 | <p>Here's an example for a URxvt session started using <code>urxvt -name URxvt</code></p> |
874 | </dd> |
983 | </dd> |
875 | <dd> |
984 | <dd> |
876 | <pre> |
985 | <pre> |
877 | URxvt.keysym.Home: \033[1~ |
986 | URxvt.keysym.Home: \033[1~ |
878 | URxvt.keysym.End: \033[4~ |
987 | URxvt.keysym.End: \033[4~ |
… | |
… | |
2833 | </dd> |
2942 | </dd> |
2834 | <p></p> |
2943 | <p></p> |
2835 | <dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong><br /> |
2944 | <dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong><br /> |
2836 | </dt> |
2945 | </dt> |
2837 | <dd> |
2946 | <dd> |
2838 | Enable extended ISO 14755 support (see rxvt(1), or |
2947 | Enable extended ISO 14755 support (see urxvt(1), or |
2839 | <em>doc/rxvt.1.txt</em>). Basic support (section 5.1) is enabled by |
2948 | <em>doc/rxvt.1.txt</em>). Basic support (section 5.1) is enabled by |
2840 | <code>--enable-frills</code>, while support for 5.2, 5.3 and 5.4 is enabled with |
2949 | <code>--enable-frills</code>, while support for 5.2, 5.3 and 5.4 is enabled with |
2841 | this switch. |
2950 | this switch. |
2842 | </dd> |
2951 | </dd> |
2843 | <p></p> |
2952 | <p></p> |