ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.html
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.7.html (file contents):
Revision 1.54 by root, Tue Jan 31 00:25:16 2006 UTC vs.
Revision 1.59 by root, Tue Jan 31 01:02:19 2006 UTC

… …
14 14
15 <li><a href="#name">NAME</a></li> 15 <li><a href="#name">NAME</a></li>
16 <li><a href="#synopsis">SYNOPSIS</a></li> 16 <li><a href="#synopsis">SYNOPSIS</a></li>
17 <li><a href="#description">DESCRIPTION</a></li> 17 <li><a href="#description">DESCRIPTION</a></li>
18 <li><a href="#frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></li> 18 <li><a href="#frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></li>
19 <ul>
20
21 <li><a href="#the_new_selection_selects_pieces_that_are_too_big__how_can_i_select_single_words">The new selection selects pieces that are too big, how can I select single words?</a></li>
22 <li><a href="#i_don_t_like_the_new_selection_popups_hotkeys_perl__how_do_i_change_disable_it">I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?</a></li>
23 <li><a href="#the_cursor_moves_when_selecting_text_in_the_current_input_line__how_do_i_switch_this_off">The cursor moves when selecting text in the current input line, how do I switch this off?</a></li>
24 <li><a href="#during_rlogin_ssh_telnet_etc__sessions__clicking_near_the_cursor_outputs_strange_escape_sequences__how_do_i_fix_this">During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?</a></li>
25 <li><a href="#why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></li>
26 <li><a href="#i_can_t_get_transparency_working__what_am_i_doing_wrong">I can't get transparency working, what am I doing wrong?</a></li>
27 <li><a href="#isn_t_rxvt_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt supposed to be small? Don't all those features bloat?</a></li>
28 <li><a href="#why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></li>
29 <li><a href="#does_it_support_tabs__can_i_have_a_tabbed_rxvtunicode">Does it support tabs, can I have a tabbed rxvt-unicode?</a></li>
30 <li><a href="#how_do_i_know_which_rxvtunicode_version_i_m_using">How do I know which rxvt-unicode version I'm using?</a></li>
31 <li><a href="#i_am_using_debian_gnu_linux_and_have_a_problem___">I am using Debian GNU/Linux and have a problem...</a></li>
32 <li><a href="#i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></li>
33 <li><a href="#i_need_to_make_it_setuid_setgid_to_support_utmp_ptys_on_my_os__is_this_safe">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></li>
34 <li><a href="#when_i_login_to_another_system_it_tells_me_about_missing_terminfo_data">When I log-in to another system it tells me about missing terminfo data?</a></li>
35 <li><a href="#tic_outputs_some_error_when_compiling_the_terminfo_entry_"><code>tic</code> outputs some error when compiling the terminfo entry.</a></li>
36 <li><a href="#bash_s_readline_does_not_work_correctly_under_rxvt_"><code>bash</code>'s readline does not work correctly under rxvt.</a></li>
37 <li><a href="#i_need_a_termcap_file_entry_">I need a termcap file entry.</a></li>
38 <li><a href="#why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></li>
39 <li><a href="#why_doesn_t_vim_emacs_etc__use_the_88_colour_mode">Why doesn't vim/emacs etc. use the 88 colour mode?</a></li>
40 <li><a href="#why_doesn_t_vim_emacs_etc__make_use_of_italic">Why doesn't vim/emacs etc. make use of italic?</a></li>
41 <li><a href="#why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></li>
42 <li><a href="#my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></li>
43 <li><a href="#rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></li>
44 <li><a href="#unicode_does_not_seem_to_work">Unicode does not seem to work?</a></li>
45 <li><a href="#why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></li>
46 <li><a href="#how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></li>
47 <li><a href="#why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></li>
48 <li><a href="#why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></li>
49 <li><a href="#on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></li>
50 <li><a href="#my_compose__multi_key__key_is_no_longer_working_">My Compose (Multi_key) key is no longer working.</a></li>
51 <li><a href="#i_cannot_type_ctrlshift2_to_get_an_ascii_nul_character_due_to_iso_14755">I cannot type <code>Ctrl-Shift-2</code> to get an ASCII NUL character due to ISO 14755</a></li>
52 <li><a href="#how_can_i_keep_rxvtunicode_from_using_reverse_video_so_much">How can I keep rxvt-unicode from using reverse video so much?</a></li>
53 <li><a href="#some_programs_assume_totally_weird_colours__red_instead_of_blue___how_can_i_fix_that">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></li>
54 <li><a href="#i_am_on_freebsd_and_rxvtunicode_does_not_seem_to_work_at_all_">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></li>
55 <li><a href="#i_use_solaris_9_and_it_doesn_t_compile_work_etc_">I use Solaris 9 and it doesn't compile/work/etc.</a></li>
56 <li><a href="#how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></li>
57 <li><a href="#how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></li>
58 <li><a href="#is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></li>
59 <li><a href="#can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></li>
60 <li><a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></li>
61 <li><a href="#why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></li>
62 <li><a href="#my_input_method_wants__some_encoding__but_i_want_utf8__what_can_i_do">My input method wants &lt;some encoding&gt; but I want UTF-8, what can I do?</a></li>
63 <li><a href="#rxvtunicode_crashes_when_the_x_input_method_changes_or_exits_">Rxvt-unicode crashes when the X Input Method changes or exits.</a></li>
64 <li><a href="#rxvtunicode_uses_gobs_of_memory__how_can_i_reduce_that">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></li>
65 <li><a href="#can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></li>
66 <li><a href="#rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></li>
67 <li><a href="#mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</a></li>
68 <li><a href="#what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></li>
69 <li><a href="#i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors. How do I change them?</a></li>
70 <li><a href="#how_can_i_start_rxvtd_in_a_racefree_way">How can I start rxvtd in a race-free way?</a></li>
71 <li><a href="#what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></li>
72 <li><a href="#i_don_t_like_the_keybindings__how_do_i_change_them">I don't like the key-bindings. How do I change them?</a></li>
73 <li><a href="#i_m_using_keyboard_model_xxx_that_has_extra_prior_next_insert_keys__how_do_i_make_use_of_them_for_example__the_sun_keyboard_type_4_has_the_following_mappings_that_rxvtunicode_doesn_t_recognize_">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize.</a></li>
74 <li><a href="#how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li>
75 <li><a href="#how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></li>
76 <li><a href="#how_do_i_compile_the_manual_pages_for_myself">How do I compile the manual pages for myself?</a></li>
77 <li><a href="#my_question_isn_t_answered_here__can_i_ask_a_human">My question isn't answered here, can I ask a human?</a></li>
78 </ul>
79
19 <li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li> 80 <li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li>
20 <li><a href="#description">DESCRIPTION</a></li> 81 <li><a href="#description">DESCRIPTION</a></li>
21 <li><a href="#definitions">Definitions</a></li> 82 <li><a href="#definitions">Definitions</a></li>
22 <li><a href="#values">Values</a></li> 83 <li><a href="#values">Values</a></li>
23 <li><a href="#escape_sequences">Escape Sequences</a></li> 84 <li><a href="#escape_sequences">Escape Sequences</a></li>
… …
60<a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p> 121<a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p>
61<p> 122<p>
62</p> 123</p>
63<hr /> 124<hr />
64<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1> 125<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>
65<dl> 126<p>
127</p>
66<dt><strong><a name="item_the_new_selection_selects_pieces_that_are_too_big_">The new selection selects pieces that are too big, how can I select 128<h2><a name="the_new_selection_selects_pieces_that_are_too_big__how_can_i_select_single_words">The new selection selects pieces that are too big, how can I select single words?</a></h2>
67single words?</a></strong><br /> 129<p>If you want to select e.g. alphanumeric words, you can use the following
68</dt> 130setting:</p>
69<dd>
70Yes. For example, if you want to select alphanumeric words, you can use
71the following resource:
72</dd>
73<dd>
74<pre> 131<pre>
75 URxvt.selection.pattern-0: ([[:word:]]+)</pre> 132 URxvt.selection.pattern-0: ([[:word:]]+)</pre>
76</dd>
77<dd>
78<p>If you click more than twice, the selection will be extended 133<p>If you click more than twice, the selection will be extended
79more and more.</p> 134more and more.</p>
80</dd>
81<dd>
82<p>To get a selection that is very similar to the old code, try this pattern:</p> 135<p>To get a selection that is very similar to the old code, try this pattern:</p>
83</dd>
84<dd>
85<pre> 136<pre>
86 URxvt.selection.pattern-0: ([^&quot;&amp;'()*,;&lt;=&gt;?@[\\\\]^`{|})]+)</pre> 137 URxvt.selection.pattern-0: ([^&quot;&amp;'()*,;&lt;=&gt;?@[\\\\]^`{|})]+)</pre>
87</dd>
88<dd>
89<p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also 138<p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also
90selects words like the old code.</p> 139selects words like the old code.</p>
91</dd> 140<p>
92<p></p> 141</p>
93<dt><strong><a name="item_i_don_27t_like_the_new_selection_2fpopups_2fhotkey">I don't like the new selection/popups/hotkeys/perl, how do I 142<h2><a name="i_don_t_like_the_new_selection_popups_hotkeys_perl__how_do_i_change_disable_it">I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?</a></h2>
94change/disable it?</a></strong><br />
95</dt>
96<dd>
97You can disable the perl extension completely by setting the 143<p>You can disable the perl extension completely by setting the
98<strong>perl-ext-common</strong> resource to the empty string, which also keeps 144<strong>perl-ext-common</strong> resource to the empty string, which also keeps
99rxvt-unicode from initialising perl, saving memory. 145rxvt-unicode from initialising perl, saving memory.</p>
100</dd>
101<dd>
102<p>If you only want to disable specific features, you first have to 146<p>If you only want to disable specific features, you first have to
103identify which perl extension is responsible. For this, read the section 147identify which perl extension is responsible. For this, read the section
104<strong>PREPACKAGED EXTENSIONS</strong> in the <code>rxvtperl(3)</code> manpage. For 148<strong>PREPACKAGED EXTENSIONS</strong> in the <code>rxvtperl(3)</code> manpage. For
105example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify 149example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify
106this <strong>perl-ext-common</strong> resource:</p> 150this <strong>perl-ext-common</strong> resource:</p>
107</dd>
108<dd>
109<pre> 151<pre>
110 URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre> 152 URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre>
111</dd>
112<dd>
113<p>This will keep the default extensions, but disable the two popup 153<p>This will keep the default extensions, but disable the two popup
114extensions. Some extensions can also be configured, for example, 154extensions. Some extensions can also be configured, for example,
115scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any 155scrollback search mode is triggered by <strong>M-s</strong>. You can move it to any
116other combination either by setting the <strong>searchable-scrollback</strong> resource:</p> 156other combination either by setting the <strong>searchable-scrollback</strong> resource:</p>
117</dd>
118<dd>
119<pre> 157<pre>
120 URxvt.searchable-scrollback: CM-s</pre> 158 URxvt.searchable-scrollback: CM-s</pre>
121</dd> 159<p>
122<p></p> 160</p>
161<h2><a name="the_cursor_moves_when_selecting_text_in_the_current_input_line__how_do_i_switch_this_off">The cursor moves when selecting text in the current input line, how do I switch this off?</a></h2>
162<p>See next entry.</p>
163<p>
164</p>
165<h2><a name="during_rlogin_ssh_telnet_etc__sessions__clicking_near_the_cursor_outputs_strange_escape_sequences__how_do_i_fix_this">During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?</a></h2>
166<p>These are caused by the <code>readline</code> perl extension. Under normal
167circumstances, it will move your cursor around when you click into the
168line that contains it. It tries hard not to do this at the wrong moment,
169but when running a program that doesn't parse cursor movements or in some
170cases during rlogin sessions, it fails to detect this properly.</p>
171<p>You can permamently switch this feature off by disabling the <code>readline</code>
172extension:</p>
173<pre>
174 URxvt.perl-ext-common: default,-readline</pre>
175<p>
176</p>
123<dt><strong><a name="item_why_doesn_27t_rxvt_2dunicode_read_my_resources_3f">Why doesn't rxvt-unicode read my resources?</a></strong><br /> 177<h2><a name="why_doesn_t_rxvtunicode_read_my_resources">Why doesn't rxvt-unicode read my resources?</a></h2>
124</dt>
125<dd>
126Well, why, indeed? It does, in a way very similar to other X 178<p>Well, why, indeed? It does, in a way very similar to other X
127applications. Most importantly, this means that if you or your OS loads 179applications. Most importantly, this means that if you or your OS loads
128resources into the X display (the right way to do it), rxvt-unicode will 180resources into the X display (the right way to do it), rxvt-unicode will
129ignore any resource files in your home directory. It will only read 181ignore any resource files in your home directory. It will only read
130<em>$HOME/.Xdefaults</em> when no resources are attached to the display. 182<em>$HOME/.Xdefaults</em> when no resources are attached to the display.</p>
131</dd>
132<dd>
133<p>If you have or use an <em>$HOME/.Xresources</em> file, chances are that 183<p>If you have or use an <em>$HOME/.Xresources</em> file, chances are that
134resources are loaded into your X-server. In this case, you have to 184resources are loaded into your X-server. In this case, you have to
135re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p> 185re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p>
136</dd>
137<dd>
138<p>Also consider the form resources have to use:</p> 186<p>Also consider the form resources have to use:</p>
139</dd>
140<dd>
141<pre> 187<pre>
142 URxvt.resource: value</pre> 188 URxvt.resource: value</pre>
143</dd>
144<dd>
145<p>If you want to use another form (there are lots of different ways of 189<p>If you want to use another form (there are lots of different ways of
146specifying resources), make sure you understand wether and why it 190specifying resources), make sure you understand wether and why it
147works. If unsure, use the form above.</p> 191works. If unsure, use the form above.</p>
148</dd> 192<p>
149<p></p> 193</p>
150<dt><strong><a name="item_i_can_27t_get_transparency_working_2c_what_am_i_do">I can't get transparency working, what am I doing wrong?</a></strong><br /> 194<h2><a name="i_can_t_get_transparency_working__what_am_i_doing_wrong">I can't get transparency working, what am I doing wrong?</a></h2>
151</dt>
152<dd>
153First of all, transparency isn't officially supported in rxvt-unicode, so 195<p>First of all, transparency isn't officially supported in rxvt-unicode, so
154you are mostly on your own. Do not bug the author about it (but you may 196you are mostly on your own. Do not bug the author about it (but you may
155bug everybody else). Also, if you can't get it working consider it a rite 197bug everybody else). Also, if you can't get it working consider it a rite
156of passage: ... and you failed. 198of passage: ... and you failed.</p>
157</dd>
158<dd>
159<p>Here are four ways to get transparency. <strong>Do</strong> read the manpage and option 199<p>Here are four ways to get transparency. <strong>Do</strong> read the manpage and option
160descriptions for the programs mentioned and rxvt-unicode. Really, do it!</p> 200descriptions for the programs mentioned and rxvt-unicode. Really, do it!</p>
161</dd>
162<dd>
163<p>1. Use inheritPixmap:</p> 201<p>1. Use inheritPixmap:</p>
164</dd>
165<dd>
166<pre> 202<pre>
167 Esetroot wallpaper.jpg 203 Esetroot wallpaper.jpg
168 rxvt -ip -tint red -sh 40</pre> 204 rxvt -ip -tint red -sh 40</pre>
169</dd>
170<dd>
171<p>That works. If you think it doesn't, you lack transparency and tinting 205<p>That works. If you think it doesn't, you lack transparency and tinting
172support, or you are unable to read.</p> 206support, or you are unable to read.</p>
173</dd>
174<dd>
175<p>2. Use a simple pixmap and emulate pseudo-transparency. This enables you 207<p>2. Use a simple pixmap and emulate pseudo-transparency. This enables you
176to use effects other than tinting and shading: Just shade/tint/whatever 208to use effects other than tinting and shading: Just shade/tint/whatever
177your picture with gimp:</p> 209your picture with gimp:</p>
178</dd>
179<dd>
180<pre> 210<pre>
181 convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm 211 convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
182 rxvt -pixmap background.xpm -pe automove-background</pre> 212 rxvt -pixmap background.xpm -pe automove-background</pre>
183</dd>
184<dd>
185<p>That works. If you think it doesn't, you lack XPM and Perl support, or you 213<p>That works. If you think it doesn't, you lack XPM and Perl support, or you
186are unable to read.</p> 214are unable to read.</p>
187</dd>
188<dd>
189<p>3. Use an ARGB visual:</p> 215<p>3. Use an ARGB visual:</p>
190</dd>
191<dd>
192<pre> 216<pre>
193 rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre> 217 rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre>
194</dd>
195<dd>
196<p>This requires XFT support, and the support of your X-server. If that 218<p>This requires XFT support, and the support of your X-server. If that
197doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't 219doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
198there yet, no matter what they claim. Rxvt-Unicode contains the neccessary 220there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
199bugfixes and workarounds for Xft and Xlib to make it work, but that 221bugfixes and workarounds for Xft and Xlib to make it work, but that
200doesn't mean that your WM has the required kludges in place.</p> 222doesn't mean that your WM has the required kludges in place.</p>
201</dd>
202<dd>
203<p>4. Use xcompmgr and let it do the job:</p> 223<p>4. Use xcompmgr and let it do the job:</p>
204</dd>
205<dd>
206<pre> 224<pre>
207 xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ 225 xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
208 -set _NET_WM_WINDOW_OPACITY 0xc0000000</pre> 226 -set _NET_WM_WINDOW_OPACITY 0xc0000000</pre>
209</dd>
210<dd>
211<p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code> 227<p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code>
212by other values to change the degree of opacity. If it doesn't work and 228by other values to change the degree of opacity. If it doesn't work and
213your server crashes, you got to keep the pieces.</p> 229your server crashes, you got to keep the pieces.</p>
214</dd> 230<p>
215<p></p> 231</p>
216<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 /> 232<h2><a name="isn_t_rxvt_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt supposed to be small? Don't all those features bloat?</a></h2>
217</dt>
218<dd>
219I often get asked about this, and I think, no, they didn't cause extra 233<p>I often get asked about this, and I think, no, they didn't cause extra
220bloat. If you compare a minimal rxvt and a minimal urxvt, you can see 234bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
221that the urxvt binary is larger (due to some encoding tables always being 235that the urxvt binary is larger (due to some encoding tables always being
222compiled in), but it actually uses less memory (RSS) after startup. Even 236compiled in), but it actually uses less memory (RSS) after startup. Even
223with <code>--disable-everything</code>, this comparison is a bit unfair, as many 237with <code>--disable-everything</code>, this comparison is a bit unfair, as many
224features unique to urxvt (locale, encoding conversion, iso14755 etc.) are 238features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
225already in use in this mode. 239already in use in this mode.</p>
226</dd>
227<dd>
228<pre> 240<pre>
229 text data bss drs rss filename 241 text data bss drs rss filename
230 98398 1664 24 15695 1824 rxvt --disable-everything 242 98398 1664 24 15695 1824 rxvt --disable-everything
231 188985 9048 66616 18222 1788 urxvt --disable-everything</pre> 243 188985 9048 66616 18222 1788 urxvt --disable-everything</pre>
232</dd>
233<dd>
234<p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which _is_ unfair, as this involves xft 244<p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which _is_ unfair, as this involves xft
235and full locale/XIM support which are quite bloaty inside libX11 and my 245and full locale/XIM support which are quite bloaty inside libX11 and my
236libc), the two diverge, but not unreasnobaly so.</p> 246libc), the two diverge, but not unreasnobaly so.</p>
237</dd>
238<dd>
239<pre> 247<pre>
240 text data bss drs rss filename 248 text data bss drs rss filename
241 163431 2152 24 20123 2060 rxvt --enable-everything 249 163431 2152 24 20123 2060 rxvt --enable-everything
242 1035683 49680 66648 29096 3680 urxvt --enable-everything</pre> 250 1035683 49680 66648 29096 3680 urxvt --enable-everything</pre>
243</dd>
244<dd>
245<p>The very large size of the text section is explained by the east-asian 251<p>The very large size of the text section is explained by the east-asian
246encoding tables, which, if unused, take up disk space but nothing else 252encoding tables, which, if unused, take up disk space but nothing else
247and can be compiled out unless you rely on X11 core fonts that use those 253and can be compiled out unless you rely on X11 core fonts that use those
248encodings. The BSS size comes from the 64k emergency buffer that my c++ 254encodings. The BSS size comes from the 64k emergency buffer that my c++
249compiler allocates (but of course doesn't use unless you are out of 255compiler allocates (but of course doesn't use unless you are out of
250memory). Also, using an xft font instead of a core font immediately adds a 256memory). Also, using an xft font instead of a core font immediately adds a
251few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when 257few megabytes of RSS. Xft indeed is responsible for a lot of RSS even when
252not used.</p> 258not used.</p>
253</dd>
254<dd>
255<p>Of course, due to every character using two or four bytes instead of one, 259<p>Of course, due to every character using two or four bytes instead of one,
256a large scrollback buffer will ultimately make rxvt-unicode use more 260a large scrollback buffer will ultimately make rxvt-unicode use more
257memory.</p> 261memory.</p>
258</dd>
259<dd>
260<p>Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this 262<p>Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
261still fares rather well. And compared to some monsters like gnome-terminal 263still fares rather well. And compared to some monsters like gnome-terminal
262(21152k + extra 4204k in separate processes) or konsole (22200k + extra 264(21152k + extra 4204k in separate processes) or konsole (22200k + extra
26343180k in daemons that stay around after exit, plus half a minute of 26543180k in daemons that stay around after exit, plus half a minute of
264startup time, including the hundreds of warnings it spits out), it fares 266startup time, including the hundreds of warnings it spits out), it fares
265extremely well *g*.</p> 267extremely well *g*.</p>
266</dd> 268<p>
267<p></p> 269</p>
268<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 /> 270<h2><a name="why_c____isn_t_that_unportable_bloated_uncool">Why C++, isn't that unportable/bloated/uncool?</a></h2>
269</dt>
270<dd>
271Is this a question? :) It comes up very often. The simple answer is: I had 271<p>Is this a question? :) It comes up very often. The simple answer is: I had
272to write it, and C++ allowed me to write and maintain it in a fraction 272to write it, and C++ allowed me to write and maintain it in a fraction
273of the time and effort (which is a scarce resource for me). Put even 273of the time and effort (which is a scarce resource for me). Put even
274shorter: It simply wouldn't exist without C++. 274shorter: It simply wouldn't exist without C++.</p>
275</dd>
276<dd>
277<p>My personal stance on this is that C++ is less portable than C, but in 275<p>My personal stance on this is that C++ is less portable than C, but in
278the case of rxvt-unicode this hardly matters, as its portability limits 276the case of rxvt-unicode this hardly matters, as its portability limits
279are defined by things like X11, pseudo terminals, locale support and unix 277are defined by things like X11, pseudo terminals, locale support and unix
280domain sockets, which are all less portable than C++ itself.</p> 278domain sockets, which are all less portable than C++ itself.</p>
281</dd>
282<dd>
283<p>Regarding the bloat, see the above question: It's easy to write programs 279<p>Regarding the bloat, see the above question: It's easy to write programs
284in C that use gobs of memory, an certainly possible to write programs in 280in C that use gobs of memory, an certainly possible to write programs in
285C++ that don't. C++ also often comes with large libraries, but this is 281C++ that don't. C++ also often comes with large libraries, but this is
286not necessarily the case with GCC. Here is what rxvt links against on my 282not necessarily the case with GCC. Here is what rxvt links against on my
287system with a minimal config:</p> 283system with a minimal config:</p>
288</dd>
289<dd>
290<pre> 284<pre>
291 libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 285 libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
292 libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaadde000) 286 libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaadde000)
293 libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab01d000) 287 libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab01d000)
294 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> 288 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>
295</dd>
296<dd>
297<p>And here is rxvt-unicode:</p> 289<p>And here is rxvt-unicode:</p>
298</dd>
299<dd>
300<pre> 290<pre>
301 libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 291 libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
302 libgcc_s.so.1 =&gt; /lib/libgcc_s.so.1 (0x00002aaaaada2000) 292 libgcc_s.so.1 =&gt; /lib/libgcc_s.so.1 (0x00002aaaaada2000)
303 libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaaeb0000) 293 libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaaeb0000)
304 libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab0ee000) 294 libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab0ee000)
305 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre> 295 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>
306</dd>
307<dd>
308<p>No large bloated libraries (of course, none were linked in statically), 296<p>No large bloated libraries (of course, none were linked in statically),
309except maybe libX11 :)</p> 297except maybe libX11 :)</p>
310</dd> 298<p>
311<p></p> 299</p>
312<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 /> 300<h2><a name="does_it_support_tabs__can_i_have_a_tabbed_rxvtunicode">Does it support tabs, can I have a tabbed rxvt-unicode?</a></h2>
313</dt>
314<dd>
315Beginning with version 7.3, there is a perl extension that implements a 301<p>Beginning with version 7.3, there is a perl extension that implements a
316simple tabbed terminal. It is installed by default, so any of these should 302simple tabbed terminal. It is installed by default, so any of these should
317give you tabs: 303give you tabs:</p>
318</dd>
319<dd>
320<pre> 304<pre>
321 rxvt -pe tabbed</pre> 305 rxvt -pe tabbed</pre>
322</dd>
323<dd>
324<pre> 306<pre>
325 URxvt.perl-ext-common: default,tabbed</pre> 307 URxvt.perl-ext-common: default,tabbed</pre>
326</dd>
327<dd>
328<p>It will also work fine with tabbing functionality of many window managers 308<p>It will also work fine with tabbing functionality of many window managers
329or similar tabbing programs, and its embedding-features allow it to be 309or similar tabbing programs, and its embedding-features allow it to be
330embedded into other programs, as witnessed by <em>doc/rxvt-tabbed</em> or 310embedded into other programs, as witnessed by <em>doc/rxvt-tabbed</em> or
331the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt 311the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt
332(murxvt) terminal as an example embedding application.</p> 312(murxvt) terminal as an example embedding application.</p>
333</dd> 313<p>
334<p></p> 314</p>
335<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 /> 315<h2><a name="how_do_i_know_which_rxvtunicode_version_i_m_using">How do I know which rxvt-unicode version I'm using?</a></h2>
336</dt>
337<dd>
338The version number is displayed with the usage (-h). Also the escape 316<p>The version number is displayed with the usage (-h). Also the escape
339sequence <code>ESC [ 8 n</code> sets the window title to the version number. When 317sequence <code>ESC [ 8 n</code> sets the window title to the version number. When
340using the rxvtc client, the version displayed is that of the 318using the rxvtc client, the version displayed is that of the
341daemon. 319daemon.</p>
342</dd> 320<p>
343<p></p> 321</p>
344<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 /> 322<h2><a name="i_am_using_debian_gnu_linux_and_have_a_problem___">I am using Debian GNU/Linux and have a problem...</a></h2>
345</dt>
346<dd>
347The Debian GNU/Linux package of rxvt-unicode in sarge contains large 323<p>The Debian GNU/Linux package of rxvt-unicode in sarge contains large
348patches that considerably change the behaviour of rxvt-unicode (but 324patches that considerably change the behaviour of rxvt-unicode (but
349unfortunately this notice has been removed). Before reporting a bug to 325unfortunately this notice has been removed). Before reporting a bug to
350the original rxvt-unicode author please download and install the genuine 326the original rxvt-unicode author please download and install the genuine
351version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce 327version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce
352the problem. If you cannot, chances are that the problems are specific to 328the problem. If you cannot, chances are that the problems are specific to
353Debian GNU/Linux, in which case it should be reported via the Debian Bug 329Debian GNU/Linux, in which case it should be reported via the Debian Bug
354Tracking System (use <code>reportbug</code> to report the bug). 330Tracking System (use <code>reportbug</code> to report the bug).</p>
355</dd>
356<dd>
357<p>For other problems that also affect the Debian package, you can and 331<p>For other problems that also affect the Debian package, you can and
358probably should use the Debian BTS, too, because, after all, it's also a 332probably should use the Debian BTS, too, because, after all, it's also a
359bug in the Debian version and it serves as a reminder for other users that 333bug in the Debian version and it serves as a reminder for other users that
360might encounter the same issue.</p> 334might encounter the same issue.</p>
361</dd> 335<p>
362<p></p> 336</p>
363<dt><strong><a name="item_i_am_maintaining_rxvt_2dunicode_for_distribution_2">I am maintaining rxvt-unicode for distribution/OS XXX, any 337<h2><a name="i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></h2>
364recommendation?</a></strong><br />
365</dt>
366<dd>
367You should build one binary with the default options. <em>configure</em> 338<p>You should build one binary with the default options. <em>configure</em>
368now enables most useful options, and the trend goes to making them 339now enables most useful options, and the trend goes to making them
369runtime-switchable, too, so there is usually no drawback to enbaling them, 340runtime-switchable, too, so there is usually no drawback to enbaling them,
370except higher disk and possibly memory usage. The perl interpreter should 341except higher disk and possibly memory usage. The perl interpreter should
371be enabled, as important functionality (menus, selection, likely more in 342be enabled, as important functionality (menus, selection, likely more in
372the future) depends on it. 343the future) depends on it.</p>
373</dd>
374<dd>
375<p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources 344<p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources
376system-wide (except maybe with <code>defaults</code>). This will result in useful 345system-wide (except maybe with <code>defaults</code>). This will result in useful
377behaviour. If your distribution aims at low memory, add an empty 346behaviour. If your distribution aims at low memory, add an empty
378<code>perl-ext-common</code> resource to the app-defaults file. This will keep the 347<code>perl-ext-common</code> resource to the app-defaults file. This will keep the
379perl interpreter disabled until the user enables it.</p> 348perl interpreter disabled until the user enables it.</p>
380</dd>
381<dd>
382<p>If you can/want build more binaries, I recommend building a minimal 349<p>If you can/want build more binaries, I recommend building a minimal
383one with <code>--disable-everything</code> (very useful) and a maximal one with 350one with <code>--disable-everything</code> (very useful) and a maximal one with
384<a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of 351<a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of
385encodings built-in that increase download times and are rarely used).</p> 352encodings built-in that increase download times and are rarely used).</p>
386</dd> 353<p>
387<p></p> 354</p>
388<dt><strong><a name="item_i_need_to_make_it_setuid_2fsetgid_to_support_utmp_">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></strong><br /> 355<h2><a name="i_need_to_make_it_setuid_setgid_to_support_utmp_ptys_on_my_os__is_this_safe">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></h2>
389</dt>
390<dd>
391It should be, starting with release 7.1. You are encouraged to properly 356<p>It should be, starting with release 7.1. You are encouraged to properly
392install urxvt with privileges necessary for your OS now. 357install urxvt with privileges necessary for your OS now.</p>
393</dd>
394<dd>
395<p>When rxvt-unicode detects that it runs setuid or setgid, it will fork 358<p>When rxvt-unicode detects that it runs setuid or setgid, it will fork
396into a helper process for privileged operations (pty handling on some 359into a helper process for privileged operations (pty handling on some
397systems, utmp/wtmp/lastlog handling on others) and drop privileges 360systems, utmp/wtmp/lastlog handling on others) and drop privileges
398immediately. This is much safer than most other terminals that keep 361immediately. This is much safer than most other terminals that keep
399privileges while running (but is more relevant to urxvt, as it contains 362privileges while running (but is more relevant to urxvt, as it contains
400things as perl interpreters, which might be ``helpful'' to attackers).</p> 363things as perl interpreters, which might be ``helpful'' to attackers).</p>
401</dd>
402<dd>
403<p>This forking is done as the very first within main(), which is very early 364<p>This forking is done as the very first within main(), which is very early
404and reduces possible bugs to initialisation code run before main(), or 365and reduces possible bugs to initialisation code run before main(), or
405things like the dynamic loader of your system, which should result in very 366things like the dynamic loader of your system, which should result in very
406little risk.</p> 367little risk.</p>
407</dd> 368<p>
408<p></p> 369</p>
409<dt><strong><a name="item_when_i_log_2din_to_another_system_it_tells_me_abou">When I log-in to another system it tells me about missing terminfo data?</a></strong><br /> 370<h2><a name="when_i_login_to_another_system_it_tells_me_about_missing_terminfo_data">When I log-in to another system it tells me about missing terminfo data?</a></h2>
410</dt>
411<dd>
412The terminal description used by rxvt-unicode is not as widely available 371<p>The terminal description used by rxvt-unicode is not as widely available
413as that for xterm, or even rxvt (for which the same problem often arises). 372as that for xterm, or even rxvt (for which the same problem often arises).</p>
414</dd>
415<dd>
416<p>The correct solution for this problem is to install the terminfo, this can 373<p>The correct solution for this problem is to install the terminfo, this can
417be done like this (with ncurses' infocmp):</p> 374be done like this (with ncurses' infocmp):</p>
418</dd>
419<dd>
420<pre> 375<pre>
421 REMOTE=remotesystem.domain 376 REMOTE=remotesystem.domain
422 infocmp rxvt-unicode | ssh $REMOTE &quot;cat &gt;/tmp/ti &amp;&amp; tic /tmp/ti&quot;</pre> 377 infocmp rxvt-unicode | ssh $REMOTE &quot;cat &gt;/tmp/ti &amp;&amp; tic /tmp/ti&quot;</pre>
423</dd>
424<dd>
425<p>... or by installing rxvt-unicode normally on the remote system,</p> 378<p>... or by installing rxvt-unicode normally on the remote system,</p>
426</dd>
427<dd>
428<p>If you cannot or do not want to do this, then you can simply set 379<p>If you cannot or do not want to do this, then you can simply set
429<code>TERM=rxvt</code> or even <code>TERM=xterm</code>, and live with the small number of 380<code>TERM=rxvt</code> or even <code>TERM=xterm</code>, and live with the small number of
430problems arising, which includes wrong keymapping, less and different 381problems arising, which includes wrong keymapping, less and different
431colours and some refresh errors in fullscreen applications. It's a nice 382colours and some refresh errors in fullscreen applications. It's a nice
432quick-and-dirty workaround for rare cases, though.</p> 383quick-and-dirty workaround for rare cases, though.</p>
433</dd>
434<dd>
435<p>If you always want to do this (and are fine with the consequences) you 384<p>If you always want to do this (and are fine with the consequences) you
436can either recompile rxvt-unicode with the desired TERM value or use a 385can either recompile rxvt-unicode with the desired TERM value or use a
437resource to set it:</p> 386resource to set it:</p>
438</dd>
439<dd>
440<pre> 387<pre>
441 URxvt.termName: rxvt</pre> 388 URxvt.termName: rxvt</pre>
442</dd>
443<dd>
444<p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace 389<p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace
445the rxvt terminfo file with the rxvt-unicode one.</p> 390the rxvt terminfo file with the rxvt-unicode one.</p>
446</dd> 391<p>
447<p></p> 392</p>
448<dt><strong><a name="item_tic_outputs_some_error_when_compiling_the_terminfo"><code>tic</code> outputs some error when compiling the terminfo entry.</a></strong><br /> 393<h2><a name="tic_outputs_some_error_when_compiling_the_terminfo_entry_"><code>tic</code> outputs some error when compiling the terminfo entry.</a></h2>
449</dt>
450<dd>
451Most likely it's the empty definition for <code>enacs=</code>. Just replace it by 394<p>Most likely it's the empty definition for <code>enacs=</code>. Just replace it by
452<code>enacs=\E[0@</code> and try again. 395<code>enacs=\E[0@</code> and try again.</p>
453</dd> 396<p>
454<p></p> 397</p>
455<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 /> 398<h2><a name="bash_s_readline_does_not_work_correctly_under_rxvt_"><code>bash</code>'s readline does not work correctly under rxvt.</a></h2>
456</dt> 399<p>See next entry.</p>
400<p>
401</p>
457<dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br /> 402<h2><a name="i_need_a_termcap_file_entry_">I need a termcap file entry.</a></h2>
458</dt>
459<dd>
460One reason you might want this is that some distributions or operating 403<p>One reason you might want this is that some distributions or operating
461systems still compile some programs using the long-obsoleted termcap 404systems still compile some programs using the long-obsoleted termcap
462library (Fedora Core's bash is one example) and rely on a termcap entry 405library (Fedora Core's bash is one example) and rely on a termcap entry
463for <code>rxvt-unicode</code>. 406for <code>rxvt-unicode</code>.</p>
464</dd>
465<dd>
466<p>You could use rxvt's termcap entry with resonable results in many cases. 407<p>You could use rxvt's termcap entry with resonable results in many cases.
467You can also create a termcap entry by using terminfo's infocmp program 408You can also create a termcap entry by using terminfo's infocmp program
468like this:</p> 409like this:</p>
469</dd>
470<dd>
471<pre> 410<pre>
472 infocmp -C rxvt-unicode</pre> 411 infocmp -C rxvt-unicode</pre>
473</dd>
474<dd>
475<p>Or you could use this termcap entry, generated by the command above:</p> 412<p>Or you could use this termcap entry, generated by the command above:</p>
476</dd>
477<dd>
478<pre> 413<pre>
479 rxvt-unicode|rxvt-unicode terminal (X Window System):\ 414 rxvt-unicode|rxvt-unicode terminal (X Window System):\
480 :am:bw:eo:km:mi:ms:xn:xo:\ 415 :am:bw:eo:km:mi:ms:xn:xo:\
481 :co#80:it#8:li#24:lm#0:\ 416 :co#80:it#8:li#24:lm#0:\
482 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ 417 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
… …
494 :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ 429 :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
495 :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ 430 :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
496 :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ 431 :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
497 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ 432 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
498 :vs=\E[?25h:</pre> 433 :vs=\E[?25h:</pre>
499</dd> 434<p>
500<p></p> 435</p>
501<dt><strong><a name="item_why_does_ls_no_longer_have_coloured_output_3f">Why does <code>ls</code> no longer have coloured output?</a></strong><br /> 436<h2><a name="why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></h2>
502</dt>
503<dd>
504The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to 437<p>The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to
505decide wether a terminal has colour, but uses it's own configuration 438decide wether a terminal has colour, but uses it's own configuration
506file. Needless to say, <code>rxvt-unicode</code> is not in it's default file (among 439file. Needless to say, <code>rxvt-unicode</code> is not in it's default file (among
507with most other terminals supporting colour). Either add: 440with most other terminals supporting colour). Either add:</p>
508</dd>
509<dd>
510<pre> 441<pre>
511 TERM rxvt-unicode</pre> 442 TERM rxvt-unicode</pre>
512</dd>
513<dd>
514<p>to <code>/etc/DIR_COLORS</code> or simply add:</p> 443<p>to <code>/etc/DIR_COLORS</code> or simply add:</p>
515</dd>
516<dd>
517<pre> 444<pre>
518 alias ls='ls --color=auto'</pre> 445 alias ls='ls --color=auto'</pre>
519</dd>
520<dd>
521<p>to your <code>.profile</code> or <code>.bashrc</code>.</p> 446<p>to your <code>.profile</code> or <code>.bashrc</code>.</p>
522</dd> 447<p>
523<p></p> 448</p>
524<dt><strong><a name="item_why_doesn_27t_vim_2femacs_etc_2e_use_the_88_colour">Why doesn't vim/emacs etc. use the 88 colour mode?</a></strong><br /> 449<h2><a name="why_doesn_t_vim_emacs_etc__use_the_88_colour_mode">Why doesn't vim/emacs etc. use the 88 colour mode?</a></h2>
525</dt> 450<p>See next entry.</p>
451<p>
452</p>
526<dt><strong><a name="item_why_doesn_27t_vim_2femacs_etc_2e_make_use_of_itali">Why doesn't vim/emacs etc. make use of italic?</a></strong><br /> 453<h2><a name="why_doesn_t_vim_emacs_etc__make_use_of_italic">Why doesn't vim/emacs etc. make use of italic?</a></h2>
527</dt> 454<p>See next entry.</p>
455<p>
456</p>
528<dt><strong><a name="item_why_are_the_secondary_screen_2drelated_options_not">Why are the secondary screen-related options not working properly?</a></strong><br /> 457<h2><a name="why_are_the_secondary_screenrelated_options_not_working_properly">Why are the secondary screen-related options not working properly?</a></h2>
529</dt>
530<dd>
531Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged 458<p>Make sure you are using <code>TERM=rxvt-unicode</code>. Some pre-packaged
532distributions (most notably Debian GNU/Linux) break rxvt-unicode 459distributions (most notably Debian GNU/Linux) break rxvt-unicode
533by setting <code>TERM</code> to <code>rxvt</code>, which doesn't have these extra 460by setting <code>TERM</code> to <code>rxvt</code>, which doesn't have these extra
534features. Unfortunately, some of these (most notably, again, Debian 461features. Unfortunately, some of these (most notably, again, Debian
535GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo 462GNU/Linux) furthermore fail to even install the <code>rxvt-unicode</code> terminfo
536file, so you will need to install it on your own (See the question <strong>When 463file, so you will need to install it on your own (See the question <strong>When
537I log-in to another system it tells me about missing terminfo data?</strong> on 464I log-in to another system it tells me about missing terminfo data?</strong> on
538how to do this). 465how to do this).</p>
539</dd> 466<p>
540<p></p> 467</p>
541<dt><strong><a name="item_my_numerical_keypad_acts_weird_and_generates_diffe">My numerical keypad acts weird and generates differing output?</a></strong><br /> 468<h2><a name="my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></h2>
542</dt>
543<dd>
544Some Debian GNUL/Linux users seem to have this problem, although no 469<p>Some Debian GNUL/Linux users seem to have this problem, although no
545specific details were reported so far. It is possible that this is caused 470specific details were reported so far. It is possible that this is caused
546by the wrong <code>TERM</code> setting, although the details of wether and how 471by the wrong <code>TERM</code> setting, although the details of wether and how
547this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible 472this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible
548keymap. See the answer to the previous question, and please report if that 473keymap. See the answer to the previous question, and please report if that
549helped. 474helped.</p>
550</dd> 475<p>
551<p></p> 476</p>
552<dt><strong><a name="item_rxvt_2dunicode_does_not_seem_to_understand_the_sel">Rxvt-unicode does not seem to understand the selected encoding?</a></strong><br /> 477<h2><a name="rxvtunicode_does_not_seem_to_understand_the_selected_encoding">Rxvt-unicode does not seem to understand the selected encoding?</a></h2>
553</dt> 478<p>See next entry.</p>
479<p>
480</p>
554<dt><strong><a name="item_unicode_does_not_seem_to_work_3f">Unicode does not seem to work?</a></strong><br /> 481<h2><a name="unicode_does_not_seem_to_work">Unicode does not seem to work?</a></h2>
555</dt>
556<dd>
557If you encounter strange problems like typing an accented character but 482<p>If you encounter strange problems like typing an accented character but
558getting two unrelated other characters or similar, or if program output is 483getting two unrelated other characters or similar, or if program output is
559subtly garbled, then you should check your locale settings. 484subtly garbled, then you should check your locale settings.</p>
560</dd>
561<dd>
562<p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the 485<p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the
563programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the 486programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the
564login script running within the rxvt-unicode window changes the locale to 487login script running within the rxvt-unicode window changes the locale to
565something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p> 488something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p>
566</dd>
567<dd>
568<p>The best thing is to fix your startup environment, as you will likely run 489<p>The best thing is to fix your startup environment, as you will likely run
569into other problems. If nothing works you can try this in your .profile.</p> 490into other problems. If nothing works you can try this in your .profile.</p>
570</dd>
571<dd>
572<pre> 491<pre>
573 printf '\e]701;%s\007' &quot;$LC_CTYPE&quot;</pre> 492 printf '\e]701;%s\007' &quot;$LC_CTYPE&quot;</pre>
574</dd>
575<dd>
576<p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not 493<p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not
577supported on your systems. Some systems have a <code>locale</code> command which 494supported on your systems. Some systems have a <code>locale</code> command which
578displays this (also, <code>perl -e0</code> can be used to check locale settings, as 495displays this (also, <code>perl -e0</code> can be used to check locale settings, as
579it will complain loudly if it cannot set the locale). If it displays something 496it will complain loudly if it cannot set the locale). If it displays something
580like:</p> 497like:</p>
581</dd>
582<dd>
583<pre> 498<pre>
584 locale: Cannot set LC_CTYPE to default locale: ...</pre> 499 locale: Cannot set LC_CTYPE to default locale: ...</pre>
585</dd>
586<dd>
587<p>Then the locale you specified is not supported on your system.</p> 500<p>Then the locale you specified is not supported on your system.</p>
588</dd>
589<dd>
590<p>If nothing works and you are sure that everything is set correctly then 501<p>If nothing works and you are sure that everything is set correctly then
591you will need to remember a little known fact: Some programs just don't 502you will need to remember a little known fact: Some programs just don't
592support locales :(</p> 503support locales :(</p>
593</dd> 504<p>
594<p></p> 505</p>
595<dt><strong><a name="item_why_do_some_characters_look_so_much_different_than">Why do some characters look so much different than others?</a></strong><br /> 506<h2><a name="why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></h2>
596</dt> 507<p>See next entry.</p>
508<p>
509</p>
597<dt><strong><a name="item_how_does_rxvt_2dunicode_choose_fonts_3f">How does rxvt-unicode choose fonts?</a></strong><br /> 510<h2><a name="how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></h2>
598</dt>
599<dd>
600Most fonts do not contain the full range of Unicode, which is 511<p>Most fonts do not contain the full range of Unicode, which is
601fine. Chances are that the font you (or the admin/package maintainer of 512fine. Chances are that the font you (or the admin/package maintainer of
602your system/os) have specified does not cover all the characters you want 513your system/os) have specified does not cover all the characters you want
603to display. 514to display.</p>
604</dd>
605<dd>
606<p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement 515<p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement
607font. Often the result is fine, but sometimes the chosen font looks 516font. Often the result is fine, but sometimes the chosen font looks
608bad/ugly/wrong. Some fonts have totally strange characters that don't 517bad/ugly/wrong. Some fonts have totally strange characters that don't
609resemble the correct glyph at all, and rxvt-unicode lacks the artificial 518resemble the correct glyph at all, and rxvt-unicode lacks the artificial
610intelligence to detect that a specific glyph is wrong: it has to believe 519intelligence to detect that a specific glyph is wrong: it has to believe
611the font that the characters it claims to contain indeed look correct.</p> 520the font that the characters it claims to contain indeed look correct.</p>
612</dd>
613<dd>
614<p>In that case, select a font of your taste and add it to the font list, 521<p>In that case, select a font of your taste and add it to the font list,
615e.g.:</p> 522e.g.:</p>
616</dd>
617<dd>
618<pre> 523<pre>
619 rxvt -fn basefont,font2,font3...</pre> 524 rxvt -fn basefont,font2,font3...</pre>
620</dd>
621<dd>
622<p>When rxvt-unicode sees a character, it will first look at the base 525<p>When rxvt-unicode sees a character, it will first look at the base
623font. If the base font does not contain the character, it will go to the 526font. If the base font does not contain the character, it will go to the
624next font, and so on. Specifying your own fonts will also speed up this 527next font, and so on. Specifying your own fonts will also speed up this
625search and use less resources within rxvt-unicode and the X-server.</p> 528search and use less resources within rxvt-unicode and the X-server.</p>
626</dd>
627<dd>
628<p>The only limitation is that none of the fonts may be larger than the base 529<p>The only limitation is that none of the fonts may be larger than the base
629font, as the base font defines the terminal character cell size, which 530font, as the base font defines the terminal character cell size, which
630must be the same due to the way terminals work.</p> 531must be the same due to the way terminals work.</p>
631</dd> 532<p>
632<p></p> 533</p>
633<dt><strong><a name="item_why_do_some_chinese_characters_look_so_different_t">Why do some chinese characters look so different than others?</a></strong><br /> 534<h2><a name="why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></h2>
634</dt>
635<dd>
636This is because there is a difference between script and language -- 535<p>This is because there is a difference between script and language --
637rxvt-unicode does not know which language the text that is output is, 536rxvt-unicode does not know which language the text that is output is,
638as it only knows the unicode character codes. If rxvt-unicode first 537as it only knows the unicode character codes. If rxvt-unicode first
639sees a japanese/chinese character, it might choose a japanese font for 538sees a japanese/chinese character, it might choose a japanese font for
640display. Subsequent japanese characters will use that font. Now, many 539display. Subsequent japanese characters will use that font. Now, many
641chinese characters aren't represented in japanese fonts, so when the first 540chinese characters aren't represented in japanese fonts, so when the first
642non-japanese character comes up, rxvt-unicode will look for a chinese font 541non-japanese character comes up, rxvt-unicode will look for a chinese font
643-- unfortunately at this point, it will still use the japanese font for 542-- unfortunately at this point, it will still use the japanese font for
644chinese characters that are also in the japanese font. 543chinese characters that are also in the japanese font.</p>
645</dd>
646<dd>
647<p>The workaround is easy: just tag a chinese font at the end of your font 544<p>The workaround is easy: just tag a chinese font at the end of your font
648list (see the previous question). The key is to view the font list as 545list (see the previous question). The key is to view the font list as
649a preference list: If you expect more japanese, list a japanese font 546a preference list: If you expect more japanese, list a japanese font
650first. If you expect more chinese, put a chinese font first.</p> 547first. If you expect more chinese, put a chinese font first.</p>
651</dd>
652<dd>
653<p>In the future it might be possible to switch language preferences at 548<p>In the future it might be possible to switch language preferences at
654runtime (the internal data structure has no problem with using different 549runtime (the internal data structure has no problem with using different
655fonts for the same character at the same time, but no interface for this 550fonts for the same character at the same time, but no interface for this
656has been designed yet).</p> 551has been designed yet).</p>
657</dd>
658<dd>
659<p>Until then, you might get away with switching fonts at runtime (see <a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a> later in this document).</p> 552<p>Until then, you might get away with switching fonts at runtime (see <a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a> later in this document).</p>
660</dd> 553<p>
661<p></p> 554</p>
662<dt><strong><a name="item_why_does_rxvt_2dunicode_sometimes_leave_pixel_drop">Why does rxvt-unicode sometimes leave pixel droppings?</a></strong><br /> 555<h2><a name="why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></h2>
663</dt>
664<dd>
665Most fonts were not designed for terminal use, which means that character 556<p>Most fonts were not designed for terminal use, which means that character
666size varies a lot. A font that is otherwise fine for terminal use might 557size varies a lot. A font that is otherwise fine for terminal use might
667contain some characters that are simply too wide. Rxvt-unicode will avoid 558contain some characters that are simply too wide. Rxvt-unicode will avoid
668these characters. For characters that are just ``a bit'' too wide a special 559these characters. For characters that are just ``a bit'' too wide a special
669``careful'' rendering mode is used that redraws adjacent characters. 560``careful'' rendering mode is used that redraws adjacent characters.</p>
670</dd>
671<dd>
672<p>All of this requires that fonts do not lie about character sizes, 561<p>All of this requires that fonts do not lie about character sizes,
673however: Xft fonts often draw glyphs larger than their acclaimed bounding 562however: Xft fonts often draw glyphs larger than their acclaimed bounding
674box, and rxvt-unicode has no way of detecting this (the correct way is to 563box, and rxvt-unicode has no way of detecting this (the correct way is to
675ask for the character bounding box, which unfortunately is wrong in these 564ask for the character bounding box, which unfortunately is wrong in these
676cases).</p> 565cases).</p>
677</dd>
678<dd>
679<p>It's not clear (to me at least), wether this is a bug in Xft, freetype, 566<p>It's not clear (to me at least), wether this is a bug in Xft, freetype,
680or the respective font. If you encounter this problem you might try using 567or the respective font. If you encounter this problem you might try using
681the <code>-lsp</code> option to give the font more height. If that doesn't work, you 568the <code>-lsp</code> option to give the font more height. If that doesn't work, you
682might be forced to use a different font.</p> 569might be forced to use a different font.</p>
683</dd>
684<dd>
685<p>All of this is not a problem when using X11 core fonts, as their bounding 570<p>All of this is not a problem when using X11 core fonts, as their bounding
686box data is correct.</p> 571box data is correct.</p>
687</dd> 572<p>
688<p></p> 573</p>
689<dt><strong><a name="item_on_solaris_9_2c_many_line_2ddrawing_characters_are">On Solaris 9, many line-drawing characters are too wide.</a></strong><br /> 574<h2><a name="on_solaris_9__many_linedrawing_characters_are_too_wide_">On Solaris 9, many line-drawing characters are too wide.</a></h2>
690</dt>
691<dd>
692Seems to be a known bug, read 575<p>Seems to be a known bug, read
693<a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the 576<a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the
694following ugly workaround to get non-double-wide-characters working: 577following ugly workaround to get non-double-wide-characters working:</p>
695</dd>
696<dd>
697<pre> 578<pre>
698 #define wcwidth(x) wcwidth(x) &gt; 1 ? 1 : wcwidth(x)</pre> 579 #define wcwidth(x) wcwidth(x) &gt; 1 ? 1 : wcwidth(x)</pre>
699</dd> 580<p>
700<p></p> 581</p>
701<dt><strong><a name="item_compose">My Compose (Multi_key) key is no longer working.</a></strong><br /> 582<h2><a name="my_compose__multi_key__key_is_no_longer_working_">My Compose (Multi_key) key is no longer working.</a></h2>
702</dt>
703<dd>
704The most common causes for this are that either your locale is not set 583<p>The most common causes for this are that either your locale is not set
705correctly, or you specified a <strong>preeditStyle</strong> that is not supported by 584correctly, or you specified a <strong>preeditStyle</strong> that is not supported by
706your input method. For example, if you specified <strong>OverTheSpot</strong> and 585your input method. For example, if you specified <strong>OverTheSpot</strong> and
707your input method (e.g. the default input method handling Compose keys) 586your input method (e.g. the default input method handling Compose keys)
708does not support this (for instance because it is not visual), then 587does not support this (for instance because it is not visual), then
709rxvt-unicode will continue without an input method. 588rxvt-unicode will continue without an input method.</p>
710</dd>
711<dd>
712<p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than 589<p>In this case either do not specify a <strong>preeditStyle</strong> or specify more than
713one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p> 590one pre-edit style, such as <strong>OverTheSpot,Root,None</strong>.</p>
714</dd> 591<p>
715<p></p> 592</p>
716<dt><strong><a name="item_i_cannot_type_ctrl_2dshift_2d2_to_get_an_ascii_nul">I cannot type <code>Ctrl-Shift-2</code> to get an ASCII NUL character due to ISO 14755</a></strong><br /> 593<h2><a name="i_cannot_type_ctrlshift2_to_get_an_ascii_nul_character_due_to_iso_14755">I cannot type <code>Ctrl-Shift-2</code> to get an ASCII NUL character due to ISO 14755</a></h2>
717</dt>
718<dd>
719Either try <code>Ctrl-2</code> alone (it often is mapped to ASCII NUL even on 594<p>Either try <code>Ctrl-2</code> alone (it often is mapped to ASCII NUL even on
720international keyboards) or simply use ISO 14755 support to your 595international keyboards) or simply use ISO 14755 support to your
721advantage, typing &lt;Ctrl-Shift-0&gt; to get a ASCII NUL. This works for other 596advantage, typing &lt;Ctrl-Shift-0&gt; to get a ASCII NUL. This works for other
722codes, too, such as <code>Ctrl-Shift-1-d</code> to type the default telnet escape 597codes, too, such as <code>Ctrl-Shift-1-d</code> to type the default telnet escape
723character and so on. 598character and so on.</p>
724</dd> 599<p>
725<p></p> 600</p>
726<dt><strong><a name="item_how_can_i_keep_rxvt_2dunicode_from_using_reverse_v">How can I keep rxvt-unicode from using reverse video so much?</a></strong><br /> 601<h2><a name="how_can_i_keep_rxvtunicode_from_using_reverse_video_so_much">How can I keep rxvt-unicode from using reverse video so much?</a></h2>
727</dt>
728<dd>
729First of all, make sure you are running with the right terminal settings 602<p>First of all, make sure you are running with the right terminal settings
730(<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then 603(<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then
731make sure you have specified colours for italic and bold, as otherwise 604make sure you have specified colours for italic and bold, as otherwise
732rxvt-unicode might use reverse video to simulate the effect: 605rxvt-unicode might use reverse video to simulate the effect:</p>
733</dd>
734<dd>
735<pre> 606<pre>
736 URxvt.colorBD: white 607 URxvt.colorBD: white
737 URxvt.colorIT: green</pre> 608 URxvt.colorIT: green</pre>
738</dd> 609<p>
739<p></p> 610</p>
740<dt><strong><a name="item_colours">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></strong><br /> 611<h2><a name="some_programs_assume_totally_weird_colours__red_instead_of_blue___how_can_i_fix_that">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></h2>
741</dt>
742<dd>
743For some unexplainable reason, some rare programs assume a very weird 612<p>For some unexplainable reason, some rare programs assume a very weird
744colour palette when confronted with a terminal with more than the standard 613colour palette when confronted with a terminal with more than the standard
7458 colours (rxvt-unicode supports 88). The right fix is, of course, to fix 6148 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
746these programs not to assume non-ISO colours without very good reasons. 615these programs not to assume non-ISO colours without very good reasons.</p>
747</dd>
748<dd>
749<p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo 616<p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo
750definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will 617definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will
751fix colours but keep you from using other rxvt-unicode features.</p> 618fix colours but keep you from using other rxvt-unicode features.</p>
752</dd> 619<p>
753<p></p> 620</p>
754<dt><strong><a name="item_i_am_on_freebsd_and_rxvt_2dunicode_does_not_seem_t">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></strong><br /> 621<h2><a name="i_am_on_freebsd_and_rxvtunicode_does_not_seem_to_work_at_all_">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></h2>
755</dt>
756<dd>
757Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined 622<p>Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined
758in your compile environment, or an implementation that implements it, 623in your compile environment, or an implementation that implements it,
759wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that 624wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that
760<strong>wchar_t</strong> is represented as unicode. 625<strong>wchar_t</strong> is represented as unicode.</p>
761</dd>
762<dd>
763<p>As you might have guessed, FreeBSD does neither define this symobl nor 626<p>As you might have guessed, FreeBSD does neither define this symobl nor
764does it support it. Instead, it uses it's own internal representation of 627does it support it. Instead, it uses it's own internal representation of
765<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p> 628<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p>
766</dd>
767<dd>
768<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and 629<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and
769<code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p> 630<code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p>
770</dd>
771<dd>
772<p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language 631<p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language
773apps in an OS, as using a locale-dependent (and non-standardized) 632apps in an OS, as using a locale-dependent (and non-standardized)
774representation of <strong>wchar_t</strong> makes it impossible to convert between 633representation of <strong>wchar_t</strong> makes it impossible to convert between
775<strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding 634<strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding
776without implementing OS-specific-wrappers for each and every locale. There 635without implementing OS-specific-wrappers for each and every locale. There
777simply are no APIs to convert <strong>wchar_t</strong> into anything except the current 636simply are no APIs to convert <strong>wchar_t</strong> into anything except the current
778locale encoding.</p> 637locale encoding.</p>
779</dd>
780<dd>
781<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this 638<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this
782by carrying their own replacement functions for character set handling 639by carrying their own replacement functions for character set handling
783with them, and either implementing OS-dependent hacks or doing multiple 640with them, and either implementing OS-dependent hacks or doing multiple
784conversions (which is slow and unreliable in case the OS implements 641conversions (which is slow and unreliable in case the OS implements
785encodings slightly different than the terminal emulator).</p> 642encodings slightly different than the terminal emulator).</p>
786</dd>
787<dd>
788<p>The rxvt-unicode author insists that the right way to fix this is in the 643<p>The rxvt-unicode author insists that the right way to fix this is in the
789system libraries once and for all, instead of forcing every app to carry 644system libraries once and for all, instead of forcing every app to carry
790complete replacements for them :)</p> 645complete replacements for them :)</p>
791</dd> 646<p>
792<p></p> 647</p>
793<dt><strong><a name="item_i_use_solaris_9_and_it_doesn_27t_compile_2fwork_2f">I use Solaris 9 and it doesn't compile/work/etc.</a></strong><br /> 648<h2><a name="i_use_solaris_9_and_it_doesn_t_compile_work_etc_">I use Solaris 9 and it doesn't compile/work/etc.</a></h2>
794</dt>
795<dd>
796Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst 649<p>Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst
797problems with <code>wcwidth</code> and a compile problem. 650problems with <code>wcwidth</code> and a compile problem.</p>
798</dd> 651<p>
799<p></p> 652</p>
800<dt><strong><a name="item_how_can_i_use_rxvt_2dunicode_under_cygwin_3f">How can I use rxvt-unicode under cygwin?</a></strong><br /> 653<h2><a name="how_can_i_use_rxvtunicode_under_cygwin">How can I use rxvt-unicode under cygwin?</a></h2>
801</dt>
802<dd>
803rxvt-unicode should compile and run out of the box on cygwin, using 654<p>rxvt-unicode should compile and run out of the box on cygwin, using
804the X11 libraries that come with cygwin. libW11 emulation is no 655the X11 libraries that come with cygwin. libW11 emulation is no
805longer supported (and makes no sense, either, as it only supported a 656longer supported (and makes no sense, either, as it only supported a
806single font). I recommend starting the X-server in <code>-multiwindow</code> or 657single font). I recommend starting the X-server in <code>-multiwindow</code> or
807<code>-rootless</code> mode instead, which will result in similar look&amp;feel as the 658<code>-rootless</code> mode instead, which will result in similar look&amp;feel as the
808old libW11 emulation. 659old libW11 emulation.</p>
809</dd>
810<dd>
811<p>At the time of this writing, cygwin didn't seem to support any multi-byte 660<p>At the time of this writing, cygwin didn't seem to support any multi-byte
812encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited 661encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited
813to 8-bit encodings.</p> 662to 8-bit encodings.</p>
814</dd> 663<p>
815<p></p> 664</p>
816<dt><strong><a name="item_how_does_rxvt_2dunicode_determine_the_encoding_to_">How does rxvt-unicode determine the encoding to use?</a></strong><br /> 665<h2><a name="how_does_rxvtunicode_determine_the_encoding_to_use">How does rxvt-unicode determine the encoding to use?</a></h2>
817</dt> 666<p>See next entry.</p>
667<p>
668</p>
818<dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br /> 669<h2><a name="is_there_an_option_to_switch_encodings">Is there an option to switch encodings?</a></h2>
819</dt>
820<dd>
821Unlike some other terminals, rxvt-unicode has no encoding switch, and no 670<p>Unlike some other terminals, rxvt-unicode has no encoding switch, and no
822specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about 671specific ``utf-8'' mode, such as xterm. In fact, it doesn't even know about
823UTF-8 or any other encodings with respect to terminal I/O. 672UTF-8 or any other encodings with respect to terminal I/O.</p>
824</dd>
825<dd>
826<p>The reasons is that there exists a perfectly fine mechanism for selecting 673<p>The reasons is that there exists a perfectly fine mechanism for selecting
827the encoding, doing I/O and (most important) communicating this to all 674the encoding, doing I/O and (most important) communicating this to all
828applications so everybody agrees on character properties such as width 675applications so everybody agrees on character properties such as width
829and code number. This mechanism is the <em>locale</em>. Applications not using 676and code number. This mechanism is the <em>locale</em>. Applications not using
830that info will have problems (for example, <code>xterm</code> gets the width of 677that info will have problems (for example, <code>xterm</code> gets the width of
831characters wrong as it uses it's own, locale-independent table under all 678characters wrong as it uses it's own, locale-independent table under all
832locales).</p> 679locales).</p>
833</dd>
834<dd>
835<p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All 680<p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All
836programs doing the same (that is, most) will automatically agree in the 681programs doing the same (that is, most) will automatically agree in the
837interpretation of characters.</p> 682interpretation of characters.</p>
838</dd>
839<dd>
840<p>Unfortunately, there is no system-independent way to select locales, nor 683<p>Unfortunately, there is no system-independent way to select locales, nor
841is there a standard on how locale specifiers will look like.</p> 684is there a standard on how locale specifiers will look like.</p>
842</dd>
843<dd>
844<p>On most systems, the content of the <code>LC_CTYPE</code> environment variable 685<p>On most systems, the content of the <code>LC_CTYPE</code> environment variable
845contains an arbitrary string which corresponds to an already-installed 686contains an arbitrary string which corresponds to an already-installed
846locale. Common names for locales are <code>en_US.UTF-8</code>, <code>de_DE.ISO-8859-15</code>, 687locale. Common names for locales are <code>en_US.UTF-8</code>, <code>de_DE.ISO-8859-15</code>,
847<code>ja_JP.EUC-JP</code>, i.e. <code>language_country.encoding</code>, but other forms 688<code>ja_JP.EUC-JP</code>, i.e. <code>language_country.encoding</code>, but other forms
848(i.e. <code>de</code> or <code>german</code>) are also common.</p> 689(i.e. <code>de</code> or <code>german</code>) are also common.</p>
849</dd>
850<dd>
851<p>Rxvt-unicode ignores all other locale categories, and except for 690<p>Rxvt-unicode ignores all other locale categories, and except for
852the encoding, ignores country or language-specific settings, 691the encoding, ignores country or language-specific settings,
853i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to 692i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to
854rxvt-unicode.</p> 693rxvt-unicode.</p>
855</dd>
856<dd>
857<p>If you want to use a specific encoding you have to make sure you start 694<p>If you want to use a specific encoding you have to make sure you start
858rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p> 695rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p>
859</dd> 696<p>
860<p></p> 697</p>
861<dt><strong><a name="item_can_i_switch_locales_at_runtime_3f">Can I switch locales at runtime?</a></strong><br /> 698<h2><a name="can_i_switch_locales_at_runtime">Can I switch locales at runtime?</a></h2>
862</dt>
863<dd>
864Yes, using an escape sequence. Try something like this, which sets 699<p>Yes, using an escape sequence. Try something like this, which sets
865rxvt-unicode's idea of <code>LC_CTYPE</code>. 700rxvt-unicode's idea of <code>LC_CTYPE</code>.</p>
866</dd>
867<dd>
868<pre> 701<pre>
869 printf '\e]701;%s\007' ja_JP.SJIS</pre> 702 printf '\e]701;%s\007' ja_JP.SJIS</pre>
870</dd>
871<dd>
872<p>See also the previous answer.</p> 703<p>See also the previous answer.</p>
873</dd>
874<dd>
875<p>Sometimes this capability is rather handy when you want to work in 704<p>Sometimes this capability is rather handy when you want to work in
876one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it 705one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it
877(e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which 706(e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which
878first switches to a locale supported by xjdic and back later:</p> 707first switches to a locale supported by xjdic and back later:</p>
879</dd>
880<dd>
881<pre> 708<pre>
882 printf '\e]701;%s\007' ja_JP.SJIS 709 printf '\e]701;%s\007' ja_JP.SJIS
883 xjdic -js 710 xjdic -js
884 printf '\e]701;%s\007' de_DE.UTF-8</pre> 711 printf '\e]701;%s\007' de_DE.UTF-8</pre>
885</dd>
886<dd>
887<p>You can also use xterm's <code>luit</code> program, which usually works fine, except 712<p>You can also use xterm's <code>luit</code> program, which usually works fine, except
888for some locales where character width differs between program- and 713for some locales where character width differs between program- and
889rxvt-unicode-locales.</p> 714rxvt-unicode-locales.</p>
890</dd> 715<p>
891<p></p> 716</p>
892<dt><strong><a name="item_can_i_switch_the_fonts_at_runtime_3f">Can I switch the fonts at runtime?</a></strong><br /> 717<h2><a name="can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></h2>
893</dt>
894<dd>
895Yes, using an escape sequence. Try something like this, which has the same 718<p>Yes, using an escape sequence. Try something like this, which has the same
896effect as using the <code>-fn</code> switch, and takes effect immediately: 719effect as using the <code>-fn</code> switch, and takes effect immediately:</p>
897</dd>
898<dd>
899<pre> 720<pre>
900 printf '\e]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre> 721 printf '\e]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre>
901</dd>
902<dd>
903<p>This is useful if you e.g. work primarily with japanese (and prefer a 722<p>This is useful if you e.g. work primarily with japanese (and prefer a
904japanese font), but you have to switch to chinese temporarily, where 723japanese font), but you have to switch to chinese temporarily, where
905japanese fonts would only be in your way.</p> 724japanese fonts would only be in your way.</p>
906</dd>
907<dd>
908<p>You can think of this as a kind of manual ISO-2022 switching.</p> 725<p>You can think of this as a kind of manual ISO-2022 switching.</p>
909</dd> 726<p>
910<p></p> 727</p>
911<dt><strong><a name="item_why_do_italic_characters_look_as_if_clipped_3f">Why do italic characters look as if clipped?</a></strong><br /> 728<h2><a name="why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></h2>
912</dt>
913<dd>
914Many fonts have difficulties with italic characters and hinting. For 729<p>Many fonts have difficulties with italic characters and hinting. For
915example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans 730example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans
916Mono</code> completely fails in it's italic face. A workaround might be to 731Mono</code> completely fails in it's italic face. A workaround might be to
917enable freetype autohinting, i.e. like this: 732enable freetype autohinting, i.e. like this:</p>
918</dd>
919<dd>
920<pre> 733<pre>
921 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 734 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
922 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> 735 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
923</dd> 736<p>
924<p></p> 737</p>
925<dt><strong><a name="item_my_input_method_wants__3csome_encoding_3e_but_i_wa">My input method wants &lt;some encoding&gt; but I want UTF-8, what can I do?</a></strong><br /> 738<h2><a name="my_input_method_wants__some_encoding__but_i_want_utf8__what_can_i_do">My input method wants &lt;some encoding&gt; but I want UTF-8, what can I do?</a></h2>
926</dt>
927<dd>
928You can specify separate locales for the input method and the rest of the 739<p>You can specify separate locales for the input method and the rest of the
929terminal, using the resource <code>imlocale</code>: 740terminal, using the resource <code>imlocale</code>:</p>
930</dd>
931<dd>
932<pre> 741<pre>
933 URxvt.imlocale: ja_JP.EUC-JP</pre> 742 URxvt.imlocale: ja_JP.EUC-JP</pre>
934</dd>
935<dd>
936<p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still 743<p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still
937use your input method. Please note, however, that you will not be able to 744use your input method. Please note, however, that you will not be able to
938input characters outside <code>EUC-JP</code> in a normal way then, as your input 745input characters outside <code>EUC-JP</code> in a normal way then, as your input
939method limits you.</p> 746method limits you.</p>
940</dd> 747<p>
941<p></p> 748</p>
942<dt><strong><a name="item_rxvt_2dunicode_crashes_when_the_x_input_method_cha">Rxvt-unicode crashes when the X Input Method changes or exits.</a></strong><br /> 749<h2><a name="rxvtunicode_crashes_when_the_x_input_method_changes_or_exits_">Rxvt-unicode crashes when the X Input Method changes or exits.</a></h2>
943</dt>
944<dd>
945Unfortunately, this is unavoidable, as the XIM protocol is racy by 750<p>Unfortunately, this is unavoidable, as the XIM protocol is racy by
946design. Applications can avoid some crashes at the expense of memory 751design. Applications can avoid some crashes at the expense of memory
947leaks, and Input Methods can avoid some crashes by careful ordering at 752leaks, and Input Methods can avoid some crashes by careful ordering at
948exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds, 753exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds,
949while <strong>SCIM</strong> (or similar input methods) fails. In the end, however, 754while <strong>SCIM</strong> (or similar input methods) fails. In the end, however,
950crashes cannot be completely avoided even if both sides cooperate. 755crashes cannot be completely avoided even if both sides cooperate.</p>
951</dd>
952<dd>
953<p>So the only workaround is not to kill your Input Method Servers.</p> 756<p>So the only workaround is not to kill your Input Method Servers.</p>
954</dd> 757<p>
955<p></p> 758</p>
956<dt><strong><a name="item_rxvt_2dunicode_uses_gobs_of_memory_2c_how_can_i_re">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></strong><br /> 759<h2><a name="rxvtunicode_uses_gobs_of_memory__how_can_i_reduce_that">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></h2>
957</dt>
958<dd>
959Rxvt-unicode tries to obey the rule of not charging you for something you 760<p>Rxvt-unicode tries to obey the rule of not charging you for something you
960don't use. One thing you should try is to configure out all settings that 761don't use. One thing you should try is to configure out all settings that
961you don't need, for example, Xft support is a resource hog by design, 762you don't need, for example, Xft support is a resource hog by design,
962when used. Compiling it out ensures that no Xft font will be loaded 763when used. Compiling it out ensures that no Xft font will be loaded
963accidentally when rxvt-unicode tries to find a font for your characters. 764accidentally when rxvt-unicode tries to find a font for your characters.</p>
964</dd>
965<dd>
966<p>Also, many people (me included) like large windows and even larger 765<p>Also, many people (me included) like large windows and even larger
967scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use 766scrollback buffers: Without <code>--enable-unicode3</code>, rxvt-unicode will use
9686 bytes per screen cell. For a 160x?? window this amounts to almost a 7676 bytes per screen cell. For a 160x?? window this amounts to almost a
969kilobyte per line. A scrollback buffer of 10000 lines will then (if full) 768kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
970use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as 769use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as
971rxvt-unicode then uses 8 bytes per screen cell.</p> 770rxvt-unicode then uses 8 bytes per screen cell.</p>
972</dd> 771<p>
973<p></p> 772</p>
974<dt><strong><a name="item_can_i_speed_up_xft_rendering_somehow_3f">Can I speed up Xft rendering somehow?</a></strong><br /> 773<h2><a name="can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></h2>
975</dt>
976<dd>
977Yes, the most obvious way to speed it up is to avoid Xft entirely, as 774<p>Yes, the most obvious way to speed it up is to avoid Xft entirely, as
978it is simply slow. If you still want Xft fonts you might try to disable 775it is simply slow. If you still want Xft fonts you might try to disable
979antialiasing (by appending <code>:antialias=false</code>), which saves lots of 776antialiasing (by appending <code>:antialias=false</code>), which saves lots of
980memory and also speeds up rendering considerably. 777memory and also speeds up rendering considerably.</p>
981</dd> 778<p>
982<p></p> 779</p>
983<dt><strong><a name="item_rxvt_2dunicode_doesn_27t_seem_to_anti_2dalias_its_">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></strong><br /> 780<h2><a name="rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></h2>
984</dt>
985<dd>
986Rxvt-unicode will use whatever you specify as a font. If it needs to 781<p>Rxvt-unicode will use whatever you specify as a font. If it needs to
987fall back to it's default font search list it will prefer X11 core 782fall back to it's default font search list it will prefer X11 core
988fonts, because they are small and fast, and then use Xft fonts. It has 783fonts, because they are small and fast, and then use Xft fonts. It has
989antialiasing disabled for most of them, because the author thinks they 784antialiasing disabled for most of them, because the author thinks they
990look best that way. 785look best that way.</p>
991</dd>
992<dd>
993<p>If you want antialiasing, you have to specify the fonts manually.</p> 786<p>If you want antialiasing, you have to specify the fonts manually.</p>
994</dd> 787<p>
995<p></p> 788</p>
996<dt><strong><a name="item_mouse_cut_2fpaste_suddenly_no_longer_works_2e">Mouse cut/paste suddenly no longer works.</a></strong><br /> 789<h2><a name="mouse_cut_paste_suddenly_no_longer_works_">Mouse cut/paste suddenly no longer works.</a></h2>
997</dt>
998<dd>
999Make sure that mouse reporting is actually turned off since killing 790<p>Make sure that mouse reporting is actually turned off since killing
1000some editors prematurely may leave the mouse in mouse report mode. I've 791some editors prematurely may leave the mouse in mouse report mode. I've
1001heard that tcsh may use mouse reporting unless it otherwise specified. A 792heard that tcsh may use mouse reporting unless it otherwise specified. A
1002quick check is to see if cut/paste works when the Alt or Shift keys are 793quick check is to see if cut/paste works when the Alt or Shift keys are
1003depressed. 794depressed.</p>
1004</dd> 795<p>
1005<p></p> 796</p>
1006<dt><strong><a name="item_what_27s_with_this_bold_2fblink_stuff_3f">What's with this bold/blink stuff?</a></strong><br /> 797<h2><a name="what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></h2>
1007</dt>
1008<dd>
1009If no bold colour is set via <code>colorBD:</code>, bold will invert text using the 798<p>If no bold colour is set via <code>colorBD:</code>, bold will invert text using the
1010standard foreground colour. 799standard foreground colour.</p>
1011</dd>
1012<dd>
1013<p>For the standard background colour, blinking will actually make the 800<p>For the standard background colour, blinking will actually make the
1014text blink when compiled with <code>--enable-blinking</code>. with standard 801text blink when compiled with <code>--enable-blinking</code>. with standard
1015colours. Without <code>--enable-blinking</code>, the blink attribute will be 802colours. Without <code>--enable-blinking</code>, the blink attribute will be
1016ignored.</p> 803ignored.</p>
1017</dd>
1018<dd>
1019<p>On ANSI colours, bold/blink attributes are used to set high-intensity 804<p>On ANSI colours, bold/blink attributes are used to set high-intensity
1020foreground/background colors.</p> 805foreground/background colors.</p>
1021</dd>
1022<dd>
1023<p>color0-7 are the low-intensity colors.</p> 806<p>color0-7 are the low-intensity colors.</p>
1024</dd>
1025<dd>
1026<p>color8-15 are the corresponding high-intensity colors.</p> 807<p>color8-15 are the corresponding high-intensity colors.</p>
1027</dd> 808<p>
1028<p></p> 809</p>
1029<dt><strong><a name="item_i_don_27t_like_the_screen_colors_2e_how_do_i_chang">I don't like the screen colors. How do I change them?</a></strong><br /> 810<h2><a name="i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors. How do I change them?</a></h2>
1030</dt>
1031<dd>
1032You can change the screen colors at run-time using <em>~/.Xdefaults</em> 811<p>You can change the screen colors at run-time using <em>~/.Xdefaults</em>
1033resources (or as long-options). 812resources (or as long-options).</p>
1034</dd>
1035<dd>
1036<p>Here are values that are supposed to resemble a VGA screen, 813<p>Here are values that are supposed to resemble a VGA screen,
1037including the murky brown that passes for low-intensity yellow:</p> 814including the murky brown that passes for low-intensity yellow:</p>
1038</dd>
1039<dd>
1040<pre> 815<pre>
1041 URxvt.color0: #000000 816 URxvt.color0: #000000
1042 URxvt.color1: #A80000 817 URxvt.color1: #A80000
1043 URxvt.color2: #00A800 818 URxvt.color2: #00A800
1044 URxvt.color3: #A8A800 819 URxvt.color3: #A8A800
1045 URxvt.color4: #0000A8 820 URxvt.color4: #0000A8
1046 URxvt.color5: #A800A8 821 URxvt.color5: #A800A8
1047 URxvt.color6: #00A8A8 822 URxvt.color6: #00A8A8
1048 URxvt.color7: #A8A8A8</pre> 823 URxvt.color7: #A8A8A8</pre>
1049</dd>
1050<dd>
1051<pre> 824<pre>
1052 URxvt.color8: #000054 825 URxvt.color8: #000054
1053 URxvt.color9: #FF0054 826 URxvt.color9: #FF0054
1054 URxvt.color10: #00FF54 827 URxvt.color10: #00FF54
1055 URxvt.color11: #FFFF54 828 URxvt.color11: #FFFF54
1056 URxvt.color12: #0000FF 829 URxvt.color12: #0000FF
1057 URxvt.color13: #FF00FF 830 URxvt.color13: #FF00FF
1058 URxvt.color14: #00FFFF 831 URxvt.color14: #00FFFF
1059 URxvt.color15: #FFFFFF</pre> 832 URxvt.color15: #FFFFFF</pre>
1060</dd>
1061<dd>
1062<p>And here is a more complete set of non-standard colors described (not by 833<p>And here is a more complete set of non-standard colors described (not by
1063me) as ``pretty girly''.</p> 834me) as ``pretty girly''.</p>
1064</dd>
1065<dd>
1066<pre> 835<pre>
1067 URxvt.cursorColor: #dc74d1 836 URxvt.cursorColor: #dc74d1
1068 URxvt.pointerColor: #dc74d1 837 URxvt.pointerColor: #dc74d1
1069 URxvt.background: #0e0e0e 838 URxvt.background: #0e0e0e
1070 URxvt.foreground: #4ad5e1 839 URxvt.foreground: #4ad5e1
… …
1080 URxvt.color13: #9e88f0 849 URxvt.color13: #9e88f0
1081 URxvt.color6: #73f7ff 850 URxvt.color6: #73f7ff
1082 URxvt.color14: #73f7ff 851 URxvt.color14: #73f7ff
1083 URxvt.color7: #e1dddd 852 URxvt.color7: #e1dddd
1084 URxvt.color15: #e1dddd</pre> 853 URxvt.color15: #e1dddd</pre>
1085</dd> 854<p>
1086<p></p> 855</p>
1087<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 /> 856<h2><a name="how_can_i_start_rxvtd_in_a_racefree_way">How can I start rxvtd in a race-free way?</a></h2>
1088</dt>
1089<dd>
1090Try <code>rxvtd -f -o</code>, which tells rxvtd to open the 857<p>Try <code>rxvtd -f -o</code>, which tells rxvtd to open the
1091display, create the listening socket and then fork. 858display, create the listening socket and then fork.</p>
1092</dd> 859<p>
1093<p></p> 860</p>
1094<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 /> 861<h2><a name="what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></h2>
1095</dt>
1096<dd>
1097Assuming that the physical Backspace key corresponds to the 862<p>Assuming that the physical Backspace key corresponds to the
1098BackSpace keysym (not likely for Linux ... see the following 863BackSpace keysym (not likely for Linux ... see the following
1099question) there are two standard values that can be used for 864question) there are two standard values that can be used for
1100Backspace: <code>^H</code> and <code>^?</code>. 865Backspace: <code>^H</code> and <code>^?</code>.</p>
1101</dd>
1102<dd>
1103<p>Historically, either value is correct, but rxvt-unicode adopts the debian 866<p>Historically, either value is correct, but rxvt-unicode adopts the debian
1104policy of using <code>^?</code> when unsure, because it's the one only only correct 867policy of using <code>^?</code> when unsure, because it's the one only only correct
1105choice :).</p> 868choice :).</p>
1106</dd>
1107<dd>
1108<p>Rxvt-unicode tries to inherit the current stty settings and uses the value 869<p>Rxvt-unicode tries to inherit the current stty settings and uses the value
1109of `erase' to guess the value for backspace. If rxvt-unicode wasn't 870of `erase' to guess the value for backspace. If rxvt-unicode wasn't
1110started from a terminal (say, from a menu or by remote shell), then the 871started from a terminal (say, from a menu or by remote shell), then the
1111system value of `erase', which corresponds to CERASE in &lt;termios.h&gt;, will 872system value of `erase', which corresponds to CERASE in &lt;termios.h&gt;, will
1112be used (which may not be the same as your stty setting).</p> 873be used (which may not be the same as your stty setting).</p>
1113</dd>
1114<dd>
1115<p>For starting a new rxvt-unicode:</p> 874<p>For starting a new rxvt-unicode:</p>
1116</dd>
1117<dd>
1118<pre> 875<pre>
1119 # use Backspace = ^H 876 # use Backspace = ^H
1120 $ stty erase ^H 877 $ stty erase ^H
1121 $ rxvt</pre> 878 $ rxvt</pre>
1122</dd>
1123<dd>
1124<pre> 879<pre>
1125 # use Backspace = ^? 880 # use Backspace = ^?
1126 $ stty erase ^? 881 $ stty erase ^?
1127 $ rxvt</pre> 882 $ rxvt</pre>
1128</dd>
1129<dd>
1130<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p> 883<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p>
1131</dd>
1132<dd>
1133<p>For an existing rxvt-unicode:</p> 884<p>For an existing rxvt-unicode:</p>
1134</dd>
1135<dd>
1136<pre> 885<pre>
1137 # use Backspace = ^H 886 # use Backspace = ^H
1138 $ stty erase ^H 887 $ stty erase ^H
1139 $ echo -n &quot;^[[36h&quot;</pre> 888 $ echo -n &quot;^[[36h&quot;</pre>
1140</dd>
1141<dd>
1142<pre> 889<pre>
1143 # use Backspace = ^? 890 # use Backspace = ^?
1144 $ stty erase ^? 891 $ stty erase ^?
1145 $ echo -n &quot;^[[36l&quot;</pre> 892 $ echo -n &quot;^[[36l&quot;</pre>
1146</dd>
1147<dd>
1148<p>This helps satisfy some of the Backspace discrepancies that occur, but 893<p>This helps satisfy some of the Backspace discrepancies that occur, but
1149if you use Backspace = <code>^H</code>, make sure that the termcap/terminfo value 894if you use Backspace = <code>^H</code>, make sure that the termcap/terminfo value
1150properly reflects that.</p> 895properly reflects that.</p>
1151</dd>
1152<dd>
1153<p>The Delete key is a another casualty of the ill-defined Backspace problem. 896<p>The Delete key is a another casualty of the ill-defined Backspace problem.
1154To avoid confusion between the Backspace and Delete keys, the Delete 897To avoid confusion between the Backspace and Delete keys, the Delete
1155key has been assigned an escape sequence to match the vt100 for Execute 898key has been assigned an escape sequence to match the vt100 for Execute
1156(<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p> 899(<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p>
1157</dd>
1158<dd>
1159<p>Some other Backspace problems:</p> 900<p>Some other Backspace problems:</p>
1160</dd>
1161<dd>
1162<p>some editors use termcap/terminfo, 901<p>some editors use termcap/terminfo,
1163some editors (vim I'm told) expect Backspace = ^H, 902some editors (vim I'm told) expect Backspace = ^H,
1164GNU Emacs (and Emacs-like editors) use ^H for help.</p> 903GNU Emacs (and Emacs-like editors) use ^H for help.</p>
1165</dd>
1166<dd>
1167<p>Perhaps someday this will all be resolved in a consistent manner.</p> 904<p>Perhaps someday this will all be resolved in a consistent manner.</p>
1168</dd> 905<p>
1169<p></p> 906</p>
1170<dt><strong><a name="item_i_don_27t_like_the_key_2dbindings_2e_how_do_i_chan">I don't like the key-bindings. How do I change them?</a></strong><br /> 907<h2><a name="i_don_t_like_the_keybindings__how_do_i_change_them">I don't like the key-bindings. How do I change them?</a></h2>
1171</dt>
1172<dd>
1173There are some compile-time selections available via configure. Unless 908<p>There are some compile-time selections available via configure. Unless
1174you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can 909you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can
1175use the `keysym' resource to alter the keystrings associated with keysyms. 910use the `keysym' resource to alter the keystrings associated with keysyms.</p>
1176</dd>
1177<dd>
1178<p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p> 911<p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p>
1179</dd>
1180<dd>
1181<pre> 912<pre>
1182 URxvt.keysym.Home: \033[1~ 913 URxvt.keysym.Home: \033[1~
1183 URxvt.keysym.End: \033[4~ 914 URxvt.keysym.End: \033[4~
1184 URxvt.keysym.C-apostrophe: \033&lt;C-'&gt; 915 URxvt.keysym.C-apostrophe: \033&lt;C-'&gt;
1185 URxvt.keysym.C-slash: \033&lt;C-/&gt; 916 URxvt.keysym.C-slash: \033&lt;C-/&gt;
… …
1197 URxvt.keysym.M-Left: \033&lt;M-Left&gt; 928 URxvt.keysym.M-Left: \033&lt;M-Left&gt;
1198 URxvt.keysym.M-Right: \033&lt;M-Right&gt; 929 URxvt.keysym.M-Right: \033&lt;M-Right&gt;
1199 URxvt.keysym.M-C-0: list \033&lt;M-C- 0123456789 &gt; 930 URxvt.keysym.M-C-0: list \033&lt;M-C- 0123456789 &gt;
1200 URxvt.keysym.M-C-a: list \033&lt;M-C- abcdefghijklmnopqrstuvwxyz &gt; 931 URxvt.keysym.M-C-a: list \033&lt;M-C- abcdefghijklmnopqrstuvwxyz &gt;
1201 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre> 932 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre>
1202</dd>
1203<dd>
1204<p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p> 933<p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p>
1205</dd> 934<p>
1206<p></p> 935</p>
1207<dt><strong><a name="item_i_27m_using_keyboard_model_xxx_that_has_extra_prio">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. 936<h2><a name="i_m_using_keyboard_model_xxx_that_has_extra_prior_next_insert_keys__how_do_i_make_use_of_them_for_example__the_sun_keyboard_type_4_has_the_following_mappings_that_rxvtunicode_doesn_t_recognize_">I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize.</a></h2>
1208How do I make use of them? For example, the Sun Keyboard type 4
1209has the following mappings that rxvt-unicode doesn't recognize.</a></strong><br />
1210</dt>
1211<dd>
1212<pre> 937<pre>
1213 KP_Insert == Insert 938 KP_Insert == Insert
1214 F22 == Print 939 F22 == Print
1215 F27 == Home 940 F27 == Home
1216 F29 == Prior 941 F29 == Prior
1217 F33 == End 942 F33 == End
1218 F35 == Next</pre> 943 F35 == Next</pre>
1219</dd>
1220<dd>
1221<p>Rather than have rxvt-unicode try to accommodate all the various possible 944<p>Rather than have rxvt-unicode try to accommodate all the various possible
1222keyboard mappings, it is better to use `xmodmap' to remap the keys as 945keyboard mappings, it is better to use `xmodmap' to remap the keys as
1223required for your particular machine.</p> 946required for your particular machine.</p>
1224</dd> 947<p>
1225<dt><strong><a name="item_how_do_i_distinguish_wether_i_27m_running_rxvt_2du">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? 948</p>
1226I need this to decide about setting colors etc.</a></strong><br /> 949<h2><a name="how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></h2>
1227</dt>
1228<dd>
1229rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can 950<p>rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can
1230check and see if that is set. Note that several programs, JED, slrn, 951check and see if that is set. Note that several programs, JED, slrn,
1231Midnight Commander automatically check this variable to decide whether or 952Midnight Commander automatically check this variable to decide whether or
1232not to use color. 953not to use color.</p>
1233</dd> 954<p>
1234<p></p> 955</p>
1235<dt><strong><a name="item_how_do_i_set_the_correct_2c_full_ip_address_for_th">How do I set the correct, full IP address for the DISPLAY variable?</a></strong><br /> 956<h2><a name="how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></h2>
1236</dt>
1237<dd>
1238If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled 957<p>If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
1239insecure mode then it is possible to use the following shell script 958insecure mode then it is possible to use the following shell script
1240snippets to correctly set the display. If your version of rxvt-unicode 959snippets to correctly set the display. If your version of rxvt-unicode
1241wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then 960wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
1242the COLORTERM variable can be used to distinguish rxvt-unicode from a 961the COLORTERM variable can be used to distinguish rxvt-unicode from a
1243regular xterm. 962regular xterm.</p>
1244</dd>
1245<dd>
1246<p>Courtesy of Chuck Blake &lt;<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>&gt; with the following shell script 963<p>Courtesy of Chuck Blake &lt;<a href="mailto:cblake@BBN.COM">cblake@BBN.COM</a>&gt; with the following shell script
1247snippets:</p> 964snippets:</p>
1248</dd>
1249<dd>
1250<pre> 965<pre>
1251 # Bourne/Korn/POSIX family of shells: 966 # Bourne/Korn/POSIX family of shells:
1252 [ ${TERM:-foo} = foo ] &amp;&amp; TERM=xterm # assume an xterm if we don't know 967 [ ${TERM:-foo} = foo ] &amp;&amp; TERM=xterm # assume an xterm if we don't know
1253 if [ ${TERM:-foo} = xterm ]; then 968 if [ ${TERM:-foo} = xterm ]; then
1254 stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not 969 stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
… …
1258 if [ &quot;&quot;${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then 973 if [ &quot;&quot;${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
1259 echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string 974 echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
1260 read DISPLAY # set it in our local shell 975 read DISPLAY # set it in our local shell
1261 fi 976 fi
1262 fi</pre> 977 fi</pre>
1263</dd> 978<p>
1264<p></p> 979</p>
1265<dt><strong><a name="item_how_do_i_compile_the_manual_pages_for_myself_3f">How do I compile the manual pages for myself?</a></strong><br /> 980<h2><a name="how_do_i_compile_the_manual_pages_for_myself">How do I compile the manual pages for myself?</a></h2>
1266</dt>
1267<dd>
1268You need to have a recent version of perl installed as <em>/usr/bin/perl</em>, 981<p>You need to have a recent version of perl installed as <em>/usr/bin/perl</em>,
1269one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to 982one that comes with <em>pod2man</em>, <em>pod2text</em> and <em>pod2html</em>. Then go to
1270the doc subdirectory and enter <code>make alldoc</code>. 983the doc subdirectory and enter <code>make alldoc</code>.</p>
1271</dd> 984<p>
1272<p></p> 985</p>
1273<dt><strong><a name="item_my_question_isn_27t_answered_here_2c_can_i_ask_a_h">My question isn't answered here, can I ask a human?</a></strong><br /> 986<h2><a name="my_question_isn_t_answered_here__can_i_ask_a_human">My question isn't answered here, can I ask a human?</a></h2>
1274</dt>
1275<dd>
1276Before sending me mail, you could go to IRC: <code>irc.freenode.net</code>, 987<p>Before sending me mail, you could go to IRC: <code>irc.freenode.net</code>,
1277channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be 988channel <code>#rxvt-unicode</code> has some rxvt-unicode enthusiasts that might be
1278interested in learning about new and exciting problems (but not FAQs :). 989interested in learning about new and exciting problems (but not FAQs :).</p>
1279</dd>
1280<p></p></dl>
1281<p> 990<p>
1282</p> 991</p>
1283<hr /> 992<hr />
1284<h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1> 993<h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1>
1285<p> 994<p>

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines