1 | =head1 NAME |
1 | =head1 NAME |
2 | |
2 | |
3 | RXVT REFERENCE - FAQ, command sequences and other background information |
3 | RXVT REFERENCE - FAQ, command sequences and other background information |
4 | |
4 | |
|
|
5 | =head1 SYNOPSIS |
|
|
6 | |
|
|
7 | # set a new font set |
|
|
8 | printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho" |
|
|
9 | |
|
|
10 | # change the locale and tell rxvt-unicode about it |
|
|
11 | export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007" |
|
|
12 | |
|
|
13 | # set window title |
|
|
14 | printf '\33]2;%s\007' "new window title" |
|
|
15 | |
|
|
16 | =head1 DESCRIPTION |
|
|
17 | |
|
|
18 | This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting |
|
|
19 | all escape sequences, and other background information. |
|
|
20 | |
|
|
21 | The newest version of this document is |
|
|
22 | also available on the World Wide Web at |
|
|
23 | L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>. |
|
|
24 | |
5 | =head1 FREQUENTLY ASKED QUESTIONS |
25 | =head1 FREQUENTLY ASKED QUESTIONS |
6 | |
26 | |
7 | =over 4 |
27 | =over 4 |
8 | |
28 | |
9 | =item How do I know which rxvt-unicode version I'm using? |
29 | =item How do I know which rxvt-unicode version I'm using? |
10 | |
30 | |
11 | The version number is displayed with the usage (-h). Also the escape |
31 | The version number is displayed with the usage (-h). Also the escape |
12 | sequence C<ESC[8n> sets the window title to the version number. |
32 | sequence C<ESC [ 8 n> sets the window title to the version number. |
|
|
33 | |
|
|
34 | =item I am using Debian GNU/Linux and have a problem... |
|
|
35 | |
|
|
36 | The Debian GNU/Linux package of rxvt-unicode contains large patches that |
|
|
37 | considerably change the behaviour of rxvt-unicode. Before reporting a |
|
|
38 | bug to the original rxvt-unicode author please download and install the |
|
|
39 | genuine version (L<http://software.schmorp.de#rxvt-unicode>) and try to |
|
|
40 | reproduce the problem. If you cannot, chances are that the problems are |
|
|
41 | specific to Debian GNU/Linux, in which case it should be reported via the |
|
|
42 | Debian Bug Tracking System (use C<reportbug> to report the bug). |
|
|
43 | |
|
|
44 | For other problems that also affect the Debian package, you can and |
|
|
45 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
46 | bug in the Debian version and it serves as a reminder for other users that |
|
|
47 | might encounter the same issue. |
13 | |
48 | |
14 | =item When I log-in to another system it tells me about missing terminfo data? |
49 | =item When I log-in to another system it tells me about missing terminfo data? |
15 | |
50 | |
16 | The terminal description used by rxvt-unicode is not as widely available |
51 | The terminal description used by rxvt-unicode is not as widely available |
17 | as that for xterm, or even rxvt (for which the same problem often arises). |
52 | as that for xterm, or even rxvt (for which the same problem often arises). |
… | |
… | |
28 | C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of |
63 | C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of |
29 | problems arising, which includes wrong keymapping, less and different |
64 | problems arising, which includes wrong keymapping, less and different |
30 | colours and some refresh errors in fullscreen applications. It's a nice |
65 | colours and some refresh errors in fullscreen applications. It's a nice |
31 | quick-and-dirty workaround for rare cases, though. |
66 | quick-and-dirty workaround for rare cases, though. |
32 | |
67 | |
33 | If you always want to do this you can either recompile rxvt-unicode with |
68 | If you always want to do this (and are fine with the consequences) you |
34 | the desired TERM value or use a resource to set it: |
69 | can either recompile rxvt-unicode with the desired TERM value or use a |
|
|
70 | resource to set it: |
35 | |
71 | |
36 | URxvt.termName: rxvt |
72 | URxvt.termName: rxvt |
37 | |
73 | |
38 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
74 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
39 | the rxvt terminfo file with the rxvt-unicode one. |
75 | the rxvt terminfo file with the rxvt-unicode one. |
40 | |
76 | |
|
|
77 | =item C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
|
|
78 | |
41 | =item I need a termcap file entry. |
79 | =item I need a termcap file entry. |
|
|
80 | |
|
|
81 | One reason you might want this is that some distributions or operating |
|
|
82 | systems still compile some programs using the long-obsoleted termcap |
|
|
83 | (Fedora Core's bash is one example) and rely on a termcap entry for |
|
|
84 | C<rxvt-unicode>. |
42 | |
85 | |
43 | You could use rxvt's termcap entry with resonable results in many cases. |
86 | You could use rxvt's termcap entry with resonable results in many cases. |
44 | You can also create a termcap entry by using terminfo's infocmp program |
87 | You can also create a termcap entry by using terminfo's infocmp program |
45 | like this: |
88 | like this: |
46 | |
89 | |
47 | infocmp -C rxvt-unicode |
90 | infocmp -C rxvt-unicode |
48 | |
91 | |
49 | OR you could this termcap entry: |
92 | Or you could use this termcap entry, generated by the command above: |
50 | |
93 | |
51 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
94 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
52 | :am:bw:eo:km:mi:ms:xn:xo:\ |
95 | :am:bw:eo:km:mi:ms:xn:xo:\ |
53 | :co#80:it#8:li#24:\ |
96 | :co#80:it#8:li#24:\ |
54 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
97 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
… | |
… | |
96 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
139 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
97 | file, so you will need to install it on your own (See the question B<When |
140 | file, so you will need to install it on your own (See the question B<When |
98 | I log-in to another system it tells me about missing terminfo data?> on |
141 | I log-in to another system it tells me about missing terminfo data?> on |
99 | how to do this). |
142 | how to do this). |
100 | |
143 | |
|
|
144 | =item My numerical keypad acts weird and generates differing output? |
|
|
145 | |
|
|
146 | Some Debian GNUL/Linux users seem to have this problem, although no |
|
|
147 | specific details were reported so far. It is possible that this is caused |
|
|
148 | by the wrong C<TERM> setting, although the details of wether and how |
|
|
149 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
|
|
150 | keymap. See the answer to the previous question, and please report if that |
|
|
151 | helped. |
|
|
152 | |
101 | =item Rxvt-unicode does not seem to understand the selected encoding? |
153 | =item Rxvt-unicode does not seem to understand the selected encoding? |
102 | |
154 | |
103 | =item Unicode does not seem to work? |
155 | =item Unicode does not seem to work? |
104 | |
156 | |
105 | If you encounter strange problems like typing an accented character but |
157 | If you encounter strange problems like typing an accented character but |
… | |
… | |
107 | subtly garbled, then you should check your locale settings. |
159 | subtly garbled, then you should check your locale settings. |
108 | |
160 | |
109 | Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the |
161 | Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the |
110 | programs. Often rxvt-unicode is started in the C<C> locale, while the |
162 | programs. Often rxvt-unicode is started in the C<C> locale, while the |
111 | login script running within the rxvt-unicode window changes the locale to |
163 | login script running within the rxvt-unicode window changes the locale to |
112 | sth. else, e.h. C<en_GB.UTF-8>. Needless to say, this is not going to work. |
164 | something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work. |
113 | |
165 | |
114 | The best thing is to fix your startup environment, as you will likely run |
166 | The best thing is to fix your startup environment, as you will likely run |
115 | into other problems. If nothing works you can try this in your .profile. |
167 | into other problems. If nothing works you can try this in your .profile. |
116 | |
168 | |
117 | printf '\e]701;%s\007' "$LC_CTYPE" |
169 | printf '\e]701;%s\007' "$LC_CTYPE" |
118 | |
170 | |
119 | If this doesn't work, then maybe you use a C<LC_CTYPE> specification not |
171 | If this doesn't work, then maybe you use a C<LC_CTYPE> specification not |
120 | supported on your systems. Some systems have a C<locale> command which |
172 | supported on your systems. Some systems have a C<locale> command which |
121 | displays this. If it displays sth. like: |
173 | displays this (also, C<perl -e0> can be used to check locale settings, as |
|
|
174 | it will complain loudly if it cannot set the locale). If it displays something |
|
|
175 | like: |
122 | |
176 | |
123 | locale: Cannot set LC_CTYPE to default locale: ... |
177 | locale: Cannot set LC_CTYPE to default locale: ... |
124 | |
178 | |
125 | Then the locale you specified is not supported on your system. |
179 | Then the locale you specified is not supported on your system. |
126 | |
180 | |
… | |
… | |
137 | your system/os) have specified does not cover all the characters you want |
191 | your system/os) have specified does not cover all the characters you want |
138 | to display. |
192 | to display. |
139 | |
193 | |
140 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
194 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
141 | font. Often the result is fine, but sometimes the chosen font looks |
195 | font. Often the result is fine, but sometimes the chosen font looks |
142 | bad. Many fonts have totally strange characters that don't resemble the |
196 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
143 | correct glyph at all, and rxvt-unicode lacks the artificial intelligence |
197 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
144 | to detect that a specific glyph is wrong: it has to believe the font that |
198 | intelligence to detect that a specific glyph is wrong: it has to believe |
145 | the characters it contains indeed look correct. |
199 | the font that the characters it claims to contain indeed look correct. |
146 | |
200 | |
147 | In that case, select a font of your taste and add it to the font list, |
201 | In that case, select a font of your taste and add it to the font list, |
148 | e.g.: |
202 | e.g.: |
149 | |
203 | |
150 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
204 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
… | |
… | |
152 | When rxvt-unicode sees a character, it will first look at the base |
206 | When rxvt-unicode sees a character, it will first look at the base |
153 | font. If the base font does not contain the character, it will go to the |
207 | font. If the base font does not contain the character, it will go to the |
154 | next font, and so on. Specifying your own fonts will also speed up this |
208 | next font, and so on. Specifying your own fonts will also speed up this |
155 | search and use less resources within rxvt-unicode and the X-server. |
209 | search and use less resources within rxvt-unicode and the X-server. |
156 | |
210 | |
157 | The only limitation is that all the fonts must not be larger than the base |
211 | The only limitation is that none of the fonts may be larger than the base |
158 | font, as the base font defines the principal cell size, which must be the |
212 | font, as the base font defines the terminal character cell size, which |
159 | same due to the way terminals work. |
213 | must be the same due to the way terminals work. |
160 | |
214 | |
161 | =item Why do some chinese characters look so different than others? |
215 | =item Why do some chinese characters look so different than others? |
162 | |
216 | |
163 | This is because there is a difference between script and language -- |
217 | This is because there is a difference between script and language -- |
164 | rxvt-unicode does not know which language the text that is output |
218 | rxvt-unicode does not know which language the text that is output is, |
165 | is, as it only knows the unicode character codes. If rxvt-unicode |
219 | as it only knows the unicode character codes. If rxvt-unicode first |
166 | first sees a japanese character, it might choose a japanese font for |
220 | sees a japanese/chinese character, it might choose a japanese font for |
167 | it. Subsequent japanese characters will take that font. Now, many chinese |
221 | display. Subsequent japanese characters will use that font. Now, many |
168 | characters aren't represented in japanese fonts, so when the first |
222 | chinese characters aren't represented in japanese fonts, so when the first |
169 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
223 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
170 | -- unfortunately at this point, it will still use the japanese font for |
224 | -- unfortunately at this point, it will still use the japanese font for |
171 | japanese characters that are also chinese. |
225 | chinese characters that are also in the japanese font. |
172 | |
226 | |
173 | The workaround is easy: just tag a chinese font at the end of your font |
227 | The workaround is easy: just tag a chinese font at the end of your font |
174 | list (see the previous question). The key is to view the font list as |
228 | list (see the previous question). The key is to view the font list as |
175 | a preference list: If you expect more japanese, list a japanese font |
229 | a preference list: If you expect more japanese, list a japanese font |
176 | first. If you expect more chinese, put a chinese font first. |
230 | first. If you expect more chinese, put a chinese font first. |
177 | |
231 | |
178 | In the future it might be possible to switch preferences at runtime (the |
232 | In the future it might be possible to switch language preferences at |
179 | internal data structure has no problem with using different fonts for |
233 | runtime (the internal data structure has no problem with using different |
180 | the same character at the same time, but no interface for this has been |
234 | fonts for the same character at the same time, but no interface for this |
181 | designed yet). |
235 | has been designed yet). |
|
|
236 | |
|
|
237 | Until then, you might get away with switching fonts at runtime (see L<Can |
|
|
238 | I switch the fonts at runtime?> later in this document). |
182 | |
239 | |
183 | =item Why does rxvt-unicode sometimes leave pixel droppings? |
240 | =item Why does rxvt-unicode sometimes leave pixel droppings? |
184 | |
241 | |
185 | Most fonts were not designed for terminal use, which means that character |
242 | Most fonts were not designed for terminal use, which means that character |
186 | size varies a lot. A font that is otherwise fine for terminal use might |
243 | size varies a lot. A font that is otherwise fine for terminal use might |
… | |
… | |
222 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
279 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
223 | character and so on. |
280 | character and so on. |
224 | |
281 | |
225 | =item How can I keep rxvt-unicode from using reverse video so much? |
282 | =item How can I keep rxvt-unicode from using reverse video so much? |
226 | |
283 | |
227 | First of all, make sure you are running with the right terminfo |
284 | First of all, make sure you are running with the right terminal settings |
228 | (C<urxvt>), which will get rid of most of these effects. Then make sure |
285 | (C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
229 | you have specified colours for italic and bold, as otherwise rxvt-unicode |
286 | make sure you have specified colours for italic and bold, as otherwise |
230 | might use reverse video to simulate the effect: |
287 | rxvt-unicode might use reverse video to simulate the effect: |
231 | |
288 | |
232 | URxvt*colorBD: white |
289 | URxvt.colorBD: white |
233 | URxvt*colorIT: green |
290 | URxvt.colorIT: green |
234 | |
291 | |
235 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
292 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
236 | |
293 | |
237 | For some unexplainable reason, some programs (i.e. irssi) assume a very |
294 | For some unexplainable reason, some rare programs assume a very weird |
238 | weird colour palette when confronted with a terminal with more than the |
295 | colour palette when confronted with a terminal with more than the standard |
239 | standard 8 colours (rxvt-unicode supports 88). The right fix is, of |
296 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
240 | course, to fix these programs not to assume non-ISO colours without very |
297 | these programs not to assume non-ISO colours without very good reasons. |
241 | good reasons. |
|
|
242 | |
298 | |
243 | In the meantime, you can either edit your C<urxvt> terminfo definition to |
299 | In the meantime, you can either edit your C<rxvt-unicode> terminfo |
244 | only claim 8 colour support or use C<TERM=rxvt>, which will fix colours |
300 | definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
245 | but keep you from using other rxvt-unicode features. |
301 | fix colours but keep you from using other rxvt-unicode features. |
246 | |
302 | |
247 | =item I am on FreeBSD and rxvt-unicode does not seem to work at all. |
303 | =item I am on FreeBSD and rxvt-unicode does not seem to work at all. |
248 | |
304 | |
249 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
305 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
250 | in your compile environment, or an implementation that implements it, |
306 | in your compile environment, or an implementation that implements it, |
251 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
307 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
252 | B<wchar_t> is represented as unicode. |
308 | B<wchar_t> is represented as unicode. |
253 | |
309 | |
254 | As you might have guessed, FreeBSD does neither define this symobl nor |
310 | As you might have guessed, FreeBSD does neither define this symobl nor |
255 | does it support it. Instead, it uses it's own internal representation of |
311 | does it support it. Instead, it uses it's own internal representation of |
256 | B<wchar_t>. This is, of course, completely legal. |
312 | B<wchar_t>. This is, of course, completely fine with respect to standards. |
257 | |
313 | |
258 | However, C<__STDC_ISO_10646__> is the only sane way to support |
314 | However, C<__STDC_ISO_10646__> is the only sane way to support |
259 | multi-language apps in an OS, as using a locale-dependent (and |
315 | multi-language apps in an OS, as using a locale-dependent (and |
260 | non-standardized) representation of B<wchar_t> makes it impossible to |
316 | non-standardized) representation of B<wchar_t> makes it impossible to |
261 | convert between B<wchar_t> (as used by X11 and your applications) and any |
317 | convert between B<wchar_t> (as used by X11 and your applications) and any |
… | |
… | |
269 | conversions (which is slow and unreliable in case the OS implements |
325 | conversions (which is slow and unreliable in case the OS implements |
270 | encodings slightly different than the terminal emulator). |
326 | encodings slightly different than the terminal emulator). |
271 | |
327 | |
272 | The rxvt-unicode author insists that the right way to fix this is in the |
328 | The rxvt-unicode author insists that the right way to fix this is in the |
273 | system libraries once and for all, instead of forcing every app to carry |
329 | system libraries once and for all, instead of forcing every app to carry |
274 | complete replacements. |
330 | complete replacements for them :) |
275 | |
331 | |
276 | =item How does rxvt-unicode determine the encoding to use? |
332 | =item How does rxvt-unicode determine the encoding to use? |
277 | |
333 | |
278 | =item Is there an option to switch encodings? |
334 | =item Is there an option to switch encodings? |
279 | |
335 | |
… | |
… | |
281 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
337 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
282 | UTF-8 or any other encodings with respect to terminal I/O. |
338 | UTF-8 or any other encodings with respect to terminal I/O. |
283 | |
339 | |
284 | The reasons is that there exists a perfectly fine mechanism for selecting |
340 | The reasons is that there exists a perfectly fine mechanism for selecting |
285 | the encoding, doing I/O and (most important) communicating this to all |
341 | the encoding, doing I/O and (most important) communicating this to all |
286 | applications so everybody agrees on character properties such as width and |
342 | applications so everybody agrees on character properties such as width |
287 | code number. This mechanism is the I<locale>. |
343 | and code number. This mechanism is the I<locale>. Applications not using |
|
|
344 | that info will have problems (for example, C<xterm> gets the width of |
|
|
345 | characters wrong as it uses it's own, locale-independent table under all |
|
|
346 | locales). |
288 | |
347 | |
289 | Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All |
348 | Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All |
290 | programs doing the same (that is, most) will automatically agree in the |
349 | programs doing the same (that is, most) will automatically agree in the |
291 | interpretation of characters. |
350 | interpretation of characters. |
292 | |
351 | |
… | |
… | |
299 | C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms |
358 | C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms |
300 | (i.e. C<de> or C<german>) are also common. |
359 | (i.e. C<de> or C<german>) are also common. |
301 | |
360 | |
302 | Rxvt-unicode ignores all other locale categories, and except for |
361 | Rxvt-unicode ignores all other locale categories, and except for |
303 | the encoding, ignores country or language-specific settings, |
362 | the encoding, ignores country or language-specific settings, |
304 | i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the same for rxvt-unicode. |
363 | i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to |
|
|
364 | rxvt-unicode. |
305 | |
365 | |
306 | If you want to use a specific encoding you have to make sure you start |
366 | If you want to use a specific encoding you have to make sure you start |
307 | rxvt-unicode with the correct C<LC_CTYPE> category. |
367 | rxvt-unicode with the correct C<LC_CTYPE> category. |
308 | |
368 | |
309 | =item Can I switch locales at runtime? |
369 | =item Can I switch locales at runtime? |
310 | |
370 | |
311 | Yes, using an escape sequence. Try sth. like this, which sets |
371 | Yes, using an escape sequence. Try something like this, which sets |
312 | rxvt-unicode's idea of C<LC_CTYPE>. |
372 | rxvt-unicode's idea of C<LC_CTYPE>. |
313 | |
373 | |
314 | printf '\e]701;%s\007' ja_JP.SJIS |
374 | printf '\e]701;%s\007' ja_JP.SJIS |
315 | |
375 | |
316 | See also the previous question. |
376 | See also the previous answer. |
317 | |
377 | |
318 | Sometimes this capability is rather handy when you want to work in one |
378 | Sometimes this capability is rather handy when you want to work in |
319 | locale (e.g. C<de_DE.UTF-8>) but some programs don't support UTF-8. For |
379 | one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it |
320 | example, I use this script to start C<xjdic>, which first switches to a |
380 | (e.g. UTF-8). For example, I use this script to start C<xjdic>, which |
321 | locale supported by xjdic and back later: |
381 | first switches to a locale supported by xjdic and back later: |
322 | |
382 | |
323 | printf '\e]701;%s\007' ja_JP.SJIS |
383 | printf '\e]701;%s\007' ja_JP.SJIS |
324 | xjdic -js |
384 | xjdic -js |
325 | printf '\e]701;%s\007' de_DE.UTF-8 |
385 | printf '\e]701;%s\007' de_DE.UTF-8 |
326 | |
386 | |
|
|
387 | You can also use xterm's C<luit> program, which usually works fine, except |
|
|
388 | for some locales where character width differs between program- and |
|
|
389 | rxvt-unicode-locales. |
|
|
390 | |
327 | =item Can I switch the fonts at runtime? |
391 | =item Can I switch the fonts at runtime? |
328 | |
392 | |
329 | Yes, using an escape sequence. Try sth. like this, which has the same |
393 | Yes, using an escape sequence. Try something like this, which has the same |
330 | effect as using the C<-fn> switch, and takes effect immediately: |
394 | effect as using the C<-fn> switch, and takes effect immediately: |
331 | |
395 | |
332 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
396 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
333 | |
397 | |
334 | This is useful if you e.g. work primarily with japanese (and prefer a |
398 | This is useful if you e.g. work primarily with japanese (and prefer a |
… | |
… | |
339 | |
403 | |
340 | =item Why do italic characters look as if clipped? |
404 | =item Why do italic characters look as if clipped? |
341 | |
405 | |
342 | Many fonts have difficulties with italic characters and hinting. For |
406 | Many fonts have difficulties with italic characters and hinting. For |
343 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
407 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
344 | Mono> completely fails in it's italic face. A workaround is to enable |
408 | Mono> completely fails in it's italic face. A workaround might be to |
345 | freetype autohinting, i.e. like this: |
409 | enable freetype autohinting, i.e. like this: |
346 | |
410 | |
347 | URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
411 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
348 | URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
412 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
349 | |
413 | |
350 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
414 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
351 | |
415 | |
352 | You can specify separate locales for the input method and the rest of the |
416 | You can specify separate locales for the input method and the rest of the |
353 | terminal, using the resource C<imlocale>: |
417 | terminal, using the resource C<imlocale>: |
… | |
… | |
359 | input characters outside C<EUC-JP> in a normal way then, as your input |
423 | input characters outside C<EUC-JP> in a normal way then, as your input |
360 | method limits you. |
424 | method limits you. |
361 | |
425 | |
362 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
426 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
363 | |
427 | |
364 | Rxvt-unicode tries to obey the rule of not charging you for sth. you |
428 | Rxvt-unicode tries to obey the rule of not charging you for something you |
365 | don't use. One thing you should try is to configure out all settings that |
429 | don't use. One thing you should try is to configure out all settings that |
366 | you don't need, for example, Xft support is a resource hog by design, |
430 | you don't need, for example, Xft support is a resource hog by design, |
367 | when used. Compiling it out ensures that no Xft font will be loaded |
431 | when used. Compiling it out ensures that no Xft font will be loaded |
368 | accidentally when rxvt-unicode tries to find a font for your characters. |
432 | accidentally when rxvt-unicode tries to find a font for your characters. |
369 | |
433 | |
… | |
… | |
422 | resources (or as long-options). |
486 | resources (or as long-options). |
423 | |
487 | |
424 | Here are values that are supposed to resemble a VGA screen, |
488 | Here are values that are supposed to resemble a VGA screen, |
425 | including the murky brown that passes for low-intensity yellow: |
489 | including the murky brown that passes for low-intensity yellow: |
426 | |
490 | |
427 | URxvt*color0: #000000 |
491 | URxvt.color0: #000000 |
428 | URxvt*color1: #A80000 |
492 | URxvt.color1: #A80000 |
429 | URxvt*color2: #00A800 |
493 | URxvt.color2: #00A800 |
430 | URxvt*color3: #A8A800 |
494 | URxvt.color3: #A8A800 |
431 | URxvt*color4: #0000A8 |
495 | URxvt.color4: #0000A8 |
432 | URxvt*color5: #A800A8 |
496 | URxvt.color5: #A800A8 |
433 | URxvt*color6: #00A8A8 |
497 | URxvt.color6: #00A8A8 |
434 | URxvt*color7: #A8A8A8 |
498 | URxvt.color7: #A8A8A8 |
435 | |
499 | |
436 | URxvt*color8: #000054 |
500 | URxvt.color8: #000054 |
437 | URxvt*color9: #FF0054 |
501 | URxvt.color9: #FF0054 |
438 | URxvt*color10: #00FF54 |
502 | URxvt.color10: #00FF54 |
439 | URxvt*color11: #FFFF54 |
503 | URxvt.color11: #FFFF54 |
440 | URxvt*color12: #0000FF |
504 | URxvt.color12: #0000FF |
441 | URxvt*color13: #FF00FF |
505 | URxvt.color13: #FF00FF |
442 | URxvt*color14: #00FFFF |
506 | URxvt.color14: #00FFFF |
443 | URxvt*color15: #FFFFFF |
507 | URxvt.color15: #FFFFFF |
444 | |
508 | |
445 | And here is a more complete set of non-standard colors described as |
509 | And here is a more complete set of non-standard colors described (not by |
446 | "pretty girly": |
510 | me) as "pretty girly". |
447 | |
511 | |
448 | URxvt.cursorColor: #dc74d1 |
512 | URxvt.cursorColor: #dc74d1 |
449 | URxvt.pointerColor: #dc74d1 |
513 | URxvt.pointerColor: #dc74d1 |
450 | URxvt.background: #0e0e0e |
514 | URxvt.background: #0e0e0e |
451 | URxvt.foreground: #4ad5e1 |
515 | URxvt.foreground: #4ad5e1 |
… | |
… | |
462 | URxvt.color6: #73f7ff |
526 | URxvt.color6: #73f7ff |
463 | URxvt.color14: #73f7ff |
527 | URxvt.color14: #73f7ff |
464 | URxvt.color7: #e1dddd |
528 | URxvt.color7: #e1dddd |
465 | URxvt.color15: #e1dddd |
529 | URxvt.color15: #e1dddd |
466 | |
530 | |
|
|
531 | =item How can I start @@RXVT_NAME@@d in a race-free way? |
|
|
532 | |
|
|
533 | Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a |
|
|
534 | server that answers @@RXVT_NAME@@c's requests, so it doesn't background |
|
|
535 | itself. |
|
|
536 | |
|
|
537 | To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the |
|
|
538 | following method to wait for the startup message before continuing: |
|
|
539 | |
|
|
540 | { @@RXVT_NAME@@d & } | read |
|
|
541 | |
467 | =item What's with the strange Backspace/Delete key behaviour? |
542 | =item What's with the strange Backspace/Delete key behaviour? |
468 | |
543 | |
469 | Assuming that the physical Backspace key corresponds to the |
544 | Assuming that the physical Backspace key corresponds to the |
470 | BackSpace keysym (not likely for Linux ... see the following |
545 | BackSpace keysym (not likely for Linux ... see the following |
471 | question) there are two standard values that can be used for |
546 | question) there are two standard values that can be used for |
… | |
… | |
489 | |
564 | |
490 | # use Backspace = ^? |
565 | # use Backspace = ^? |
491 | $ stty erase ^? |
566 | $ stty erase ^? |
492 | $ @@RXVT_NAME@@ |
567 | $ @@RXVT_NAME@@ |
493 | |
568 | |
494 | Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7). |
569 | Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7). |
495 | |
570 | |
496 | For an existing rxvt-unicode: |
571 | For an existing rxvt-unicode: |
497 | |
572 | |
498 | # use Backspace = ^H |
573 | # use Backspace = ^H |
499 | $ stty erase ^H |
574 | $ stty erase ^H |
… | |
… | |
508 | properly reflects that. |
583 | properly reflects that. |
509 | |
584 | |
510 | The Delete key is a another casualty of the ill-defined Backspace problem. |
585 | The Delete key is a another casualty of the ill-defined Backspace problem. |
511 | To avoid confusion between the Backspace and Delete keys, the Delete |
586 | To avoid confusion between the Backspace and Delete keys, the Delete |
512 | key has been assigned an escape sequence to match the vt100 for Execute |
587 | key has been assigned an escape sequence to match the vt100 for Execute |
513 | (ESC[3~) and is in the supplied termcap/terminfo. |
588 | (C<ESC [ 3 ~>) and is in the supplied termcap/terminfo. |
514 | |
589 | |
515 | Some other Backspace problems: |
590 | Some other Backspace problems: |
516 | |
591 | |
517 | some editors use termcap/terminfo, |
592 | some editors use termcap/terminfo, |
518 | some editors (vim I'm told) expect Backspace = ^H, |
593 | some editors (vim I'm told) expect Backspace = ^H, |
… | |
… | |
524 | |
599 | |
525 | There are some compile-time selections available via configure. Unless |
600 | There are some compile-time selections available via configure. Unless |
526 | you have run "configure" with the C<--disable-resources> option you can |
601 | you have run "configure" with the C<--disable-resources> option you can |
527 | use the `keysym' resource to alter the keystrings associated with keysyms. |
602 | use the `keysym' resource to alter the keystrings associated with keysyms. |
528 | |
603 | |
529 | Here's an example for a URxvt session started using `@@RXVT_NAME@@ -name URxvt' |
604 | Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt> |
530 | |
605 | |
531 | URxvt.keysym.Home: \033[1~ |
606 | URxvt.keysym.Home: \033[1~ |
532 | URxvt.keysym.End: \033[4~ |
607 | URxvt.keysym.End: \033[4~ |
533 | URxvt.keysym.C-apostrophe: \033<C-'> |
608 | URxvt.keysym.C-apostrophe: \033<C-'> |
534 | URxvt.keysym.C-slash: \033<C-/> |
609 | URxvt.keysym.C-slash: \033<C-/> |
… | |
… | |
564 | |
639 | |
565 | Rather than have rxvt-unicode try to accommodate all the various possible |
640 | Rather than have rxvt-unicode try to accommodate all the various possible |
566 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
641 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
567 | required for your particular machine. |
642 | required for your particular machine. |
568 | |
643 | |
569 | =item How do I distinguish if I'm running rxvt-unicode or a regular xterm? |
644 | =item How do I distinguish wether I'm running rxvt-unicode or a regular xterm? |
570 | I need this to decide about setting colors etc. |
645 | I need this to decide about setting colors etc. |
571 | |
646 | |
572 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
647 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
573 | check and see if that is set. Note that several programs, JED, slrn, |
648 | check and see if that is set. Note that several programs, JED, slrn, |
574 | Midnight Commander automatically check this variable to decide whether or |
649 | Midnight Commander automatically check this variable to decide whether or |
… | |
… | |
611 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
686 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
612 | interested in learning about new and exciting problems (but not FAQs :). |
687 | interested in learning about new and exciting problems (but not FAQs :). |
613 | |
688 | |
614 | =back |
689 | =back |
615 | |
690 | |
616 | =head1 SYNOPSIS |
691 | =head1 RXVT TECHNICAL REFERENCE |
617 | |
|
|
618 | # set a new font set |
|
|
619 | printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho" |
|
|
620 | |
|
|
621 | # change the locale and tell rxvt-unicode about it |
|
|
622 | export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007" |
|
|
623 | |
|
|
624 | # set window title |
|
|
625 | printf '\33]2;%s\007' "new window title" |
|
|
626 | |
692 | |
627 | =head1 DESCRIPTION |
693 | =head1 DESCRIPTION |
628 | |
694 | |
629 | The rest of this document describes various technical aspects of |
695 | The rest of this document describes various technical aspects of |
630 | B<rxvt-unicode>. First the description of supported command sequences, |
696 | B<rxvt-unicode>. First the description of supported command sequences, |
631 | followed by menu and pixmap support and last by a description of all |
697 | followed by menu and pixmap support and last by a description of all |
632 | features selectable at C<configure> time. |
698 | features selectable at C<configure> time. |
633 | |
699 | |
634 | =head1 RXVT TECHNICAL REFERENCE |
|
|
635 | |
|
|
636 | =head1 Definitions |
700 | =head1 Definitions |
637 | |
701 | |
638 | =over 4 |
702 | =over 4 |
639 | |
703 | |
640 | =item B<< C<c> >> |
704 | =item B<< C<c> >> |
… | |
… | |
768 | Single Shift Select of G3 Character Set (SS3): affects next character |
832 | Single Shift Select of G3 Character Set (SS3): affects next character |
769 | only I<unimplemented> |
833 | only I<unimplemented> |
770 | |
834 | |
771 | =item B<< C<ESC Z> >> |
835 | =item B<< C<ESC Z> >> |
772 | |
836 | |
773 | Obsolete form of returns: B<< C<ESC[?1;2C> >> I<rxvt-unicode compile-time option> |
837 | Obsolete form of returns: B<< C<ESC [ ? 1 ; 2 C> >> I<rxvt-unicode compile-time option> |
774 | |
838 | |
775 | =item B<< C<ESC c> >> |
839 | =item B<< C<ESC c> >> |
776 | |
840 | |
777 | Full reset (RIS) |
841 | Full reset (RIS) |
778 | |
842 | |
… | |
… | |
782 | |
846 | |
783 | =item B<< C<ESC o> >> |
847 | =item B<< C<ESC o> >> |
784 | |
848 | |
785 | Invoke the G3 Character Set (LS3) |
849 | Invoke the G3 Character Set (LS3) |
786 | |
850 | |
787 | =item B<< C<ESC> ( C> >> |
851 | =item B<< C<ESC ( C> >> |
788 | |
852 | |
789 | Designate G0 Character Set (ISO 2022), see below for values of C<C>. |
853 | Designate G0 Character Set (ISO 2022), see below for values of C<C>. |
790 | |
854 | |
791 | =item B<< C<ESC> ) C> >> |
855 | =item B<< C<ESC ) C> >> |
792 | |
856 | |
793 | Designate G1 Character Set (ISO 2022), see below for values of C<C>. |
857 | Designate G1 Character Set (ISO 2022), see below for values of C<C>. |
794 | |
858 | |
795 | =item B<< C<ESC * C> >> |
859 | =item B<< C<ESC * C> >> |
796 | |
860 | |
… | |
… | |
937 | |
1001 | |
938 | =item B<< C<ESC [ Ps c> >> |
1002 | =item B<< C<ESC [ Ps c> >> |
939 | |
1003 | |
940 | Send Device Attributes (DA) |
1004 | Send Device Attributes (DA) |
941 | B<< C<Ps = 0> >> (or omitted): request attributes from terminal |
1005 | B<< C<Ps = 0> >> (or omitted): request attributes from terminal |
942 | returns: B<< C<ESC[?1;2c> >> (``I am a VT100 with Advanced Video |
1006 | returns: B<< C<ESC [ ? 1 ; 2 c> >> (``I am a VT100 with Advanced Video |
943 | Option'') |
1007 | Option'') |
944 | |
1008 | |
945 | =item B<< C<ESC [ Ps d> >> |
1009 | =item B<< C<ESC [ Ps d> >> |
946 | |
1010 | |
947 | Cursor to Line B<< C<Ps> >> (VPA) |
1011 | Cursor to Line B<< C<Ps> >> (VPA) |
… | |
… | |
1077 | B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels |
1141 | B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels |
1078 | B<< C<Ps = 5> >> Raise window |
1142 | B<< C<Ps = 5> >> Raise window |
1079 | B<< C<Ps = 6> >> Lower window |
1143 | B<< C<Ps = 6> >> Lower window |
1080 | B<< C<Ps = 7> >> Refresh screen once |
1144 | B<< C<Ps = 7> >> Refresh screen once |
1081 | B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns |
1145 | B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns |
1082 | B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2> |
1146 | B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>) |
1083 | B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>) |
1147 | B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>) |
1084 | B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>) |
1148 | B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>) |
1085 | B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>) |
1149 | B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>) |
1086 | B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9> |
1150 | B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9> |
1087 | B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>) |
1151 | B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>) |
… | |
… | |
1631 | |
1695 | |
1632 | As a convenience for the many Emacs-type editors, I<action> may start |
1696 | As a convenience for the many Emacs-type editors, I<action> may start |
1633 | with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be |
1697 | with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be |
1634 | appended if missed from B<M-x> commands. |
1698 | appended if missed from B<M-x> commands. |
1635 | |
1699 | |
1636 | As a convenience for issuing XTerm B<ESC]> sequences from a menubar (or |
1700 | As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or |
1637 | quick arrow), a B<BEL> (B<^G>) will be appended if needed. |
1701 | quick arrow), a B<BEL> (B<^G>) will be appended if needed. |
1638 | |
1702 | |
1639 | =over 4 |
1703 | =over 4 |
1640 | |
1704 | |
1641 | =item For example, |
1705 | =item For example, |
… | |
… | |
2259 | Remove all resources checking. |
2323 | Remove all resources checking. |
2260 | |
2324 | |
2261 | =item --enable-xgetdefault |
2325 | =item --enable-xgetdefault |
2262 | |
2326 | |
2263 | Make resources checking via XGetDefault() instead of our small |
2327 | Make resources checking via XGetDefault() instead of our small |
2264 | version which only checks ~/.Xdefaults, or if that doesn't exist |
2328 | version which only checks ~/.Xdefaults, or if that doesn't exist then |
2265 | then ~/.Xresources. |
2329 | ~/.Xresources. |
|
|
2330 | |
|
|
2331 | Please note that nowadays, things like XIM will automatically pull in and |
|
|
2332 | use the full X resource manager, so the overhead of using it might be very |
|
|
2333 | small, if nonexistant. |
2266 | |
2334 | |
2267 | =item --enable-strings |
2335 | =item --enable-strings |
2268 | |
2336 | |
2269 | Add support for our possibly faster memset() function and other |
2337 | Add support for our possibly faster memset() function and other |
2270 | various routines, overriding your system's versions which may |
2338 | various routines, overriding your system's versions which may |
… | |
… | |
2293 | iso-14755-2 and -3, and visual feedback |
2361 | iso-14755-2 and -3, and visual feedback |
2294 | backindex and forwardindex escape sequence |
2362 | backindex and forwardindex escape sequence |
2295 | window op and locale change escape sequences |
2363 | window op and locale change escape sequences |
2296 | tripleclickwords |
2364 | tripleclickwords |
2297 | settable insecure mode |
2365 | settable insecure mode |
|
|
2366 | keysym remapping support |
2298 | |
2367 | |
2299 | =item --enable-iso14755 |
2368 | =item --enable-iso14755 |
2300 | |
2369 | |
2301 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2370 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2302 | F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by |
2371 | F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by |