… | |
… | |
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" Mincho"</pre> |
|
|
58 | <pre> |
|
|
59 | # change the locale and tell rxvt-unicode about it |
|
|
60 | export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"</pre> |
|
|
61 | <pre> |
|
|
62 | # set window title |
|
|
63 | printf '\33]2;%s\007' "new window title"</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 |
|
|
69 | all escape sequences, and other background information.</p> |
|
|
70 | <p>The newest version of this document is |
|
|
71 | also 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> |
58 | The version number is displayed with the usage (-h). Also the escape |
81 | The version number is displayed with the usage (-h). Also the escape |
59 | sequence <code>ESC[8n</code> sets the window title to the version number. |
82 | sequence <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> |
|
|
88 | The Debian GNU/Linux package of rxvt-unicode contains large patches that |
|
|
89 | considerably change the behaviour of rxvt-unicode. Before reporting a |
|
|
90 | bug to the original rxvt-unicode author please download and install the |
|
|
91 | genuine version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to |
|
|
92 | reproduce the problem. If you cannot, chances are that the problems are |
|
|
93 | specific to Debian GNU/Linux, in which case it should be reported via the |
|
|
94 | Debian Bug Tracking System (use <code>reportbug</code> to report the bug). |
|
|
95 | </dd> |
|
|
96 | <dd> |
|
|
97 | <p>For other problems that also affect the Debian package, you can and |
|
|
98 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
99 | bug in the Debian version and it serves as a reminder for other users that |
|
|
100 | might encounter the same issue.</p> |
60 | </dd> |
101 | </dd> |
61 | <p></p> |
102 | <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 /> |
103 | <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> |
104 | </dt> |
64 | <dd> |
105 | <dd> |
… | |
… | |
83 | problems arising, which includes wrong keymapping, less and different |
124 | problems arising, which includes wrong keymapping, less and different |
84 | colours and some refresh errors in fullscreen applications. It's a nice |
125 | colours and some refresh errors in fullscreen applications. It's a nice |
85 | quick-and-dirty workaround for rare cases, though.</p> |
126 | quick-and-dirty workaround for rare cases, though.</p> |
86 | </dd> |
127 | </dd> |
87 | <dd> |
128 | <dd> |
88 | <p>If you always want to do this you can either recompile rxvt-unicode with |
129 | <p>If you always want to do this (and are fine with the consequences) you |
89 | the desired TERM value or use a resource to set it:</p> |
130 | can either recompile rxvt-unicode with the desired TERM value or use a |
|
|
131 | resource to set it:</p> |
90 | </dd> |
132 | </dd> |
91 | <dd> |
133 | <dd> |
92 | <pre> |
134 | <pre> |
93 | URxvt.termName: rxvt</pre> |
135 | URxvt.termName: rxvt</pre> |
94 | </dd> |
136 | </dd> |
95 | <dd> |
137 | <dd> |
96 | <p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace |
138 | <p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace |
97 | the rxvt terminfo file with the rxvt-unicode one.</p> |
139 | the rxvt terminfo file with the rxvt-unicode one.</p> |
98 | </dd> |
140 | </dd> |
99 | <p></p> |
141 | <p></p> |
|
|
142 | <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 /> |
|
|
143 | </dt> |
100 | <dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br /> |
144 | <dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br /> |
101 | </dt> |
145 | </dt> |
102 | <dd> |
146 | <dd> |
|
|
147 | One reason you might want this is that some distributions or operating |
|
|
148 | systems still compile some programs using the long-obsoleted termcap |
|
|
149 | (Fedora Core's bash is one example) and rely on a termcap entry for |
|
|
150 | <code>rxvt-unicode</code>. |
|
|
151 | </dd> |
|
|
152 | <dd> |
103 | You could use rxvt's termcap entry with resonable results in many cases. |
153 | <p>You could use rxvt's termcap entry with resonable results in many cases. |
104 | You can also create a termcap entry by using terminfo's infocmp program |
154 | You can also create a termcap entry by using terminfo's infocmp program |
105 | like this: |
155 | like this:</p> |
106 | </dd> |
156 | </dd> |
107 | <dd> |
157 | <dd> |
108 | <pre> |
158 | <pre> |
109 | infocmp -C rxvt-unicode</pre> |
159 | infocmp -C rxvt-unicode</pre> |
110 | </dd> |
160 | </dd> |
111 | <dd> |
161 | <dd> |
112 | <p>OR you could this termcap entry:</p> |
162 | <p>Or you could use this termcap entry, generated by the command above:</p> |
113 | </dd> |
163 | </dd> |
114 | <dd> |
164 | <dd> |
115 | <pre> |
165 | <pre> |
116 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
166 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
117 | :am:bw:eo:km:mi:ms:xn:xo:\ |
167 | :am:bw:eo:km:mi:ms:xn:xo:\ |
… | |
… | |
172 | file, so you will need to install it on your own (See the question <strong>When |
222 | file, so you will need to install it on your own (See the question <strong>When |
173 | I log-in to another system it tells me about missing terminfo data?</strong> on |
223 | I log-in to another system it tells me about missing terminfo data?</strong> on |
174 | how to do this). |
224 | how to do this). |
175 | </dd> |
225 | </dd> |
176 | <p></p> |
226 | <p></p> |
|
|
227 | <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 /> |
|
|
228 | </dt> |
|
|
229 | <dd> |
|
|
230 | Some Debian GNUL/Linux users seem to have this problem, although no |
|
|
231 | specific details were reported so far. It is possible that this is caused |
|
|
232 | by the wrong <code>TERM</code> setting, although the details of wether and how |
|
|
233 | this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible |
|
|
234 | keymap. See the answer to the previous question, and please report if that |
|
|
235 | helped. |
|
|
236 | </dd> |
|
|
237 | <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 /> |
238 | <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> |
239 | </dt> |
179 | <dt><strong><a name="item_unicode_does_not_seem_to_work_3f">Unicode does not seem to work?</a></strong><br /> |
240 | <dt><strong><a name="item_unicode_does_not_seem_to_work_3f">Unicode does not seem to work?</a></strong><br /> |
180 | </dt> |
241 | </dt> |
181 | <dd> |
242 | <dd> |
… | |
… | |
185 | </dd> |
246 | </dd> |
186 | <dd> |
247 | <dd> |
187 | <p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the |
248 | <p>Rxvt-unicode must be started with the same <code>LC_CTYPE</code> setting as the |
188 | programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the |
249 | programs. Often rxvt-unicode is started in the <a href="#item_c"><code>C</code></a> locale, while the |
189 | login script running within the rxvt-unicode window changes the locale to |
250 | login script running within the rxvt-unicode window changes the locale to |
190 | sth. else, e.h. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p> |
251 | something else, e.g. <code>en_GB.UTF-8</code>. Needless to say, this is not going to work.</p> |
191 | </dd> |
252 | </dd> |
192 | <dd> |
253 | <dd> |
193 | <p>The best thing is to fix your startup environment, as you will likely run |
254 | <p>The best thing is to fix your startup environment, as you will likely run |
194 | into other problems. If nothing works you can try this in your .profile.</p> |
255 | into other problems. If nothing works you can try this in your .profile.</p> |
195 | </dd> |
256 | </dd> |
… | |
… | |
198 | printf '\e]701;%s\007' "$LC_CTYPE"</pre> |
259 | printf '\e]701;%s\007' "$LC_CTYPE"</pre> |
199 | </dd> |
260 | </dd> |
200 | <dd> |
261 | <dd> |
201 | <p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not |
262 | <p>If this doesn't work, then maybe you use a <code>LC_CTYPE</code> specification not |
202 | supported on your systems. Some systems have a <code>locale</code> command which |
263 | supported on your systems. Some systems have a <code>locale</code> command which |
203 | displays this. If it displays sth. like:</p> |
264 | displays this (also, <code>perl -e0</code> can be used to check locale settings, as |
|
|
265 | it will complain loudly if it cannot set the locale). If it displays something |
|
|
266 | like:</p> |
204 | </dd> |
267 | </dd> |
205 | <dd> |
268 | <dd> |
206 | <pre> |
269 | <pre> |
207 | locale: Cannot set LC_CTYPE to default locale: ...</pre> |
270 | locale: Cannot set LC_CTYPE to default locale: ...</pre> |
208 | </dd> |
271 | </dd> |
… | |
… | |
226 | to display. |
289 | to display. |
227 | </dd> |
290 | </dd> |
228 | <dd> |
291 | <dd> |
229 | <p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement |
292 | <p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement |
230 | font. Often the result is fine, but sometimes the chosen font looks |
293 | font. Often the result is fine, but sometimes the chosen font looks |
231 | bad. Many fonts have totally strange characters that don't resemble the |
294 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
232 | correct glyph at all, and rxvt-unicode lacks the artificial intelligence |
295 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
233 | to detect that a specific glyph is wrong: it has to believe the font that |
296 | intelligence to detect that a specific glyph is wrong: it has to believe |
234 | the characters it contains indeed look correct.</p> |
297 | the font that the characters it claims to contain indeed look correct.</p> |
235 | </dd> |
298 | </dd> |
236 | <dd> |
299 | <dd> |
237 | <p>In that case, select a font of your taste and add it to the font list, |
300 | <p>In that case, select a font of your taste and add it to the font list, |
238 | e.g.:</p> |
301 | e.g.:</p> |
239 | </dd> |
302 | </dd> |
… | |
… | |
246 | font. If the base font does not contain the character, it will go to the |
309 | font. If the base font does not contain the character, it will go to the |
247 | next font, and so on. Specifying your own fonts will also speed up this |
310 | next font, and so on. Specifying your own fonts will also speed up this |
248 | search and use less resources within rxvt-unicode and the X-server.</p> |
311 | search and use less resources within rxvt-unicode and the X-server.</p> |
249 | </dd> |
312 | </dd> |
250 | <dd> |
313 | <dd> |
251 | <p>The only limitation is that all the fonts must not be larger than the base |
314 | <p>The only limitation is that none of the fonts may be larger than the base |
252 | font, as the base font defines the principal cell size, which must be the |
315 | font, as the base font defines the terminal character cell size, which |
253 | same due to the way terminals work.</p> |
316 | must be the same due to the way terminals work.</p> |
254 | </dd> |
317 | </dd> |
255 | <p></p> |
318 | <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 /> |
319 | <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> |
320 | </dt> |
258 | <dd> |
321 | <dd> |
259 | This is because there is a difference between script and language -- |
322 | This is because there is a difference between script and language -- |
260 | rxvt-unicode does not know which language the text that is output |
323 | rxvt-unicode does not know which language the text that is output is, |
261 | is, as it only knows the unicode character codes. If rxvt-unicode |
324 | as it only knows the unicode character codes. If rxvt-unicode first |
262 | first sees a japanese character, it might choose a japanese font for |
325 | sees a japanese/chinese character, it might choose a japanese font for |
263 | it. Subsequent japanese characters will take that font. Now, many chinese |
326 | display. Subsequent japanese characters will use that font. Now, many |
264 | characters aren't represented in japanese fonts, so when the first |
327 | chinese characters aren't represented in japanese fonts, so when the first |
265 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
328 | non-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 |
329 | -- unfortunately at this point, it will still use the japanese font for |
267 | japanese characters that are also chinese. |
330 | chinese characters that are also in the japanese font. |
268 | </dd> |
331 | </dd> |
269 | <dd> |
332 | <dd> |
270 | <p>The workaround is easy: just tag a chinese font at the end of your font |
333 | <p>The workaround is easy: just tag a chinese font at the end of your font |
271 | list (see the previous question). The key is to view the font list as |
334 | list (see the previous question). The key is to view the font list as |
272 | a preference list: If you expect more japanese, list a japanese font |
335 | a preference list: If you expect more japanese, list a japanese font |
273 | first. If you expect more chinese, put a chinese font first.</p> |
336 | first. If you expect more chinese, put a chinese font first.</p> |
274 | </dd> |
337 | </dd> |
275 | <dd> |
338 | <dd> |
276 | <p>In the future it might be possible to switch preferences at runtime (the |
339 | <p>In the future it might be possible to switch language preferences at |
277 | internal data structure has no problem with using different fonts for |
340 | runtime (the internal data structure has no problem with using different |
278 | the same character at the same time, but no interface for this has been |
341 | fonts for the same character at the same time, but no interface for this |
279 | designed yet).</p> |
342 | has been designed yet).</p> |
|
|
343 | </dd> |
|
|
344 | <dd> |
|
|
345 | <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> |
346 | </dd> |
281 | <p></p> |
347 | <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 /> |
348 | <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> |
349 | </dt> |
284 | <dd> |
350 | <dd> |
… | |
… | |
332 | </dd> |
398 | </dd> |
333 | <p></p> |
399 | <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 /> |
400 | <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> |
401 | </dt> |
336 | <dd> |
402 | <dd> |
337 | First of all, make sure you are running with the right terminfo |
403 | First 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 |
404 | (<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then |
339 | you have specified colours for italic and bold, as otherwise rxvt-unicode |
405 | make sure you have specified colours for italic and bold, as otherwise |
340 | might use reverse video to simulate the effect: |
406 | rxvt-unicode might use reverse video to simulate the effect: |
341 | </dd> |
|
|
342 | <dd> |
407 | </dd> |
|
|
408 | <dd> |
343 | <pre> |
409 | <pre> |
344 | URxvt*colorBD: white |
410 | URxvt.colorBD: white |
345 | URxvt*colorIT: green</pre> |
411 | URxvt.colorIT: green</pre> |
346 | </dd> |
412 | </dd> |
347 | <p></p> |
413 | <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 /> |
414 | <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> |
415 | </dt> |
350 | <dd> |
416 | <dd> |
351 | For some unexplainable reason, some programs (i.e. irssi) assume a very |
417 | For some unexplainable reason, some rare programs assume a very weird |
352 | weird colour palette when confronted with a terminal with more than the |
418 | colour palette when confronted with a terminal with more than the standard |
353 | standard 8 colours (rxvt-unicode supports 88). The right fix is, of |
419 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
354 | course, to fix these programs not to assume non-ISO colours without very |
420 | these programs not to assume non-ISO colours without very good reasons. |
355 | good reasons. |
|
|
356 | </dd> |
|
|
357 | <dd> |
421 | </dd> |
|
|
422 | <dd> |
358 | <p>In the meantime, you can either edit your <code>urxvt</code> terminfo definition to |
423 | <p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo |
359 | only claim 8 colour support or use <code>TERM=rxvt</code>, which will fix colours |
424 | definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will |
360 | but keep you from using other rxvt-unicode features.</p> |
425 | fix colours but keep you from using other rxvt-unicode features.</p> |
361 | </dd> |
426 | </dd> |
362 | <p></p> |
427 | <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 /> |
428 | <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> |
429 | </dt> |
365 | <dd> |
430 | <dd> |
… | |
… | |
369 | <strong>wchar_t</strong> is represented as unicode. |
434 | <strong>wchar_t</strong> is represented as unicode. |
370 | </dd> |
435 | </dd> |
371 | <dd> |
436 | <dd> |
372 | <p>As you might have guessed, FreeBSD does neither define this symobl nor |
437 | <p>As you might have guessed, FreeBSD does neither define this symobl nor |
373 | does it support it. Instead, it uses it's own internal representation of |
438 | does it support it. Instead, it uses it's own internal representation of |
374 | <strong>wchar_t</strong>. This is, of course, completely legal.</p> |
439 | <strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p> |
375 | </dd> |
440 | </dd> |
376 | <dd> |
441 | <dd> |
377 | <p>However, <code>__STDC_ISO_10646__</code> is the only sane way to support |
442 | <p>However, <code>__STDC_ISO_10646__</code> is the only sane way to support |
378 | multi-language apps in an OS, as using a locale-dependent (and |
443 | multi-language apps in an OS, as using a locale-dependent (and |
379 | non-standardized) representation of <strong>wchar_t</strong> makes it impossible to |
444 | non-standardized) representation of <strong>wchar_t</strong> makes it impossible to |
… | |
… | |
390 | encodings slightly different than the terminal emulator).</p> |
455 | encodings slightly different than the terminal emulator).</p> |
391 | </dd> |
456 | </dd> |
392 | <dd> |
457 | <dd> |
393 | <p>The rxvt-unicode author insists that the right way to fix this is in the |
458 | <p>The rxvt-unicode author insists that the right way to fix this is in the |
394 | system libraries once and for all, instead of forcing every app to carry |
459 | system libraries once and for all, instead of forcing every app to carry |
395 | complete replacements.</p> |
460 | complete replacements for them :)</p> |
396 | </dd> |
461 | </dd> |
397 | <p></p> |
462 | <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 /> |
463 | <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> |
464 | </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 /> |
465 | <dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br /> |
… | |
… | |
405 | UTF-8 or any other encodings with respect to terminal I/O. |
470 | UTF-8 or any other encodings with respect to terminal I/O. |
406 | </dd> |
471 | </dd> |
407 | <dd> |
472 | <dd> |
408 | <p>The reasons is that there exists a perfectly fine mechanism for selecting |
473 | <p>The reasons is that there exists a perfectly fine mechanism for selecting |
409 | the encoding, doing I/O and (most important) communicating this to all |
474 | the encoding, doing I/O and (most important) communicating this to all |
410 | applications so everybody agrees on character properties such as width and |
475 | applications so everybody agrees on character properties such as width |
411 | code number. This mechanism is the <em>locale</em>.</p> |
476 | and code number. This mechanism is the <em>locale</em>. Applications not using |
|
|
477 | that info will have problems (for example, <code>xterm</code> gets the width of |
|
|
478 | characters wrong as it uses it's own, locale-independent table under all |
|
|
479 | locales).</p> |
412 | </dd> |
480 | </dd> |
413 | <dd> |
481 | <dd> |
414 | <p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All |
482 | <p>Rxvt-unicode uses the <code>LC_CTYPE</code> locale category to select encoding. All |
415 | programs doing the same (that is, most) will automatically agree in the |
483 | programs doing the same (that is, most) will automatically agree in the |
416 | interpretation of characters.</p> |
484 | interpretation of characters.</p> |
… | |
… | |
427 | (i.e. <code>de</code> or <code>german</code>) are also common.</p> |
495 | (i.e. <code>de</code> or <code>german</code>) are also common.</p> |
428 | </dd> |
496 | </dd> |
429 | <dd> |
497 | <dd> |
430 | <p>Rxvt-unicode ignores all other locale categories, and except for |
498 | <p>Rxvt-unicode ignores all other locale categories, and except for |
431 | the encoding, ignores country or language-specific settings, |
499 | the encoding, ignores country or language-specific settings, |
432 | i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the same for rxvt-unicode.</p> |
500 | i.e. <code>de_DE.UTF-8</code> and <code>ja_JP.UTF-8</code> are the normally same to |
|
|
501 | rxvt-unicode.</p> |
433 | </dd> |
502 | </dd> |
434 | <dd> |
503 | <dd> |
435 | <p>If you want to use a specific encoding you have to make sure you start |
504 | <p>If you want to use a specific encoding you have to make sure you start |
436 | rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p> |
505 | rxvt-unicode with the correct <code>LC_CTYPE</code> category.</p> |
437 | </dd> |
506 | </dd> |
438 | <p></p> |
507 | <p></p> |
439 | <dt><strong><a name="item_can_i_switch_locales_at_runtime_3f">Can I switch locales at runtime?</a></strong><br /> |
508 | <dt><strong><a name="item_can_i_switch_locales_at_runtime_3f">Can I switch locales at runtime?</a></strong><br /> |
440 | </dt> |
509 | </dt> |
441 | <dd> |
510 | <dd> |
442 | Yes, using an escape sequence. Try sth. like this, which sets |
511 | Yes, using an escape sequence. Try something like this, which sets |
443 | rxvt-unicode's idea of <code>LC_CTYPE</code>. |
512 | rxvt-unicode's idea of <code>LC_CTYPE</code>. |
444 | </dd> |
513 | </dd> |
445 | <dd> |
514 | <dd> |
446 | <pre> |
515 | <pre> |
447 | printf '\e]701;%s\007' ja_JP.SJIS</pre> |
516 | printf '\e]701;%s\007' ja_JP.SJIS</pre> |
448 | </dd> |
517 | </dd> |
449 | <dd> |
518 | <dd> |
450 | <p>See also the previous question.</p> |
519 | <p>See also the previous answer.</p> |
451 | </dd> |
|
|
452 | <dd> |
520 | </dd> |
|
|
521 | <dd> |
453 | <p>Sometimes this capability is rather handy when you want to work in one |
522 | <p>Sometimes this capability is rather handy when you want to work in |
454 | locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support UTF-8. For |
523 | one locale (e.g. <code>de_DE.UTF-8</code>) but some programs don't support it |
455 | example, I use this script to start <code>xjdic</code>, which first switches to a |
524 | (e.g. UTF-8). For example, I use this script to start <code>xjdic</code>, which |
456 | locale supported by xjdic and back later:</p> |
525 | first switches to a locale supported by xjdic and back later:</p> |
457 | </dd> |
526 | </dd> |
458 | <dd> |
527 | <dd> |
459 | <pre> |
528 | <pre> |
460 | printf '\e]701;%s\007' ja_JP.SJIS |
529 | printf '\e]701;%s\007' ja_JP.SJIS |
461 | xjdic -js |
530 | xjdic -js |
462 | printf '\e]701;%s\007' de_DE.UTF-8</pre> |
531 | printf '\e]701;%s\007' de_DE.UTF-8</pre> |
463 | </dd> |
532 | </dd> |
|
|
533 | <dd> |
|
|
534 | <p>You can also use xterm's <code>luit</code> program, which usually works fine, except |
|
|
535 | for some locales where character width differs between program- and |
|
|
536 | rxvt-unicode-locales.</p> |
|
|
537 | </dd> |
464 | <p></p> |
538 | <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 /> |
539 | <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> |
540 | </dt> |
467 | <dd> |
541 | <dd> |
468 | Yes, using an escape sequence. Try sth. like this, which has the same |
542 | Yes, using an escape sequence. Try something like this, which has the same |
469 | effect as using the <code>-fn</code> switch, and takes effect immediately: |
543 | effect as using the <code>-fn</code> switch, and takes effect immediately: |
470 | </dd> |
544 | </dd> |
471 | <dd> |
545 | <dd> |
472 | <pre> |
546 | <pre> |
473 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"</pre> |
547 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"</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 /> |
558 | <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> |
559 | </dt> |
486 | <dd> |
560 | <dd> |
487 | Many fonts have difficulties with italic characters and hinting. For |
561 | Many fonts have difficulties with italic characters and hinting. For |
488 | example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans |
562 | example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans |
489 | Mono</code> completely fails in it's italic face. A workaround is to enable |
563 | Mono</code> completely fails in it's italic face. A workaround might be to |
490 | freetype autohinting, i.e. like this: |
564 | enable freetype autohinting, i.e. like this: |
491 | </dd> |
|
|
492 | <dd> |
565 | </dd> |
|
|
566 | <dd> |
493 | <pre> |
567 | <pre> |
494 | URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
568 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
495 | URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> |
569 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre> |
496 | </dd> |
570 | </dd> |
497 | <p></p> |
571 | <p></p> |
498 | <dt><strong><a name="item_my_input_method_wants__3csome_encoding_3e_but_i_wa">My input method wants <some encoding> but I want UTF-8, what can I do?</a></strong><br /> |
572 | <dt><strong><a name="item_my_input_method_wants__3csome_encoding_3e_but_i_wa">My input method wants <some encoding> but I want UTF-8, what can I do?</a></strong><br /> |
499 | </dt> |
573 | </dt> |
500 | <dd> |
574 | <dd> |
… | |
… | |
513 | </dd> |
587 | </dd> |
514 | <p></p> |
588 | <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 /> |
589 | <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> |
590 | </dt> |
517 | <dd> |
591 | <dd> |
518 | Rxvt-unicode tries to obey the rule of not charging you for sth. you |
592 | Rxvt-unicode tries to obey the rule of not charging you for something you |
519 | don't use. One thing you should try is to configure out all settings that |
593 | don't use. One thing you should try is to configure out all settings that |
520 | you don't need, for example, Xft support is a resource hog by design, |
594 | you don't need, for example, Xft support is a resource hog by design, |
521 | when used. Compiling it out ensures that no Xft font will be loaded |
595 | when used. Compiling it out ensures that no Xft font will be loaded |
522 | accidentally when rxvt-unicode tries to find a font for your characters. |
596 | accidentally when rxvt-unicode tries to find a font for your characters. |
523 | </dd> |
597 | </dd> |
… | |
… | |
595 | <p>Here are values that are supposed to resemble a VGA screen, |
669 | <p>Here are values that are supposed to resemble a VGA screen, |
596 | including the murky brown that passes for low-intensity yellow:</p> |
670 | including the murky brown that passes for low-intensity yellow:</p> |
597 | </dd> |
671 | </dd> |
598 | <dd> |
672 | <dd> |
599 | <pre> |
673 | <pre> |
600 | URxvt*color0: #000000 |
674 | URxvt.color0: #000000 |
601 | URxvt*color1: #A80000 |
675 | URxvt.color1: #A80000 |
602 | URxvt*color2: #00A800 |
676 | URxvt.color2: #00A800 |
603 | URxvt*color3: #A8A800 |
677 | URxvt.color3: #A8A800 |
604 | URxvt*color4: #0000A8 |
678 | URxvt.color4: #0000A8 |
605 | URxvt*color5: #A800A8 |
679 | URxvt.color5: #A800A8 |
606 | URxvt*color6: #00A8A8 |
680 | URxvt.color6: #00A8A8 |
607 | URxvt*color7: #A8A8A8</pre> |
681 | URxvt.color7: #A8A8A8</pre> |
608 | </dd> |
|
|
609 | <dd> |
682 | </dd> |
|
|
683 | <dd> |
610 | <pre> |
684 | <pre> |
611 | URxvt*color8: #000054 |
685 | URxvt.color8: #000054 |
612 | URxvt*color9: #FF0054 |
686 | URxvt.color9: #FF0054 |
613 | URxvt*color10: #00FF54 |
687 | URxvt.color10: #00FF54 |
614 | URxvt*color11: #FFFF54 |
688 | URxvt.color11: #FFFF54 |
615 | URxvt*color12: #0000FF |
689 | URxvt.color12: #0000FF |
616 | URxvt*color13: #FF00FF |
690 | URxvt.color13: #FF00FF |
617 | URxvt*color14: #00FFFF |
691 | URxvt.color14: #00FFFF |
618 | URxvt*color15: #FFFFFF</pre> |
692 | URxvt.color15: #FFFFFF</pre> |
619 | </dd> |
|
|
620 | <dd> |
693 | </dd> |
|
|
694 | <dd> |
621 | <p>And here is a more complete set of non-standard colors described as |
695 | <p>And here is a more complete set of non-standard colors described (not by |
622 | ``pretty girly'':</p> |
696 | me) as ``pretty girly''.</p> |
623 | </dd> |
697 | </dd> |
624 | <dd> |
698 | <dd> |
625 | <pre> |
699 | <pre> |
626 | URxvt.cursorColor: #dc74d1 |
700 | URxvt.cursorColor: #dc74d1 |
627 | URxvt.pointerColor: #dc74d1 |
701 | URxvt.pointerColor: #dc74d1 |
… | |
… | |
641 | URxvt.color14: #73f7ff |
715 | URxvt.color14: #73f7ff |
642 | URxvt.color7: #e1dddd |
716 | URxvt.color7: #e1dddd |
643 | URxvt.color15: #e1dddd</pre> |
717 | URxvt.color15: #e1dddd</pre> |
644 | </dd> |
718 | </dd> |
645 | <p></p> |
719 | <p></p> |
|
|
720 | <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 /> |
|
|
721 | </dt> |
|
|
722 | <dd> |
|
|
723 | Despite it's name, rxvtd is not a real daemon, but more like a |
|
|
724 | server that answers rxvtc's requests, so it doesn't background |
|
|
725 | itself. |
|
|
726 | </dd> |
|
|
727 | <dd> |
|
|
728 | <p>To ensure rxvtd is listening on it's socket, you can use the |
|
|
729 | following method to wait for the startup message before continuing:</p> |
|
|
730 | </dd> |
|
|
731 | <dd> |
|
|
732 | <pre> |
|
|
733 | { rxvtd & } | read</pre> |
|
|
734 | </dd> |
|
|
735 | <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 /> |
736 | <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> |
737 | </dt> |
648 | <dd> |
738 | <dd> |
649 | Assuming that the physical Backspace key corresponds to the |
739 | Assuming that the physical Backspace key corresponds to the |
650 | BackSpace keysym (not likely for Linux ... see the following |
740 | BackSpace keysym (not likely for Linux ... see the following |
… | |
… | |
677 | # use Backspace = ^? |
767 | # use Backspace = ^? |
678 | $ stty erase ^? |
768 | $ stty erase ^? |
679 | $ rxvt</pre> |
769 | $ rxvt</pre> |
680 | </dd> |
770 | </dd> |
681 | <dd> |
771 | <dd> |
682 | <p>Toggle with ``ESC[36h'' / ``ESC[36l'' as documented in rxvt(7).</p> |
772 | <p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code> as documented in rxvt(7).</p> |
683 | </dd> |
773 | </dd> |
684 | <dd> |
774 | <dd> |
685 | <p>For an existing rxvt-unicode:</p> |
775 | <p>For an existing rxvt-unicode:</p> |
686 | </dd> |
776 | </dd> |
687 | <dd> |
777 | <dd> |
… | |
… | |
703 | </dd> |
793 | </dd> |
704 | <dd> |
794 | <dd> |
705 | <p>The Delete key is a another casualty of the ill-defined Backspace problem. |
795 | <p>The Delete key is a another casualty of the ill-defined Backspace problem. |
706 | To avoid confusion between the Backspace and Delete keys, the Delete |
796 | To avoid confusion between the Backspace and Delete keys, the Delete |
707 | key has been assigned an escape sequence to match the vt100 for Execute |
797 | key has been assigned an escape sequence to match the vt100 for Execute |
708 | (ESC[3~) and is in the supplied termcap/terminfo.</p> |
798 | (<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p> |
709 | </dd> |
799 | </dd> |
710 | <dd> |
800 | <dd> |
711 | <p>Some other Backspace problems:</p> |
801 | <p>Some other Backspace problems:</p> |
712 | </dd> |
802 | </dd> |
713 | <dd> |
803 | <dd> |
… | |
… | |
725 | There are some compile-time selections available via configure. Unless |
815 | There are some compile-time selections available via configure. Unless |
726 | you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can |
816 | you have run ``configure'' with the <a href="#item__2d_2ddisable_2dresources"><code>--disable-resources</code></a> option you can |
727 | use the `keysym' resource to alter the keystrings associated with keysyms. |
817 | use the `keysym' resource to alter the keystrings associated with keysyms. |
728 | </dd> |
818 | </dd> |
729 | <dd> |
819 | <dd> |
730 | <p>Here's an example for a URxvt session started using `rxvt -name URxvt'</p> |
820 | <p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p> |
731 | </dd> |
|
|
732 | <dd> |
821 | </dd> |
|
|
822 | <dd> |
733 | <pre> |
823 | <pre> |
734 | URxvt.keysym.Home: \e[1~ |
824 | URxvt.keysym.Home: \033[1~ |
735 | URxvt.keysym.End: \e[4~ |
825 | URxvt.keysym.End: \033[4~ |
736 | URxvt.keysym.C-apostrophe: \e<C-'> |
826 | URxvt.keysym.C-apostrophe: \033<C-'> |
737 | URxvt.keysym.C-slash: \e<C-/> |
827 | URxvt.keysym.C-slash: \033<C-/> |
738 | URxvt.keysym.C-semicolon: \e<C-;> |
828 | URxvt.keysym.C-semicolon: \033<C-;> |
739 | URxvt.keysym.C-grave: \e<C-`> |
829 | URxvt.keysym.C-grave: \033<C-`> |
740 | URxvt.keysym.C-comma: \e<C-,> |
830 | URxvt.keysym.C-comma: \033<C-,> |
741 | URxvt.keysym.C-period: \e<C-.> |
831 | URxvt.keysym.C-period: \033<C-.> |
742 | URxvt.keysym.C-0x60: \e<C-`> |
832 | URxvt.keysym.C-0x60: \033<C-`> |
743 | URxvt.keysym.C-Tab: \e<C-Tab> |
833 | URxvt.keysym.C-Tab: \033<C-Tab> |
744 | URxvt.keysym.C-Return: \e<C-Return> |
834 | URxvt.keysym.C-Return: \033<C-Return> |
745 | URxvt.keysym.S-Return: \e<S-Return> |
835 | URxvt.keysym.S-Return: \033<S-Return> |
746 | URxvt.keysym.S-space: \e<S-Space> |
836 | URxvt.keysym.S-space: \033<S-Space> |
747 | URxvt.keysym.M-Up: \e<M-Up> |
837 | URxvt.keysym.M-Up: \033<M-Up> |
748 | URxvt.keysym.M-Down: \e<M-Down> |
838 | URxvt.keysym.M-Down: \033<M-Down> |
749 | URxvt.keysym.M-Left: \e<M-Left> |
839 | URxvt.keysym.M-Left: \033<M-Left> |
750 | URxvt.keysym.M-Right: \e<M-Right> |
840 | URxvt.keysym.M-Right: \033<M-Right> |
751 | URxvt.keysym.M-C-0: list \e<M-C- 0123456789 > |
841 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
752 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
842 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
753 | URxvt.keysym.F12: proto:\033]701;zh_CN.GBK\007</pre> |
843 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007</pre> |
754 | </dd> |
844 | </dd> |
755 | <dd> |
845 | <dd> |
756 | <p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p> |
846 | <p>See some more examples in the documentation for the <strong>keysym</strong> resource.</p> |
757 | </dd> |
847 | </dd> |
758 | <p></p> |
848 | <p></p> |
… | |
… | |
772 | <dd> |
862 | <dd> |
773 | <p>Rather than have rxvt-unicode try to accommodate all the various possible |
863 | <p>Rather than have rxvt-unicode try to accommodate all the various possible |
774 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
864 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
775 | required for your particular machine.</p> |
865 | required for your particular machine.</p> |
776 | </dd> |
866 | </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? |
867 | <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? |
778 | I need this to decide about setting colors etc.</a></strong><br /> |
868 | I need this to decide about setting colors etc.</a></strong><br /> |
779 | </dt> |
869 | </dt> |
780 | <dd> |
870 | <dd> |
781 | rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can |
871 | rxvt and rxvt-unicode always export the variable ``COLORTERM'', so you can |
782 | check and see if that is set. Note that several programs, JED, slrn, |
872 | check and see if that is set. Note that several programs, JED, slrn, |
… | |
… | |
831 | </dd> |
921 | </dd> |
832 | <p></p></dl> |
922 | <p></p></dl> |
833 | <p> |
923 | <p> |
834 | </p> |
924 | </p> |
835 | <hr /> |
925 | <hr /> |
836 | <h1><a name="synopsis">SYNOPSIS</a></h1> |
926 | <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" Mincho"</pre> |
|
|
840 | <pre> |
|
|
841 | # change the locale and tell rxvt-unicode about it |
|
|
842 | export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"</pre> |
|
|
843 | <pre> |
|
|
844 | # set window title |
|
|
845 | printf '\33]2;%s\007' "new window title"</pre> |
|
|
846 | <p> |
927 | <p> |
847 | </p> |
928 | </p> |
848 | <hr /> |
929 | <hr /> |
849 | <h1><a name="description">DESCRIPTION</a></h1> |
930 | <h1><a name="description">DESCRIPTION</a></h1> |
850 | <p>The rest of this document describes various technical aspects of |
931 | <p>The rest of this document describes various technical aspects of |
… | |
… | |
852 | followed by menu and pixmap support and last by a description of all |
933 | followed by menu and pixmap support and last by a description of all |
853 | features selectable at <code>configure</code> time.</p> |
934 | features selectable at <code>configure</code> time.</p> |
854 | <p> |
935 | <p> |
855 | </p> |
936 | </p> |
856 | <hr /> |
937 | <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> |
938 | <h1><a name="definitions">Definitions</a></h1> |
862 | <dl> |
939 | <dl> |
863 | <dt><strong><a name="item_c"><strong><code>c</code> </strong>></a></strong><br /> |
940 | <dt><strong><a name="item_c"><strong><code>c</code> </strong>></a></strong><br /> |
864 | </dt> |
941 | </dt> |
865 | <dd> |
942 | <dd> |
… | |
… | |
1045 | </dd> |
1122 | </dd> |
1046 | <p></p> |
1123 | <p></p> |
1047 | <dt><strong><a name="item_esc_z"><strong><code>ESC Z</code> </strong>></a></strong><br /> |
1124 | <dt><strong><a name="item_esc_z"><strong><code>ESC Z</code> </strong>></a></strong><br /> |
1048 | </dt> |
1125 | </dt> |
1049 | <dd> |
1126 | <dd> |
1050 | Obsolete form of returns: <strong><code>ESC[?1;2C</code> </strong>> <em>rxvt-unicode compile-time option</em> |
1127 | Obsolete form of returns: <strong><code>ESC [ ? 1 ; 2 C</code> </strong>> <em>rxvt-unicode compile-time option</em> |
1051 | </dd> |
1128 | </dd> |
1052 | <p></p> |
1129 | <p></p> |
1053 | <dt><strong><a name="item_esc_c"><strong><code>ESC c</code> </strong>></a></strong><br /> |
1130 | <dt><strong><a name="item_esc_c"><strong><code>ESC c</code> </strong>></a></strong><br /> |
1054 | </dt> |
1131 | </dt> |
1055 | <dd> |
1132 | <dd> |
… | |
… | |
1066 | </dt> |
1143 | </dt> |
1067 | <dd> |
1144 | <dd> |
1068 | Invoke the G3 Character Set (LS3) |
1145 | Invoke the G3 Character Set (LS3) |
1069 | </dd> |
1146 | </dd> |
1070 | <p></p> |
1147 | <p></p> |
1071 | <dt><strong><strong><code>ESC</code> ( C</strong> >></strong><br /> |
1148 | <dt><strong><strong><code>ESC ( C</code> </strong>></strong><br /> |
1072 | </dt> |
1149 | </dt> |
1073 | <dd> |
1150 | <dd> |
1074 | Designate G0 Character Set (ISO 2022), see below for values of <a href="#item_c"><code>C</code></a>. |
1151 | Designate G0 Character Set (ISO 2022), see below for values of <a href="#item_c"><code>C</code></a>. |
1075 | </dd> |
1152 | </dd> |
1076 | <p></p> |
1153 | <p></p> |
1077 | <dt><strong><a name="item_esc__29_c_3e"><strong><a href="#item_esc"><code>ESC</code></a> ) C</strong> >></a></strong><br /> |
1154 | <dt><strong><a name="item_esc__29_c"><strong><code>ESC ) C</code> </strong>></a></strong><br /> |
1078 | </dt> |
1155 | </dt> |
1079 | <dd> |
1156 | <dd> |
1080 | Designate G1 Character Set (ISO 2022), see below for values of <a href="#item_c"><code>C</code></a>. |
1157 | Designate G1 Character Set (ISO 2022), see below for values of <a href="#item_c"><code>C</code></a>. |
1081 | </dd> |
1158 | </dd> |
1082 | <p></p> |
1159 | <p></p> |
… | |
… | |
1257 | <dt><strong><a name="item_esc__5b_ps_c"><strong><code>ESC [ Ps c</code> </strong>></a></strong><br /> |
1334 | <dt><strong><a name="item_esc__5b_ps_c"><strong><code>ESC [ Ps c</code> </strong>></a></strong><br /> |
1258 | </dt> |
1335 | </dt> |
1259 | <dd> |
1336 | <dd> |
1260 | Send Device Attributes (DA) |
1337 | Send Device Attributes (DA) |
1261 | <strong><code>Ps = 0</code> </strong>> (or omitted): request attributes from terminal |
1338 | <strong><code>Ps = 0</code> </strong>> (or omitted): request attributes from terminal |
1262 | returns: <strong><code>ESC[?1;2c</code> </strong>> (``I am a VT100 with Advanced Video |
1339 | returns: <strong><code>ESC [ ? 1 ; 2 c</code> </strong>> (``I am a VT100 with Advanced Video |
1263 | Option'') |
1340 | Option'') |
1264 | </dd> |
1341 | </dd> |
1265 | <p></p> |
1342 | <p></p> |
1266 | <dt><strong><a name="item_esc__5b_ps_d"><strong><code>ESC [ Ps d</code> </strong>></a></strong><br /> |
1343 | <dt><strong><a name="item_esc__5b_ps_d"><strong><code>ESC [ Ps d</code> </strong>></a></strong><br /> |
1267 | </dt> |
1344 | </dt> |
… | |
… | |
1388 | </dd> |
1465 | </dd> |
1389 | <table> |
1466 | <table> |
1390 | <tr><td>Ps = 1</td><td>Deiconify (map) window</td></tr> |
1467 | <tr><td>Ps = 1</td><td>Deiconify (map) window</td></tr> |
1391 | <tr><td>Ps = 2</td><td>Iconify window</td></tr> |
1468 | <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> |
1469 | <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> |
1470 | <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> |
1471 | <tr><td>Ps = 5</td><td>Raise window</td></tr> |
1395 | <tr><td>Ps = 6</td><td>Lower window</td></tr> |
1472 | <tr><td>Ps = 6</td><td>Lower window</td></tr> |
1396 | <tr><td>Ps = 7</td><td>Refresh screen once</td></tr> |
1473 | <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> |
1474 | <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> |
1475 | <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> |
1476 | <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> |
1477 | <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> |
1478 | <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> |
1479 | <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> |
1480 | <tr><td>Ps = 20</td><td>Reports icon label (ESC ] L NAME \234)</td></tr> |
… | |
… | |
1890 | non-+<strong>NUL</strong> characters, the leading <strong>NUL</strong> is stripped off and the |
1967 | non-+<strong>NUL</strong> characters, the leading <strong>NUL</strong> is stripped off and the |
1891 | balance is sent back to rxvt.</p> |
1968 | balance is sent back to rxvt.</p> |
1892 | <p>As a convenience for the many Emacs-type editors, <em>action</em> may start |
1969 | <p>As a convenience for the many Emacs-type editors, <em>action</em> may start |
1893 | with <strong>M-</strong> (eg, <strong>M-$</strong> is equivalent to <strong>\E$</strong>) and a <strong>CR</strong> will be |
1970 | with <strong>M-</strong> (eg, <strong>M-$</strong> is equivalent to <strong>\E$</strong>) and a <strong>CR</strong> will be |
1894 | appended if missed from <strong>M-x</strong> commands.</p> |
1971 | appended 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 |
1972 | <p>As a convenience for issuing XTerm <strong>ESC ]</strong> sequences from a menubar (or |
1896 | quick arrow), a <strong>BEL</strong> (<strong>^G</strong>) will be appended if needed.</p> |
1973 | quick arrow), a <strong>BEL</strong> (<strong>^G</strong>) will be appended if needed.</p> |
1897 | <dl> |
1974 | <dl> |
1898 | <dt><strong><a name="item_for_example_2c">For example,</a></strong><br /> |
1975 | <dt><strong><a name="item_for_example_2c">For example,</a></strong><br /> |
1899 | </dt> |
1976 | </dt> |
1900 | <dd> |
1977 | <dd> |
… | |
… | |
2633 | <p></p> |
2710 | <p></p> |
2634 | <dt><strong><a name="item__2d_2denable_2dxgetdefault">--enable-xgetdefault</a></strong><br /> |
2711 | <dt><strong><a name="item__2d_2denable_2dxgetdefault">--enable-xgetdefault</a></strong><br /> |
2635 | </dt> |
2712 | </dt> |
2636 | <dd> |
2713 | <dd> |
2637 | Make resources checking via <code>XGetDefault()</code> instead of our small |
2714 | Make resources checking via <code>XGetDefault()</code> instead of our small |
2638 | version which only checks ~/.Xdefaults, or if that doesn't exist |
2715 | version which only checks ~/.Xdefaults, or if that doesn't exist then |
2639 | then ~/.Xresources. |
2716 | ~/.Xresources. |
|
|
2717 | </dd> |
|
|
2718 | <dd> |
|
|
2719 | <p>Please note that nowadays, things like XIM will automatically pull in and |
|
|
2720 | use the full X resource manager, so the overhead of using it might be very |
|
|
2721 | small, if nonexistant.</p> |
2640 | </dd> |
2722 | </dd> |
2641 | <p></p> |
2723 | <p></p> |
2642 | <dt><strong><a name="item__2d_2denable_2dstrings">--enable-strings</a></strong><br /> |
2724 | <dt><strong><a name="item__2d_2denable_2dstrings">--enable-strings</a></strong><br /> |
2643 | </dt> |
2725 | </dt> |
2644 | <dd> |
2726 | <dd> |
… | |
… | |
2675 | extra window properties (e.g. UTF-8 window names and PID) |
2757 | extra window properties (e.g. UTF-8 window names and PID) |
2676 | iso-14755-2 and -3, and visual feedback |
2758 | iso-14755-2 and -3, and visual feedback |
2677 | backindex and forwardindex escape sequence |
2759 | backindex and forwardindex escape sequence |
2678 | window op and locale change escape sequences |
2760 | window op and locale change escape sequences |
2679 | tripleclickwords |
2761 | tripleclickwords |
2680 | settable insecure mode</pre> |
2762 | settable insecure mode |
|
|
2763 | keysym remapping support</pre> |
2681 | </dd> |
2764 | </dd> |
2682 | <p></p> |
2765 | <p></p> |
2683 | <dt><strong><a name="item__2d_2denable_2diso14755">--enable-iso14755</a></strong><br /> |
2766 | <dt><strong><a name="item__2d_2denable_2diso14755">--enable-iso14755</a></strong><br /> |
2684 | </dt> |
2767 | </dt> |
2685 | <dd> |
2768 | <dd> |