… | |
… | |
236 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
236 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
237 | |
237 | |
238 | Then click on a window you want to make transparent. Replace C<0xc0000000> |
238 | Then click on a window you want to make transparent. Replace C<0xc0000000> |
239 | by other values to change the degree of opacity. If it doesn't work and |
239 | by other values to change the degree of opacity. If it doesn't work and |
240 | your server crashes, you got to keep the pieces. |
240 | your server crashes, you got to keep the pieces. |
241 | |
|
|
242 | =head3 Why do some chinese characters look so different than others? |
|
|
243 | |
|
|
244 | This is because there is a difference between script and language -- |
|
|
245 | rxvt-unicode does not know which language the text that is output is, |
|
|
246 | as it only knows the unicode character codes. If rxvt-unicode first |
|
|
247 | sees a japanese/chinese character, it might choose a japanese font for |
|
|
248 | display. Subsequent japanese characters will use that font. Now, many |
|
|
249 | chinese characters aren't represented in japanese fonts, so when the first |
|
|
250 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
251 | -- unfortunately at this point, it will still use the japanese font for |
|
|
252 | chinese characters that are also in the japanese font. |
|
|
253 | |
|
|
254 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
255 | list (see the previous question). The key is to view the font list as |
|
|
256 | a preference list: If you expect more japanese, list a japanese font |
|
|
257 | first. If you expect more chinese, put a chinese font first. |
|
|
258 | |
|
|
259 | In the future it might be possible to switch language preferences at |
|
|
260 | runtime (the internal data structure has no problem with using different |
|
|
261 | fonts for the same character at the same time, but no interface for this |
|
|
262 | has been designed yet). |
|
|
263 | |
|
|
264 | Until then, you might get away with switching fonts at runtime (see L<Can |
|
|
265 | I switch the fonts at runtime?> later in this document). |
|
|
266 | |
241 | |
267 | =head3 Why does rxvt-unicode sometimes leave pixel droppings? |
242 | =head3 Why does rxvt-unicode sometimes leave pixel droppings? |
268 | |
243 | |
269 | Most fonts were not designed for terminal use, which means that character |
244 | Most fonts were not designed for terminal use, which means that character |
270 | size varies a lot. A font that is otherwise fine for terminal use might |
245 | size varies a lot. A font that is otherwise fine for terminal use might |
… | |
… | |
412 | URxvt.color15: #e1dddd |
387 | URxvt.color15: #e1dddd |
413 | |
388 | |
414 | They have been described (not by me) as "pretty girly". |
389 | They have been described (not by me) as "pretty girly". |
415 | |
390 | |
416 | =head3 Why do some characters look so much different than others? |
391 | =head3 Why do some characters look so much different than others? |
417 | |
392 | |
418 | See next entry. |
393 | See next entry. |
419 | |
394 | |
420 | =head3 How does rxvt-unicode choose fonts? |
395 | =head3 How does rxvt-unicode choose fonts? |
421 | |
396 | |
422 | Most fonts do not contain the full range of Unicode, which is |
397 | Most fonts do not contain the full range of Unicode, which is |
423 | fine. Chances are that the font you (or the admin/package maintainer of |
398 | fine. Chances are that the font you (or the admin/package maintainer of |
424 | your system/os) have specified does not cover all the characters you want |
399 | your system/os) have specified does not cover all the characters you want |
425 | to display. |
400 | to display. |
426 | |
401 | |
427 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
402 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
428 | font. Often the result is fine, but sometimes the chosen font looks |
403 | font. Often the result is fine, but sometimes the chosen font looks |
429 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
404 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
430 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
405 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
431 | intelligence to detect that a specific glyph is wrong: it has to believe |
406 | intelligence to detect that a specific glyph is wrong: it has to believe |
432 | the font that the characters it claims to contain indeed look correct. |
407 | the font that the characters it claims to contain indeed look correct. |
433 | |
408 | |
434 | In that case, select a font of your taste and add it to the font list, |
409 | In that case, select a font of your taste and add it to the font list, |
435 | e.g.: |
410 | e.g.: |
436 | |
411 | |
437 | @@URXVT_NAME@@ -fn basefont,font2,font3... |
412 | @@URXVT_NAME@@ -fn basefont,font2,font3... |
438 | |
413 | |
439 | When rxvt-unicode sees a character, it will first look at the base |
414 | When rxvt-unicode sees a character, it will first look at the base |
440 | font. If the base font does not contain the character, it will go to the |
415 | font. If the base font does not contain the character, it will go to the |
441 | next font, and so on. Specifying your own fonts will also speed up this |
416 | next font, and so on. Specifying your own fonts will also speed up this |
442 | search and use less resources within rxvt-unicode and the X-server. |
417 | search and use less resources within rxvt-unicode and the X-server. |
443 | |
418 | |
444 | The only limitation is that none of the fonts may be larger than the base |
419 | The only limitation is that none of the fonts may be larger than the base |
445 | font, as the base font defines the terminal character cell size, which |
420 | font, as the base font defines the terminal character cell size, which |
446 | must be the same due to the way terminals work. |
421 | must be the same due to the way terminals work. |
|
|
422 | |
|
|
423 | =head3 Why do some chinese characters look so different than others? |
|
|
424 | |
|
|
425 | This is because there is a difference between script and language -- |
|
|
426 | rxvt-unicode does not know which language the text that is output is, |
|
|
427 | as it only knows the unicode character codes. If rxvt-unicode first |
|
|
428 | sees a japanese/chinese character, it might choose a japanese font for |
|
|
429 | display. Subsequent japanese characters will use that font. Now, many |
|
|
430 | chinese characters aren't represented in japanese fonts, so when the first |
|
|
431 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
432 | -- unfortunately at this point, it will still use the japanese font for |
|
|
433 | chinese characters that are also in the japanese font. |
|
|
434 | |
|
|
435 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
436 | list (see the previous question). The key is to view the font list as |
|
|
437 | a preference list: If you expect more japanese, list a japanese font |
|
|
438 | first. If you expect more chinese, put a chinese font first. |
|
|
439 | |
|
|
440 | In the future it might be possible to switch language preferences at |
|
|
441 | runtime (the internal data structure has no problem with using different |
|
|
442 | fonts for the same character at the same time, but no interface for this |
|
|
443 | has been designed yet). |
|
|
444 | |
|
|
445 | Until then, you might get away with switching fonts at runtime (see L<Can |
|
|
446 | I switch the fonts at runtime?> later in this document). |
447 | |
447 | |
448 | =head2 Keyboard, Mouse & User Interaction |
448 | =head2 Keyboard, Mouse & User Interaction |
449 | |
449 | |
450 | =head3 The new selection selects pieces that are too big, how can I select single words? |
450 | =head3 The new selection selects pieces that are too big, how can I select single words? |
451 | |
451 | |
… | |
… | |
1005 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
1005 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
1006 | to 8-bit encodings. |
1006 | to 8-bit encodings. |
1007 | |
1007 | |
1008 | =head1 RXVT-UNICODE TECHNICAL REFERENCE |
1008 | =head1 RXVT-UNICODE TECHNICAL REFERENCE |
1009 | |
1009 | |
1010 | =head1 DESCRIPTION |
|
|
1011 | |
|
|
1012 | The rest of this document describes various technical aspects of |
1010 | The rest of this document describes various technical aspects of |
1013 | B<rxvt-unicode>. First the description of supported command sequences, |
1011 | B<rxvt-unicode>. First the description of supported command sequences, |
1014 | followed by pixmap support and last by a description of all features |
1012 | followed by pixmap support and last by a description of all features |
1015 | selectable at C<configure> time. |
1013 | selectable at C<configure> time. |
1016 | |
1014 | |
1017 | =head1 Definitions |
1015 | =head2 Definitions |
1018 | |
1016 | |
1019 | =over 4 |
1017 | =over 4 |
1020 | |
1018 | |
1021 | =item B<< C<c> >> |
1019 | =item B<< C<c> >> |
1022 | |
1020 | |
… | |
… | |
1040 | |
1038 | |
1041 | A text parameter composed of printable characters. |
1039 | A text parameter composed of printable characters. |
1042 | |
1040 | |
1043 | =back |
1041 | =back |
1044 | |
1042 | |
1045 | =head1 Values |
1043 | =head2 Values |
1046 | |
1044 | |
1047 | =over 4 |
1045 | =over 4 |
1048 | |
1046 | |
1049 | =item B<< C<ENQ> >> |
1047 | =item B<< C<ENQ> >> |
1050 | |
1048 | |
… | |
… | |
1093 | |
1091 | |
1094 | Space Character |
1092 | Space Character |
1095 | |
1093 | |
1096 | =back |
1094 | =back |
1097 | |
1095 | |
1098 | =head1 Escape Sequences |
1096 | =head2 Escape Sequences |
1099 | |
1097 | |
1100 | =over 4 |
1098 | =over 4 |
1101 | |
1099 | |
1102 | =item B<< C<ESC # 8> >> |
1100 | =item B<< C<ESC # 8> >> |
1103 | |
1101 | |
… | |
… | |
1201 | |
1199 | |
1202 | =back |
1200 | =back |
1203 | |
1201 | |
1204 | X<CSI> |
1202 | X<CSI> |
1205 | |
1203 | |
1206 | =head1 CSI (Command Sequence Introducer) Sequences |
1204 | =head2 CSI (Command Sequence Introducer) Sequences |
1207 | |
1205 | |
1208 | =over 4 |
1206 | =over 4 |
1209 | |
1207 | |
1210 | =item B<< C<ESC [ Ps @> >> |
1208 | =item B<< C<ESC [ Ps @> >> |
1211 | |
1209 | |
… | |
… | |
1481 | |
1479 | |
1482 | =back |
1480 | =back |
1483 | |
1481 | |
1484 | X<PrivateModes> |
1482 | X<PrivateModes> |
1485 | |
1483 | |
1486 | =head1 DEC Private Modes |
1484 | =head2 DEC Private Modes |
1487 | |
1485 | |
1488 | =over 4 |
1486 | =over 4 |
1489 | |
1487 | |
1490 | =item B<< C<ESC [ ? Pm h> >> |
1488 | =item B<< C<ESC [ ? Pm h> >> |
1491 | |
1489 | |
… | |
… | |
1755 | |
1753 | |
1756 | =back |
1754 | =back |
1757 | |
1755 | |
1758 | X<XTerm> |
1756 | X<XTerm> |
1759 | |
1757 | |
1760 | =head1 XTerm Operating System Commands |
1758 | =head2 XTerm Operating System Commands |
1761 | |
1759 | |
1762 | =over 4 |
1760 | =over 4 |
1763 | |
1761 | |
1764 | =item B<< C<ESC ] Ps;Pt ST> >> |
1762 | =item B<< C<ESC ] Ps;Pt ST> >> |
1765 | |
1763 | |
… | |
… | |
1802 | B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl). |
1800 | B<< C<Ps = 777> >> Call the perl extension with the given string, which should be of the form C<extension:parameters> (Compile perl). |
1803 | |
1801 | |
1804 | =end table |
1802 | =end table |
1805 | |
1803 | |
1806 | =back |
1804 | =back |
1807 | |
|
|
1808 | X<XPM> |
|
|
1809 | |
1805 | |
1810 | =head1 XPM |
1806 | =head1 XPM |
1811 | |
1807 | |
1812 | For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value |
1808 | For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value |
1813 | of B<< C<Pt> >> can be the name of the background pixmap followed by a |
1809 | of B<< C<Pt> >> can be the name of the background pixmap followed by a |