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.4 by root, Thu Feb 3 10:24:10 2005 UTC vs.
Revision 1.22 by root, Wed Jul 13 03:08:57 2005 UTC

… …
11<!-- INDEX BEGIN --> 11<!-- INDEX BEGIN -->
12 12
13<ul> 13<ul>
14 14
15 <li><a href="#name">NAME</a></li> 15 <li><a href="#name">NAME</a></li>
16 <li><a href="#frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></li>
17 <li><a href="#synopsis">SYNOPSIS</a></li> 16 <li><a href="#synopsis">SYNOPSIS</a></li>
18 <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>
19 <li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li> 19 <li><a href="#rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></li>
20 <li><a href="#description">DESCRIPTION</a></li>
20 <li><a href="#definitions">Definitions</a></li> 21 <li><a href="#definitions">Definitions</a></li>
21 <li><a href="#values">Values</a></li> 22 <li><a href="#values">Values</a></li>
22 <li><a href="#escape_sequences">Escape Sequences</a></li> 23 <li><a href="#escape_sequences">Escape Sequences</a></li>
23 <li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li> 24 <li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li>
24 <li><a href="#dec_private_modes">DEC Private Modes</a></li> 25 <li><a href="#dec_private_modes">DEC Private Modes</a></li>
… …
48<h1><a name="name">NAME</a></h1> 49<h1><a name="name">NAME</a></h1>
49<p>RXVT REFERENCE - FAQ, command sequences and other background information</p> 50<p>RXVT REFERENCE - FAQ, command sequences and other background information</p>
50<p> 51<p>
51</p> 52</p>
52<hr /> 53<hr />
54<h1><a name="synopsis">SYNOPSIS</a></h1>
55<pre>
56 # set a new font set
57 printf '\33]50;%s\007' 9x15,xft:Kochi&quot; Mincho&quot;</pre>
58<pre>
59 # change the locale and tell rxvt-unicode about it
60 export LC_CTYPE=ja_JP.EUC-JP; printf &quot;\33]701;$LC_CTYPE\007&quot;</pre>
61<pre>
62 # set window title
63 printf '\33]2;%s\007' &quot;new window title&quot;</pre>
64<p>
65</p>
66<hr />
67<h1><a name="description">DESCRIPTION</a></h1>
68<p>This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
69all escape sequences, and other background information.</p>
70<p>The newest version of this document is
71also available on the World Wide Web at
72<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>
73<p>
74</p>
75<hr />
53<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1> 76<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>
54<dl> 77<dl>
55<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 /> 78<dt><strong><a name="item_how_do_i_know_which_rxvt_2dunicode_version_i_27m_u">How do I know which rxvt-unicode version I'm using?</a></strong><br />
56</dt> 79</dt>
57<dd> 80<dd>
58The version number is displayed with the usage (-h). Also the escape 81The version number is displayed with the usage (-h). Also the escape
59sequence <code>ESC[8n</code> sets the window title to the version number. 82sequence <code>ESC [ 8 n</code> sets the window title to the version number.
83</dd>
84<p></p>
85<dt><strong><a name="item_i_am_using_debian_gnu_2flinux_and_have_a_problem_2">I am using Debian GNU/Linux and have a problem...</a></strong><br />
86</dt>
87<dd>
88The Debian GNU/Linux package of rxvt-unicode in sarge contains large
89patches that considerably change the behaviour of rxvt-unicode. Before
90reporting a bug to the original rxvt-unicode author please download and
91install the genuine version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>)
92and try to reproduce the problem. If you cannot, chances are that the
93problems are specific to Debian GNU/Linux, in which case it should be
94reported via the Debian Bug Tracking System (use <code>reportbug</code> to report
95the bug).
96</dd>
97<dd>
98<p>For other problems that also affect the Debian package, you can and
99probably should use the Debian BTS, too, because, after all, it's also a
100bug in the Debian version and it serves as a reminder for other users that
101might encounter the same issue.</p>
60</dd> 102</dd>
61<p></p> 103<p></p>
62<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 /> 104<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 />
63</dt> 105</dt>
64<dd> 106<dd>
… …
83problems arising, which includes wrong keymapping, less and different 125problems arising, which includes wrong keymapping, less and different
84colours and some refresh errors in fullscreen applications. It's a nice 126colours and some refresh errors in fullscreen applications. It's a nice
85quick-and-dirty workaround for rare cases, though.</p> 127quick-and-dirty workaround for rare cases, though.</p>
86</dd> 128</dd>
87<dd> 129<dd>
88<p>If you always want to do this you can either recompile rxvt-unicode with 130<p>If you always want to do this (and are fine with the consequences) you
89the desired TERM value or use a resource to set it:</p> 131can either recompile rxvt-unicode with the desired TERM value or use a
132resource to set it:</p>
90</dd> 133</dd>
91<dd> 134<dd>
92<pre> 135<pre>
93 URxvt.termName: rxvt</pre> 136 URxvt.termName: rxvt</pre>
94</dd> 137</dd>
95<dd> 138<dd>
96<p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace 139<p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace
97the rxvt terminfo file with the rxvt-unicode one.</p> 140the rxvt terminfo file with the rxvt-unicode one.</p>
98</dd> 141</dd>
99<p></p> 142<p></p>
143<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 />
144</dt>
145<dd>
146Most likely it's the empty definition for <code>enacs=</code>. Just replace it by
147<code>enacs=\E[0@</code> and try again.
148</dd>
149<p></p>
150<dt><strong><a name="item_bash_27s_readline_does_not_work_correctly_under_rx"><code>bash</code>'s readline does not work correctly under rxvt.</a></strong><br />
151</dt>
100<dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br /> 152<dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br />
101</dt> 153</dt>
102<dd> 154<dd>
155One reason you might want this is that some distributions or operating
156systems still compile some programs using the long-obsoleted termcap
157library (Fedora Core's bash is one example) and rely on a termcap entry
158for <code>rxvt-unicode</code>.
159</dd>
160<dd>
103You could use rxvt's termcap entry with resonable results in many cases. 161<p>You could use rxvt's termcap entry with resonable results in many cases.
104You can also create a termcap entry by using terminfo's infocmp program 162You can also create a termcap entry by using terminfo's infocmp program
105like this: 163like this:</p>
106</dd> 164</dd>
107<dd> 165<dd>
108<pre> 166<pre>
109 infocmp -C rxvt-unicode</pre> 167 infocmp -C rxvt-unicode</pre>
110</dd> 168</dd>
111<dd> 169<dd>
112<p>OR you could this termcap entry:</p> 170<p>Or you could use this termcap entry, generated by the command above:</p>
113</dd> 171</dd>
114<dd> 172<dd>
115<pre> 173<pre>
116 rxvt-unicode|rxvt-unicode terminal (X Window System):\ 174 rxvt-unicode|rxvt-unicode terminal (X Window System):\
117 :am:bw:eo:km:mi:ms:xn:xo:\ 175 :am:bw:eo:km:mi:ms:xn:xo:\
118 :co#80:it#8:li#24:\ 176 :co#80:it#8:li#24:lm#0:\
119 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ 177 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
120 :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ 178 :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
121 :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\ 179 :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
122 :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\ 180 :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
123 :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\ 181 :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
124 :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\ 182 :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
183 :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
125 :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ 184 :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
126 :k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\ 185 :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
127 :k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\ 186 :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
128 :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\ 187 :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E&gt;:\
129 :ke=\E[?1l\E&gt;:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\ 188 :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
130 :ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\ 189 :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
131 :nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\ 190 :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
132 :st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\ 191 :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
133 :up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ 192 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
134 :vs=\E[?25h:</pre> 193 :vs=\E[?25h:</pre>
135</dd> 194</dd>
136<p></p> 195<p></p>
137<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 /> 196<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 />
138</dt> 197</dt>
… …
172file, so you will need to install it on your own (See the question <strong>When 231file, so you will need to install it on your own (See the question <strong>When
173I log-in to another system it tells me about missing terminfo data?</strong> on 232I log-in to another system it tells me about missing terminfo data?</strong> on
174how to do this). 233how to do this).
175</dd> 234</dd>
176<p></p> 235<p></p>
236<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 />
237</dt>
238<dd>
239Some Debian GNUL/Linux users seem to have this problem, although no
240specific details were reported so far. It is possible that this is caused
241by the wrong <code>TERM</code> setting, although the details of wether and how
242this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible
243keymap. See the answer to the previous question, and please report if that
244helped.
245</dd>
246<p></p>
177<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 /> 247<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 />
178</dt> 248</dt>
179<dt><strong><a name="item_unicode_does_not_seem_to_work_3f">Unicode does not seem to work?</a></strong><br /> 249<dt><strong><a name="item_unicode_does_not_seem_to_work_3f">Unicode does not seem to work?</a></strong><br />
180</dt> 250</dt>
181<dd> 251<dd>
… …
185</dd> 255</dd>
186<dd> 256<dd>
187<p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the 257<p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the
188programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the 258programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the
189login script running within the rxvt-unicode window changes the locale to 259login script running within the rxvt-unicode window changes the locale to
190sth. else, e.h. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p> 260something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p>
191</dd> 261</dd>
192<dd> 262<dd>
193<p>The best thing is to fix your startup environment, as you will likely run 263<p>The best thing is to fix your startup environment, as you will likely run
194into other problems. If nothing works you can try this in your .profile.</p> 264into other problems. If nothing works you can try this in your .profile.</p>
195</dd> 265</dd>
… …
198 printf '\e]701;%s\007' &quot;$LC_CTYPE&quot;</pre> 268 printf '\e]701;%s\007' &quot;$LC_CTYPE&quot;</pre>
199</dd> 269</dd>
200<dd> 270<dd>
201<p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not 271<p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not
202supported on your systems. Some systems have a <code>locale</code> command which 272supported on your systems. Some systems have a <code>locale</code> command which
203displays this. If it displays sth. like:</p> 273displays this (also, <code>perl -e0</code> can be used to check locale settings, as
274it will complain loudly if it cannot set the locale). If it displays something
275like:</p>
204</dd> 276</dd>
205<dd> 277<dd>
206<pre> 278<pre>
207 locale: Cannot set LC_CTYPE to default locale: ...</pre> 279 locale: Cannot set LC_CTYPE to default locale: ...</pre>
208</dd> 280</dd>
… …
226to display. 298to display.
227</dd> 299</dd>
228<dd> 300<dd>
229<p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement 301<p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement
230font. Often the result is fine, but sometimes the chosen font looks 302font. Often the result is fine, but sometimes the chosen font looks
231bad. Many fonts have totally strange characters that don't resemble the 303bad/ugly/wrong. Some fonts have totally strange characters that don't
232correct glyph at all, and rxvt-unicode lacks the artificial intelligence 304resemble the correct glyph at all, and rxvt-unicode lacks the artificial
233to detect that a specific glyph is wrong: it has to believe the font that 305intelligence to detect that a specific glyph is wrong: it has to believe
234the characters it contains indeed look correct.</p> 306the font that the characters it claims to contain indeed look correct.</p>
235</dd> 307</dd>
236<dd> 308<dd>
237<p>In that case, select a font of your taste and add it to the font list, 309<p>In that case, select a font of your taste and add it to the font list,
238e.g.:</p> 310e.g.:</p>
239</dd> 311</dd>
… …
246font. If the base font does not contain the character, it will go to the 318font. If the base font does not contain the character, it will go to the
247next font, and so on. Specifying your own fonts will also speed up this 319next font, and so on. Specifying your own fonts will also speed up this
248search and use less resources within rxvt-unicode and the X-server.</p> 320search and use less resources within rxvt-unicode and the X-server.</p>
249</dd> 321</dd>
250<dd> 322<dd>
251<p>The only limitation is that all the fonts must not be larger than the base 323<p>The only limitation is that none of the fonts may be larger than the base
252font, as the base font defines the principal cell size, which must be the 324font, as the base font defines the terminal character cell size, which
253same due to the way terminals work.</p> 325must be the same due to the way terminals work.</p>
254</dd> 326</dd>
255<p></p> 327<p></p>
256<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 /> 328<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 />
257</dt> 329</dt>
258<dd> 330<dd>
259This is because there is a difference between script and language -- 331This is because there is a difference between script and language --
260rxvt-unicode does not know which language the text that is output 332rxvt-unicode does not know which language the text that is output is,
261is, as it only knows the unicode character codes. If rxvt-unicode 333as it only knows the unicode character codes. If rxvt-unicode first
262first sees a japanese character, it might choose a japanese font for 334sees a japanese/chinese character, it might choose a japanese font for
263it. Subsequent japanese characters will take that font. Now, many chinese 335display. Subsequent japanese characters will use that font. Now, many
264characters aren't represented in japanese fonts, so when the first 336chinese characters aren't represented in japanese fonts, so when the first
265non-japanese character comes up, rxvt-unicode will look for a chinese font 337non-japanese character comes up, rxvt-unicode will look for a chinese font
266-- unfortunately at this point, it will still use the japanese font for 338-- unfortunately at this point, it will still use the japanese font for
267japanese characters that are also chinese. 339chinese characters that are also in the japanese font.
268</dd> 340</dd>
269<dd> 341<dd>
270<p>The workaround is easy: just tag a chinese font at the end of your font 342<p>The workaround is easy: just tag a chinese font at the end of your font
271list (see the previous question). The key is to view the font list as 343list (see the previous question). The key is to view the font list as
272a preference list: If you expect more japanese, list a japanese font 344a preference list: If you expect more japanese, list a japanese font
273first. If you expect more chinese, put a chinese font first.</p> 345first. If you expect more chinese, put a chinese font first.</p>
274</dd> 346</dd>
275<dd> 347<dd>
276<p>In the future it might be possible to switch preferences at runtime (the 348<p>In the future it might be possible to switch language preferences at
277internal data structure has no problem with using different fonts for 349runtime (the internal data structure has no problem with using different
278the same character at the same time, but no interface for this has been 350fonts for the same character at the same time, but no interface for this
279designed yet).</p> 351has been designed yet).</p>
352</dd>
353<dd>
354<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>
280</dd> 355</dd>
281<p></p> 356<p></p>
282<dt><strong><a name="item_why_does_rxvt_2dunicode_sometimes_leave_pixel_drop">Why does rxvt-unicode sometimes leave pixel droppings?</a></strong><br /> 357<dt><strong><a name="item_why_does_rxvt_2dunicode_sometimes_leave_pixel_drop">Why does rxvt-unicode sometimes leave pixel droppings?</a></strong><br />
283</dt> 358</dt>
284<dd> 359<dd>
… …
302might be forced to use a different font.</p> 377might be forced to use a different font.</p>
303</dd> 378</dd>
304<dd> 379<dd>
305<p>All of this is not a problem when using X11 core fonts, as their bounding 380<p>All of this is not a problem when using X11 core fonts, as their bounding
306box data is correct.</p> 381box data is correct.</p>
382</dd>
383<p></p>
384<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 />
385</dt>
386<dd>
387Seems to be a known bug, read
388<a href="http://nixdoc.net/files/forum/about34198.html">http://nixdoc.net/files/forum/about34198.html</a>. Some people use the
389following ugly workaround to get non-double-wide-characters working:
390</dd>
391<dd>
392<pre>
393 #define wcwidth(x) wcwidth(x) &gt; 1 ? 1 : wcwidth(x)</pre>
307</dd> 394</dd>
308<p></p> 395<p></p>
309<dt><strong><a name="item_compose">My Compose (Multi_key) key is no longer working.</a></strong><br /> 396<dt><strong><a name="item_compose">My Compose (Multi_key) key is no longer working.</a></strong><br />
310</dt> 397</dt>
311<dd> 398<dd>
… …
332</dd> 419</dd>
333<p></p> 420<p></p>
334<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 /> 421<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 />
335</dt> 422</dt>
336<dd> 423<dd>
337First of all, make sure you are running with the right terminfo 424First of all, make sure you are running with the right terminal settings
338(<code>urxvt</code>), which will get rid of most of these effects. Then make sure 425(<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then
339you have specified colours for italic and bold, as otherwise rxvt-unicode 426make sure you have specified colours for italic and bold, as otherwise
340might use reverse video to simulate the effect: 427rxvt-unicode might use reverse video to simulate the effect:
341</dd>
342<dd> 428</dd>
429<dd>
343<pre> 430<pre>
344 URxvt*colorBD: white 431 URxvt.colorBD: white
345 URxvt*colorIT: green</pre> 432 URxvt.colorIT: green</pre>
346</dd> 433</dd>
347<p></p> 434<p></p>
348<dt><strong><a name="item_colours">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></strong><br /> 435<dt><strong><a name="item_colours">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></strong><br />
349</dt> 436</dt>
350<dd> 437<dd>
351For some unexplainable reason, some programs (i.e. irssi) assume a very 438For some unexplainable reason, some rare programs assume a very weird
352weird colour palette when confronted with a terminal with more than the 439colour palette when confronted with a terminal with more than the standard
353standard 8 colours (rxvt-unicode supports 88). The right fix is, of 4408 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
354course, to fix these programs not to assume non-ISO colours without very 441these programs not to assume non-ISO colours without very good reasons.
355good reasons.
356</dd>
357<dd> 442</dd>
443<dd>
358<p>In the meantime, you can either edit your <code>urxvt</code> terminfo definition to 444<p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo
359only claim 8 colour support or use <code>TERM=rxvt</code>, which will fix colours 445definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will
360but keep you from using other rxvt-unicode features.</p> 446fix colours but keep you from using other rxvt-unicode features.</p>
361</dd> 447</dd>
362<p></p> 448<p></p>
363<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 /> 449<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 />
364</dt> 450</dt>
365<dd> 451<dd>
… …
369<strong>wchar_t</strong> is represented as unicode. 455<strong>wchar_t</strong> is represented as unicode.
370</dd> 456</dd>
371<dd> 457<dd>
372<p>As you might have guessed, FreeBSD does neither define this symobl nor 458<p>As you might have guessed, FreeBSD does neither define this symobl nor
373does it support it. Instead, it uses it's own internal representation of 459does it support it. Instead, it uses it's own internal representation of
374<strong>wchar_t</strong>. This is, of course, completely legal.</p> 460<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p>
375</dd>
376<dd> 461</dd>
462<dd>
463<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and
464<code>UTF-8</code> locales under FreeBSD (which all use Unicode as <strong>wchar_t</strong>.</p>
465</dd>
466<dd>
377<p>However, <code>__STDC_ISO_10646__</code> is the only sane way to support 467<p><code>__STDC_ISO_10646__</code> is the only sane way to support multi-language
378multi-language apps in an OS, as using a locale-dependent (and 468apps in an OS, as using a locale-dependent (and non-standardized)
379non-standardized) representation of <strong>wchar_t</strong> makes it impossible to 469representation of <strong>wchar_t</strong> makes it impossible to convert between
380convert between <strong>wchar_t</strong> (as used by X11 and your applications) and any 470<strong>wchar_t</strong> (as used by X11 and your applications) and any other encoding
381other encoding without implementing OS-specific-wrappers for each and 471without implementing OS-specific-wrappers for each and every locale. There
382every locale. There simply are no APIs to convert <strong>wchar_t</strong> into anything 472simply are no APIs to convert <strong>wchar_t</strong> into anything except the current
383except the current locale encoding.</p> 473locale encoding.</p>
384</dd> 474</dd>
385<dd> 475<dd>
386<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this 476<p>Some applications (such as the formidable <strong>mlterm</strong>) work around this
387by carrying their own replacement functions for character set handling 477by carrying their own replacement functions for character set handling
388with them, and either implementing OS-dependent hacks or doing multiple 478with them, and either implementing OS-dependent hacks or doing multiple
… …
390encodings slightly different than the terminal emulator).</p> 480encodings slightly different than the terminal emulator).</p>
391</dd> 481</dd>
392<dd> 482<dd>
393<p>The rxvt-unicode author insists that the right way to fix this is in the 483<p>The rxvt-unicode author insists that the right way to fix this is in the
394system libraries once and for all, instead of forcing every app to carry 484system libraries once and for all, instead of forcing every app to carry
395complete replacements.</p> 485complete replacements for them :)</p>
486</dd>
487<p></p>
488<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 />
489</dt>
490<dd>
491Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst
492problems with <code>wcwidth</code> and a compile problem.
493</dd>
494<p></p>
495<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 />
496</dt>
497<dd>
498rxvt-unicode should compile and run out of the box on cygwin, using
499the X11 libraries that come with cygwin. libW11 emulation is no
500longer supported (and makes no sense, either, as it only supported a
501single font). I recommend starting the X-server in <code>-multiwindow</code> or
502<code>-rootless</code> mode instead, which will result in similar look&amp;feel as the
503old libW11 emulation.
504</dd>
505<dd>
506<p>At the time of this writing, cygwin didn't seem to support any multi-byte
507encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited
508to 8-bit encodings.</p>
396</dd> 509</dd>
397<p></p> 510<p></p>
398<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 /> 511<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 />
399</dt> 512</dt>
400<dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br /> 513<dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br />
… …
405UTF-8 or any other encodings with respect to terminal I/O. 518UTF-8 or any other encodings with respect to terminal I/O.
406</dd> 519</dd>
407<dd> 520<dd>
408<p>The reasons is that there exists a perfectly fine mechanism for selecting 521<p>The reasons is that there exists a perfectly fine mechanism for selecting
409the encoding, doing I/O and (most important) communicating this to all 522the encoding, doing I/O and (most important) communicating this to all
410applications so everybody agrees on character properties such as width and 523applications so everybody agrees on character properties such as width
411code number. This mechanism is the <em>locale</em>.</p> 524and code number. This mechanism is the <em>locale</em>. Applications not using
525that info will have problems (for example, <code>xterm</code> gets the width of
526characters wrong as it uses it's own, locale-independent table under all
527locales).</p>
412</dd> 528</dd>
413<dd> 529<dd>
414<p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All 530<p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All
415programs doing the same (that is, most) will automatically agree in the 531programs doing the same (that is, most) will automatically agree in the
416interpretation of characters.</p> 532interpretation of characters.</p>
… …
427(i.e. <code>de</code> or <code>german</code>) are also common.</p> 543(i.e. <code>de</code> or <code>german</code>) are also common.</p>
428</dd> 544</dd>
429<dd> 545<dd>
430<p>Rxvt-unicode ignores all other locale categories, and except for 546<p>Rxvt-unicode ignores all other locale categories, and except for
431the encoding, ignores country or language-specific settings, 547the encoding, ignores country or language-specific settings,
432i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the same for rxvt-unicode.</p> 548i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to
549rxvt-unicode.</p>
433</dd> 550</dd>
434<dd> 551<dd>
435<p>If you want to use a specific encoding you have to make sure you start 552<p>If you want to use a specific encoding you have to make sure you start
436rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p> 553rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p>
437</dd> 554</dd>
438<p></p> 555<p></p>
439<dt><strong><a name="item_can_i_switch_locales_at_runtime_3f">Can I switch locales at runtime?</a></strong><br /> 556<dt><strong><a name="item_can_i_switch_locales_at_runtime_3f">Can I switch locales at runtime?</a></strong><br />
440</dt> 557</dt>
441<dd> 558<dd>
442Yes, using an escape sequence. Try sth. like this, which sets 559Yes, using an escape sequence. Try something like this, which sets
443rxvt-unicode's idea of <code>LC_CTYPE</code>. 560rxvt-unicode's idea of <code>LC_CTYPE</code>.
444</dd> 561</dd>
445<dd> 562<dd>
446<pre> 563<pre>
447 printf '\e]701;%s\007' ja_JP.SJIS</pre> 564 printf '\e]701;%s\007' ja_JP.SJIS</pre>
448</dd> 565</dd>
449<dd> 566<dd>
450<p>See also the previous question.</p> 567<p>See also the previous answer.</p>
451</dd>
452<dd> 568</dd>
569<dd>
453<p>Sometimes this capability is rather handy when you want to work in one 570<p>Sometimes this capability is rather handy when you want to work in
454locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support UTF-8. For 571one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it
455example, I use this script to start <code>xjdic</code>, which first switches to a 572(e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which
456locale supported by xjdic and back later:</p> 573first switches to a locale supported by xjdic and back later:</p>
457</dd> 574</dd>
458<dd> 575<dd>
459<pre> 576<pre>
460 printf '\e]701;%s\007' ja_JP.SJIS 577 printf '\e]701;%s\007' ja_JP.SJIS
461 xjdic -js 578 xjdic -js
462 printf '\e]701;%s\007' de_DE.UTF-8</pre> 579 printf '\e]701;%s\007' de_DE.UTF-8</pre>
463</dd> 580</dd>
581<dd>
582<p>You can also use xterm's <code>luit</code> program, which usually works fine, except
583for some locales where character width differs between program- and
584rxvt-unicode-locales.</p>
585</dd>
464<p></p> 586<p></p>
465<dt><strong><a name="item_can_i_switch_the_fonts_at_runtime_3f">Can I switch the fonts at runtime?</a></strong><br /> 587<dt><strong><a name="item_can_i_switch_the_fonts_at_runtime_3f">Can I switch the fonts at runtime?</a></strong><br />
466</dt> 588</dt>
467<dd> 589<dd>
468Yes, using an escape sequence. Try sth. like this, which has the same 590Yes, using an escape sequence. Try something like this, which has the same
469effect as using the <code>-fn</code> switch, and takes effect immediately: 591effect as using the <code>-fn</code> switch, and takes effect immediately:
470</dd> 592</dd>
471<dd> 593<dd>
472<pre> 594<pre>
473 printf '\e]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre> 595 printf '\e]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre>
… …
484<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 /> 606<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 />
485</dt> 607</dt>
486<dd> 608<dd>
487Many fonts have difficulties with italic characters and hinting. For 609Many fonts have difficulties with italic characters and hinting. For
488example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans 610example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans
489Mono</code> completely fails in it's italic face. A workaround is to enable 611Mono</code> completely fails in it's italic face. A workaround might be to
490freetype autohinting, i.e. like this: 612enable freetype autohinting, i.e. like this:
491</dd>
492<dd> 613</dd>
614<dd>
493<pre> 615<pre>
494 URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 616 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
495 URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> 617 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
496</dd> 618</dd>
497<p></p> 619<p></p>
498<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 /> 620<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 />
499</dt> 621</dt>
500<dd> 622<dd>
… …
510use your input method. Please note, however, that you will not be able to 632use your input method. Please note, however, that you will not be able to
511input characters outside <code>EUC-JP</code> in a normal way then, as your input 633input characters outside <code>EUC-JP</code> in a normal way then, as your input
512method limits you.</p> 634method limits you.</p>
513</dd> 635</dd>
514<p></p> 636<p></p>
637<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 />
638</dt>
639<dd>
640Unfortunately, this is unavoidable, as the XIM protocol is racy by
641design. Applications can avoid some crashes at the expense of memory
642leaks, and Input Methods can avoid some crashes by careful ordering at
643exit time. <strong>kinput2</strong> (and derived input methods) generally succeeds,
644while <strong>SCIM</strong> (or similar input methods) fails. In the end, however,
645crashes cannot be completely avoided even if both sides cooperate.
646</dd>
647<dd>
648<p>So the only workaround is not to kill your Input Method Servers.</p>
649</dd>
650<p></p>
515<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 /> 651<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 />
516</dt> 652</dt>
517<dd> 653<dd>
518Rxvt-unicode tries to obey the rule of not charging you for sth. you 654Rxvt-unicode tries to obey the rule of not charging you for something you
519don't use. One thing you should try is to configure out all settings that 655don't use. One thing you should try is to configure out all settings that
520you don't need, for example, Xft support is a resource hog by design, 656you don't need, for example, Xft support is a resource hog by design,
521when used. Compiling it out ensures that no Xft font will be loaded 657when used. Compiling it out ensures that no Xft font will be loaded
522accidentally when rxvt-unicode tries to find a font for your characters. 658accidentally when rxvt-unicode tries to find a font for your characters.
523</dd> 659</dd>
… …
595<p>Here are values that are supposed to resemble a VGA screen, 731<p>Here are values that are supposed to resemble a VGA screen,
596including the murky brown that passes for low-intensity yellow:</p> 732including the murky brown that passes for low-intensity yellow:</p>
597</dd> 733</dd>
598<dd> 734<dd>
599<pre> 735<pre>
600 URxvt*color0: #000000 736 URxvt.color0: #000000
601 URxvt*color1: #A80000 737 URxvt.color1: #A80000
602 URxvt*color2: #00A800 738 URxvt.color2: #00A800
603 URxvt*color3: #A8A800 739 URxvt.color3: #A8A800
604 URxvt*color4: #0000A8 740 URxvt.color4: #0000A8
605 URxvt*color5: #A800A8 741 URxvt.color5: #A800A8
606 URxvt*color6: #00A8A8 742 URxvt.color6: #00A8A8
607 URxvt*color7: #A8A8A8</pre> 743 URxvt.color7: #A8A8A8</pre>
608</dd>
609<dd> 744</dd>
745<dd>
610<pre> 746<pre>
611 URxvt*color8: #000054 747 URxvt.color8: #000054
612 URxvt*color9: #FF0054 748 URxvt.color9: #FF0054
613 URxvt*color10: #00FF54 749 URxvt.color10: #00FF54
614 URxvt*color11: #FFFF54 750 URxvt.color11: #FFFF54
615 URxvt*color12: #0000FF 751 URxvt.color12: #0000FF
616 URxvt*color13: #FF00FF 752 URxvt.color13: #FF00FF
617 URxvt*color14: #00FFFF 753 URxvt.color14: #00FFFF
618 URxvt*color15: #FFFFFF</pre> 754 URxvt.color15: #FFFFFF</pre>
619</dd>
620<dd> 755</dd>
756<dd>
621<p>And here is a more complete set of non-standard colors described as 757<p>And here is a more complete set of non-standard colors described (not by
622``pretty girly'':</p> 758me) as ``pretty girly''.</p>
623</dd> 759</dd>
624<dd> 760<dd>
625<pre> 761<pre>
626 URxvt.cursorColor: #dc74d1 762 URxvt.cursorColor: #dc74d1
627 URxvt.pointerColor: #dc74d1 763 URxvt.pointerColor: #dc74d1
… …
641 URxvt.color14: #73f7ff 777 URxvt.color14: #73f7ff
642 URxvt.color7: #e1dddd 778 URxvt.color7: #e1dddd
643 URxvt.color15: #e1dddd</pre> 779 URxvt.color15: #e1dddd</pre>
644</dd> 780</dd>
645<p></p> 781<p></p>
782<dt><strong><a name="item_how_can_i_start_rxvtd_in_a_race_2dfree_way_3f">How can I start rxvtd in a race-free way?</a></strong><br />
783</dt>
784<dd>
785Try <code>rxvtd -f -o</code>, which tells rxvtd to open the
786display, create the listening socket and then fork.
787</dd>
788<p></p>
646<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 /> 789<dt><strong><a name="item_what_27s_with_the_strange_backspace_2fdelete_key_b">What's with the strange Backspace/Delete key behaviour?</a></strong><br />
647</dt> 790</dt>
648<dd> 791<dd>
649Assuming that the physical Backspace key corresponds to the 792Assuming that the physical Backspace key corresponds to the
650BackSpace keysym (not likely for Linux ... see the following 793BackSpace keysym (not likely for Linux ... see the following
… …
677 # use Backspace = ^? 820 # use Backspace = ^?
678 $ stty erase ^? 821 $ stty erase ^?
679 $ rxvt</pre> 822 $ rxvt</pre>
680</dd> 823</dd>
681<dd> 824<dd>
682<p>Toggle with ``ESC[36h'' / ``ESC[36l'' as documented in rxvt(7).</p> 825<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code> as documented in rxvt(7).</p>
683</dd> 826</dd>
684<dd> 827<dd>
685<p>For an existing rxvt-unicode:</p> 828<p>For an existing rxvt-unicode:</p>
686</dd> 829</dd>
687<dd> 830<dd>
… …
703</dd> 846</dd>
704<dd> 847<dd>
705<p>The Delete key is a another casualty of the ill-defined Backspace problem. 848<p>The Delete key is a another casualty of the ill-defined Backspace problem.
706To avoid confusion between the Backspace and Delete keys, the Delete 849To avoid confusion between the Backspace and Delete keys, the Delete
707key has been assigned an escape sequence to match the vt100 for Execute 850key has been assigned an escape sequence to match the vt100 for Execute
708(ESC[3~) and is in the supplied termcap/terminfo.</p> 851(<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p>
709</dd> 852</dd>
710<dd> 853<dd>
711<p>Some other Backspace problems:</p> 854<p>Some other Backspace problems:</p>
712</dd> 855</dd>
713<dd> 856<dd>
… …
725There are some compile-time selections available via configure. Unless 868There are some compile-time selections available via configure. Unless
726you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can 869you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can
727use the `keysym' resource to alter the keystrings associated with keysyms. 870use the `keysym' resource to alter the keystrings associated with keysyms.
728</dd> 871</dd>
729<dd> 872<dd>
730<p>Here's an example for a URxvt session started using `rxvt -name URxvt'</p> 873<p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p>
731</dd>
732<dd> 874</dd>
875<dd>
733<pre> 876<pre>
734 URxvt.keysym.Home: \e[1~ 877 URxvt.keysym.Home: \033[1~
735 URxvt.keysym.End: \e[4~ 878 URxvt.keysym.End: \033[4~
736 URxvt.keysym.C-apostrophe: \e&lt;C-'&gt; 879 URxvt.keysym.C-apostrophe: \033&lt;C-'&gt;
737 URxvt.keysym.C-slash: \e&lt;C-/&gt; 880 URxvt.keysym.C-slash: \033&lt;C-/&gt;
738 URxvt.keysym.C-semicolon: \e&lt;C-;&gt; 881 URxvt.keysym.C-semicolon: \033&lt;C-;&gt;
739 URxvt.keysym.C-grave: \e&lt;C-`&gt; 882 URxvt.keysym.C-grave: \033&lt;C-`&gt;
740 URxvt.keysym.C-comma: \e&lt;C-,&gt; 883 URxvt.keysym.C-comma: \033&lt;C-,&gt;
741 URxvt.keysym.C-period: \e&lt;C-.&gt; 884 URxvt.keysym.C-period: \033&lt;C-.&gt;
742 URxvt.keysym.C-0x60: \e&lt;C-`&gt; 885 URxvt.keysym.C-0x60: \033&lt;C-`&gt;
743 URxvt.keysym.C-Tab: \e&lt;C-Tab&gt; 886 URxvt.keysym.C-Tab: \033&lt;C-Tab&gt;
744 URxvt.keysym.C-Return: \e&lt;C-Return&gt; 887 URxvt.keysym.C-Return: \033&lt;C-Return&gt;
745 URxvt.keysym.S-Return: \e&lt;S-Return&gt; 888 URxvt.keysym.S-Return: \033&lt;S-Return&gt;
746 URxvt.keysym.S-space: \e&lt;S-Space&gt; 889 URxvt.keysym.S-space: \033&lt;S-Space&gt;
747 URxvt.keysym.M-Up: \e&lt;M-Up&gt; 890 URxvt.keysym.M-Up: \033&lt;M-Up&gt;
748 URxvt.keysym.M-Down: \e&lt;M-Down&gt; 891 URxvt.keysym.M-Down: \033&lt;M-Down&gt;
749 URxvt.keysym.M-Left: \e&lt;M-Left&gt; 892 URxvt.keysym.M-Left: \033&lt;M-Left&gt;
750 URxvt.keysym.M-Right: \e&lt;M-Right&gt; 893 URxvt.keysym.M-Right: \033&lt;M-Right&gt;
751 URxvt.keysym.M-C-0: list \e&lt;M-C- 0123456789 &gt; 894 URxvt.keysym.M-C-0: list \033&lt;M-C- 0123456789 &gt;
752 URxvt.keysym.M-C-a: list \033&lt;M-C- abcdefghijklmnopqrstuvwxyz &gt; 895 URxvt.keysym.M-C-a: list \033&lt;M-C- abcdefghijklmnopqrstuvwxyz &gt;
753 URxvt.keysym.F12: proto:\033]701;zh_CN.GBK\007</pre> 896 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre>
754</dd> 897</dd>
755<dd> 898<dd>
756<p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p> 899<p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p>
757</dd> 900</dd>
758<p></p> 901<p></p>
… …
772<dd> 915<dd>
773<p>Rather than have rxvt-unicode try to accommodate all the various possible 916<p>Rather than have rxvt-unicode try to accommodate all the various possible
774keyboard mappings, it is better to use `xmodmap' to remap the keys as 917keyboard mappings, it is better to use `xmodmap' to remap the keys as
775required for your particular machine.</p> 918required for your particular machine.</p>
776</dd> 919</dd>
777<dt><strong><a name="item_how_do_i_distinguish_if_i_27m_running_rxvt_2dunico">How do I distinguish if I'm running rxvt-unicode or a regular xterm? 920<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?
778I need this to decide about setting colors etc.</a></strong><br /> 921I need this to decide about setting colors etc.</a></strong><br />
779</dt> 922</dt>
780<dd> 923<dd>
781rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can 924rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can
782check and see if that is set. Note that several programs, JED, slrn, 925check and see if that is set. Note that several programs, JED, slrn,
… …
831</dd> 974</dd>
832<p></p></dl> 975<p></p></dl>
833<p> 976<p>
834</p> 977</p>
835<hr /> 978<hr />
836<h1><a name="synopsis">SYNOPSIS</a></h1> 979<h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1>
837<pre>
838 # set a new font set
839 printf '\33]50;%s\007' 9x15,xft:Kochi&quot; Mincho&quot;</pre>
840<pre>
841 # change the locale and tell rxvt-unicode about it
842 export LC_CTYPE=ja_JP.EUC-JP; printf &quot;\33]701;$LC_CTYPE\007&quot;</pre>
843<pre>
844 # set window title
845 printf '\33]2;%s\007' &quot;new window title&quot;</pre>
846<p> 980<p>
847</p> 981</p>
848<hr /> 982<hr />
849<h1><a name="description">DESCRIPTION</a></h1> 983<h1><a name="description">DESCRIPTION</a></h1>
850<p>The rest of this document describes various technical aspects of 984<p>The rest of this document describes various technical aspects of
… …
852followed by menu and pixmap support and last by a description of all 986followed by menu and pixmap support and last by a description of all
853features selectable at <code>configure</code> time.</p> 987features selectable at <code>configure</code> time.</p>
854<p> 988<p>
855</p> 989</p>
856<hr /> 990<hr />
857<h1><a name="rxvt_technical_reference">RXVT TECHNICAL REFERENCE</a></h1>
858<p>
859</p>
860<hr />
861<h1><a name="definitions">Definitions</a></h1> 991<h1><a name="definitions">Definitions</a></h1>
862<dl> 992<dl>
863<dt><strong><a name="item_c"><strong><code>c</code> </strong>&gt;</a></strong><br /> 993<dt><strong><a name="item_c"><strong><code>c</code> </strong>&gt;</a></strong><br />
864</dt> 994</dt>
865<dd> 995<dd>
… …
1045</dd> 1175</dd>
1046<p></p> 1176<p></p>
1047<dt><strong><a name="item_esc_z"><strong><code>ESC Z</code> </strong>&gt;</a></strong><br /> 1177<dt><strong><a name="item_esc_z"><strong><code>ESC Z</code> </strong>&gt;</a></strong><br />
1048</dt> 1178</dt>
1049<dd> 1179<dd>
1050Obsolete form of returns: <strong><code>ESC[?1;2C</code> </strong>&gt; <em>rxvt-unicode compile-time option</em> 1180Obsolete form of returns: <strong><code>ESC [ ? 1 ; 2 C</code> </strong>&gt; <em>rxvt-unicode compile-time option</em>
1051</dd> 1181</dd>
1052<p></p> 1182<p></p>
1053<dt><strong><a name="item_esc_c"><strong><code>ESC c</code> </strong>&gt;</a></strong><br /> 1183<dt><strong><a name="item_esc_c"><strong><code>ESC c</code> </strong>&gt;</a></strong><br />
1054</dt> 1184</dt>
1055<dd> 1185<dd>
… …
1066</dt> 1196</dt>
1067<dd> 1197<dd>
1068Invoke the G3 Character Set (LS3) 1198Invoke the G3 Character Set (LS3)
1069</dd> 1199</dd>
1070<p></p> 1200<p></p>
1071<dt><strong><strong><code>ESC</code> ( C</strong> &gt;&gt;</strong><br /> 1201<dt><strong><strong><code>ESC ( C</code> </strong>&gt;</strong><br />
1072</dt> 1202</dt>
1073<dd> 1203<dd>
1074Designate G0 Character Set (ISO 2022), see below for values of <a href="#item_c"><code>C</code></a>. 1204Designate G0 Character Set (ISO 2022), see below for values of <a href="#item_c"><code>C</code></a>.
1075</dd> 1205</dd>
1076<p></p> 1206<p></p>
1077<dt><strong><a name="item_esc__29_c_3e"><strong><a href="#item_esc"><code>ESC</code></a> ) C</strong> &gt;&gt;</a></strong><br /> 1207<dt><strong><a name="item_esc__29_c"><strong><code>ESC ) C</code> </strong>&gt;</a></strong><br />
1078</dt> 1208</dt>
1079<dd> 1209<dd>
1080Designate G1 Character Set (ISO 2022), see below for values of <a href="#item_c"><code>C</code></a>. 1210Designate G1 Character Set (ISO 2022), see below for values of <a href="#item_c"><code>C</code></a>.
1081</dd> 1211</dd>
1082<p></p> 1212<p></p>
… …
1257<dt><strong><a name="item_esc__5b_ps_c"><strong><code>ESC [ Ps c</code> </strong>&gt;</a></strong><br /> 1387<dt><strong><a name="item_esc__5b_ps_c"><strong><code>ESC [ Ps c</code> </strong>&gt;</a></strong><br />
1258</dt> 1388</dt>
1259<dd> 1389<dd>
1260Send Device Attributes (DA) 1390Send Device Attributes (DA)
1261<strong><code>Ps = 0</code> </strong>&gt; (or omitted): request attributes from terminal 1391<strong><code>Ps = 0</code> </strong>&gt; (or omitted): request attributes from terminal
1262returns: <strong><code>ESC[?1;2c</code> </strong>&gt; (``I am a VT100 with Advanced Video 1392returns: <strong><code>ESC [ ? 1 ; 2 c</code> </strong>&gt; (``I am a VT100 with Advanced Video
1263Option'') 1393Option'')
1264</dd> 1394</dd>
1265<p></p> 1395<p></p>
1266<dt><strong><a name="item_esc__5b_ps_d"><strong><code>ESC [ Ps d</code> </strong>&gt;</a></strong><br /> 1396<dt><strong><a name="item_esc__5b_ps_d"><strong><code>ESC [ Ps d</code> </strong>&gt;</a></strong><br />
1267</dt> 1397</dt>
… …
1388</dd> 1518</dd>
1389<table> 1519<table>
1390<tr><td>Ps = 1</td><td>Deiconify (map) window</td></tr> 1520<tr><td>Ps = 1</td><td>Deiconify (map) window</td></tr>
1391<tr><td>Ps = 2</td><td>Iconify window</td></tr> 1521<tr><td>Ps = 2</td><td>Iconify window</td></tr>
1392<tr><td>Ps = 3</td><td>ESC [ 3 ; X ; Y t Move window to (X|Y)</td></tr> 1522<tr><td>Ps = 3</td><td>ESC [ 3 ; X ; Y t Move window to (X|Y)</td></tr>
1393<tr><td>Ps = 4</td><td>ESC [ 4 ; W ; H t Resize to WxH pixels</td></tr> 1523<tr><td>Ps = 4</td><td>ESC [ 4 ; H ; W t Resize to WxH pixels</td></tr>
1394<tr><td>Ps = 5</td><td>Raise window</td></tr> 1524<tr><td>Ps = 5</td><td>Raise window</td></tr>
1395<tr><td>Ps = 6</td><td>Lower window</td></tr> 1525<tr><td>Ps = 6</td><td>Lower window</td></tr>
1396<tr><td>Ps = 7</td><td>Refresh screen once</td></tr> 1526<tr><td>Ps = 7</td><td>Refresh screen once</td></tr>
1397<tr><td>Ps = 8</td><td>ESC [ 4 ; C ; R t Resize to C columns and R rows</td></tr> 1527<tr><td>Ps = 8</td><td>ESC [ 8 ; R ; C t Resize to R rows and C columns</td></tr>
1398<tr><td>Ps = 11</td><td>Report window state (responds with Ps = 1 or Ps = 2</td></tr> 1528<tr><td>Ps = 11</td><td>Report window state (responds with Ps = 1 or Ps = 2)</td></tr>
1399<tr><td>Ps = 13</td><td>Report window position (responds with Ps = 3)</td></tr> 1529<tr><td>Ps = 13</td><td>Report window position (responds with Ps = 3)</td></tr>
1400<tr><td>Ps = 14</td><td>Report window pixel size (responds with Ps = 4)</td></tr> 1530<tr><td>Ps = 14</td><td>Report window pixel size (responds with Ps = 4)</td></tr>
1401<tr><td>Ps = 18</td><td>Report window text size (responds with Ps = 7)</td></tr> 1531<tr><td>Ps = 18</td><td>Report window text size (responds with Ps = 7)</td></tr>
1402<tr><td>Ps = 19</td><td>Currently the same as Ps = 18, but responds with Ps = 9</td></tr> 1532<tr><td>Ps = 19</td><td>Currently the same as Ps = 18, but responds with Ps = 9</td></tr>
1403<tr><td>Ps = 20</td><td>Reports icon label (ESC ] L NAME \234)</td></tr> 1533<tr><td>Ps = 20</td><td>Reports icon label (ESC ] L NAME \234)</td></tr>
… …
1618<tr><td>Ps = 13</td><td>Change colour of mouse foreground to Pt</td></tr> 1748<tr><td>Ps = 13</td><td>Change colour of mouse foreground to Pt</td></tr>
1619<tr><td>Ps = 17</td><td>Change colour of highlight characters to Pt</td></tr> 1749<tr><td>Ps = 17</td><td>Change colour of highlight characters to Pt</td></tr>
1620<tr><td>Ps = 18</td><td>Change colour of bold characters to Pt</td></tr> 1750<tr><td>Ps = 18</td><td>Change colour of bold characters to Pt</td></tr>
1621<tr><td>Ps = 19</td><td>Change colour of underlined characters to Pt</td></tr> 1751<tr><td>Ps = 19</td><td>Change colour of underlined characters to Pt</td></tr>
1622<tr><td>Ps = 20</td><td>Change default background to Pt</td></tr> 1752<tr><td>Ps = 20</td><td>Change default background to Pt</td></tr>
1623<tr><td>Ps = 39</td><td>Change default foreground colour to Pt rxvt compile-time option</td></tr> 1753<tr><td>Ps = 39</td><td>Change default foreground colour to Pt.</td></tr>
1624<tr><td>Ps = 46</td><td>Change Log File to Pt unimplemented</td></tr> 1754<tr><td>Ps = 46</td><td>Change Log File to Pt unimplemented</td></tr>
1625<tr><td>Ps = 49</td><td>Change default background colour to Pt rxvt compile-time option</td></tr> 1755<tr><td>Ps = 49</td><td>Change default background colour to Pt.</td></tr>
1626<tr><td>Ps = 50</td><td>Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n</td></tr> 1756<tr><td>Ps = 50</td><td>Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n</td></tr>
1627<tr><td>Ps = 55</td><td>Log all scrollback buffer and all of screen to Pt</td></tr> 1757<tr><td>Ps = 55</td><td>Log all scrollback buffer and all of screen to Pt</td></tr>
1628<tr><td>Ps = 701</td><td>Change current locale to Pt, or, if Pt is ?, return the current locale (rxvt extension)</td></tr> 1758<tr><td>Ps = 701</td><td>Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).</td></tr>
1629<tr><td>Ps = 703</td><td>Menubar command Pt rxvt compile-time option (rxvt-unicode extension)</td></tr> 1759<tr><td>Ps = 703</td><td>Menubar command Pt (Compile menubar).</td></tr>
1630<tr><td>Ps = 704</td><td>Change colour of italic characters to Pt</td></tr> 1760<tr><td>Ps = 704</td><td>Change colour of italic characters to Pt</td></tr>
1631<tr><td>Ps = 705</td><td>Change background pixmap tint colour to Pt</td></tr> 1761<tr><td>Ps = 705</td><td>Change background pixmap tint colour to Pt (Compile transparency).</td></tr>
1632<tr><td>Ps = 710</td><td>Set normal fontset to Pt. Same as Ps = 50.</td></tr> 1762<tr><td>Ps = 710</td><td>Set normal fontset to Pt. Same as Ps = 50.</td></tr>
1633<tr><td>Ps = 711</td><td>Set bold fontset to Pt. Similar to Ps = 50.</td></tr> 1763<tr><td>Ps = 711</td><td>Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
1634<tr><td>Ps = 712</td><td>Set italic fontset to Pt. Similar to Ps = 50.</td></tr> 1764<tr><td>Ps = 712</td><td>Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
1635<tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50.</td></tr> 1765<tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
1766<tr><td>Ps = 720</td><td>Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>
1767<tr><td>Ps = 721</td><td>Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>
1636</table><p></p></dl> 1768</table><p></p></dl>
1637<p></p> 1769<p></p>
1638<p> 1770<p>
1639</p> 1771</p>
1640<hr /> 1772<hr />
… …
1686<dt><strong><a name="item__5btitle_3a_2bstring_5d"><strong>[title:+<em>string</em>] </strong>&gt;</a></strong><br /> 1818<dt><strong><a name="item__5btitle_3a_2bstring_5d"><strong>[title:+<em>string</em>] </strong>&gt;</a></strong><br />
1687</dt> 1819</dt>
1688<dd> 1820<dd>
1689set the current menuBar's title to <em>string</em>, which may contain the 1821set the current menuBar's title to <em>string</em>, which may contain the
1690following format specifiers: 1822following format specifiers:
1691<strong>%%</strong> : literal <strong>%</strong> character 1823</dd>
1692<strong>%n</strong> : rxvt name (as per the <strong>-name</strong> command-line option) 1824<dd>
1693<strong>%v</strong> : rxvt version 1825<pre>
1826 B&lt;%n&gt; rxvt name (as per the B&lt;-name&gt; command-line option)
1827 B&lt;%v&gt; rxvt version
1828 B&lt;%%&gt; literal B&lt;%&gt; character</pre>
1694</dd> 1829</dd>
1695<p></p> 1830<p></p>
1696<dt><strong><a name="item__5bdone_5d"><strong>[done]</strong></a></strong><br /> 1831<dt><strong><a name="item__5bdone_5d"><strong>[done]</strong></a></strong><br />
1697</dt> 1832</dt>
1698<dd> 1833<dd>
… …
1890non-+<strong>NUL</strong> characters, the leading <strong>NUL</strong> is stripped off and the 2025non-+<strong>NUL</strong> characters, the leading <strong>NUL</strong> is stripped off and the
1891balance is sent back to rxvt.</p> 2026balance is sent back to rxvt.</p>
1892<p>As a convenience for the many Emacs-type editors, <em>action</em> may start 2027<p>As a convenience for the many Emacs-type editors, <em>action</em> may start
1893with <strong>M-</strong> (eg, <strong>M-$</strong> is equivalent to <strong>\E$</strong>) and a <strong>CR</strong> will be 2028with <strong>M-</strong> (eg, <strong>M-$</strong> is equivalent to <strong>\E$</strong>) and a <strong>CR</strong> will be
1894appended if missed from <strong>M-x</strong> commands.</p> 2029appended if missed from <strong>M-x</strong> commands.</p>
1895<p>As a convenience for issuing XTerm <strong>ESC]</strong> sequences from a menubar (or 2030<p>As a convenience for issuing XTerm <strong>ESC ]</strong> sequences from a menubar (or
1896quick arrow), a <strong>BEL</strong> (<strong>^G</strong>) will be appended if needed.</p> 2031quick arrow), a <strong>BEL</strong> (<strong>^G</strong>) will be appended if needed.</p>
1897<dl> 2032<dl>
1898<dt><strong><a name="item_for_example_2c">For example,</a></strong><br /> 2033<dt><strong><a name="item_for_example_2c">For example,</a></strong><br />
1899</dt> 2034</dt>
1900<dd> 2035<dd>
… …
2432</dd> 2567</dd>
2433<p></p> 2568<p></p>
2434<dt><strong><a name="item__2d_2dwith_2dcodesets_3dname_2c_2e_2e_2e">--with-codesets=NAME,...</a></strong><br /> 2569<dt><strong><a name="item__2d_2dwith_2dcodesets_3dname_2c_2e_2e_2e">--with-codesets=NAME,...</a></strong><br />
2435</dt> 2570</dt>
2436<dd> 2571<dd>
2437Compile in support for additional codeset (encoding) groups (eu, vn are 2572Compile in support for additional codeset (encoding) groups (<code>eu</code>, <code>vn</code>
2438always compiled in, which includes most 8-bit character sets). These 2573are always compiled in, which includes most 8-bit character sets). These
2439codeset tables are currently only used for driving X11 core fonts, they 2574codeset tables are used for driving X11 core fonts, they are not required
2440are not required for Xft fonts. Compiling them in will make your binary 2575for Xft fonts, although having them compiled in lets rxvt-unicode choose
2441bigger (together about 700kB), but it doesn't increase memory usage unless 2576replacement fonts more intelligently. Compiling them in will make your
2577binary bigger (all of together cost about 700kB), but it doesn't increase
2442you use an X11 font requiring one of these encodings. 2578memory usage unless you use a font requiring one of these encodings.
2443</dd> 2579</dd>
2444<table> 2580<table>
2445<tr><td>all</td><td>all available codeset groups</td></tr> 2581<tr><td>all</td><td>all available codeset groups</td></tr>
2446<tr><td>zh</td><td>common chinese encodings</td></tr> 2582<tr><td>zh</td><td>common chinese encodings</td></tr>
2447<tr><td>zh_ext</td><td>rarely used but very big chinese encodigs</td></tr> 2583<tr><td>zh_ext</td><td>rarely used but very big chinese encodigs</td></tr>
… …
2481where accents are encoded as seperate unicode characters. This is 2617where accents are encoded as seperate unicode characters. This is
2482done by using precomposited characters when available or creating 2618done by using precomposited characters when available or creating
2483new pseudo-characters when no precomposed form exists. 2619new pseudo-characters when no precomposed form exists.
2484</dd> 2620</dd>
2485<dd> 2621<dd>
2486<p>Without --enable-unicode3, the number of additional precomposed 2622<p>Without --enable-unicode3, the number of additional precomposed characters
2487characters is rather limited (2048, if this is full, rxvt will use the 2623is rather limited (2048, if this is full, rxvt-unicode will use the
2488private use area, extending the number of combinations to 8448). With 2624private use area, extending the number of combinations to 8448). With
2489--enable-unicode3, no practical limit exists. This will also enable 2625--enable-unicode3, no practical limit exists.</p>
2490storage of characters &gt;65535.</p> 2626</dd>
2627<dd>
2628<p>This option will also enable storage (but not display) of characters
2629beyond plane 0 (&gt;65535) when --enable-unicode3 was not specified.</p>
2491</dd> 2630</dd>
2492<dd> 2631<dd>
2493<p>The combining table also contains entries for arabic presentation forms, 2632<p>The combining table also contains entries for arabic presentation forms,
2494but these are not currently used. Bug me if you want these to be used.</p> 2633but these are not currently used. Bug me if you want these to be used (and
2634tell me how these are to be used...).</p>
2495</dd> 2635</dd>
2496<p></p> 2636<p></p>
2497<dt><strong><a name="item_fallback">--enable-fallback(=CLASS)</a></strong><br /> 2637<dt><strong><a name="item_fallback">--enable-fallback(=CLASS)</a></strong><br />
2498</dt> 2638</dt>
2499<dd> 2639<dd>
… …
2633<p></p> 2773<p></p>
2634<dt><strong><a name="item__2d_2denable_2dxgetdefault">--enable-xgetdefault</a></strong><br /> 2774<dt><strong><a name="item__2d_2denable_2dxgetdefault">--enable-xgetdefault</a></strong><br />
2635</dt> 2775</dt>
2636<dd> 2776<dd>
2637Make resources checking via <code>XGetDefault()</code> instead of our small 2777Make resources checking via <code>XGetDefault()</code> instead of our small
2638version which only checks ~/.Xdefaults, or if that doesn't exist 2778version which only checks ~/.Xdefaults, or if that doesn't exist then
2639then ~/.Xresources. 2779~/.Xresources.
2780</dd>
2781<dd>
2782<p>Please note that nowadays, things like XIM will automatically pull in and
2783use the full X resource manager, so the overhead of using it might be very
2784small, if nonexistant.</p>
2640</dd> 2785</dd>
2641<p></p> 2786<p></p>
2642<dt><strong><a name="item__2d_2denable_2dstrings">--enable-strings</a></strong><br /> 2787<dt><strong><a name="item__2d_2denable_2dstrings">--enable-strings</a></strong><br />
2643</dt> 2788</dt>
2644<dd> 2789<dd>
… …
2667in combination with other switches) is:</p> 2812in combination with other switches) is:</p>
2668</dd> 2813</dd>
2669<dd> 2814<dd>
2670<pre> 2815<pre>
2671 MWM-hints 2816 MWM-hints
2817 EWMH-hints (pid, utf8 names) and protocols (ping)
2672 seperate underline colour 2818 seperate underline colour
2673 settable border widths and borderless switch 2819 settable border widths and borderless switch
2674 settable extra linespacing 2820 settable extra linespacing
2675 extra window properties (e.g. UTF-8 window names and PID)
2676 iso-14755-2 and -3, and visual feedback 2821 iso-14755-2 and -3, and visual feedback
2677 backindex and forwardindex escape sequence 2822 backindex and forwardindex escape sequence
2678 window op and locale change escape sequences 2823 window op and some xterm/OSC escape sequences
2679 tripleclickwords 2824 tripleclickwords
2680 settable insecure mode</pre> 2825 settable insecure mode
2826 keysym remapping support
2827 cursor blinking and underline cursor
2828 -embed and -pty-fd options</pre>
2681</dd> 2829</dd>
2682<p></p> 2830<p></p>
2683<dt><strong><a name="item__2d_2denable_2diso14755">--enable-iso14755</a></strong><br /> 2831<dt><strong><a name="item__2d_2denable_2diso14755">--enable-iso14755</a></strong><br />
2684</dt> 2832</dt>
2685<dd> 2833<dd>
… …
2740</dt> 2888</dt>
2741<dd> 2889<dd>
2742Add smart growth/shrink behaviour when changing font size via from hot 2890Add smart growth/shrink behaviour when changing font size via from hot
2743keys. This should keep in a fixed position the rxvt corner which is 2891keys. This should keep in a fixed position the rxvt corner which is
2744closest to a corner of the screen. 2892closest to a corner of the screen.
2745</dd>
2746<p></p>
2747<dt><strong><a name="item__2d_2denable_2dcursor_2dblink">--enable-cursor-blink</a></strong><br />
2748</dt>
2749<dd>
2750Add support for a blinking cursor.
2751</dd> 2893</dd>
2752<p></p> 2894<p></p>
2753<dt><strong><a name="item__2d_2denable_2dpointer_2dblank">--enable-pointer-blank</a></strong><br /> 2895<dt><strong><a name="item__2d_2denable_2dpointer_2dblank">--enable-pointer-blank</a></strong><br />
2754</dt> 2896</dt>
2755<dd> 2897<dd>

Diff Legend

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