… | |
… | |
153 | This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting |
153 | This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting |
154 | all escape sequences, and other background information. |
154 | all escape sequences, and other background information. |
155 | .PP |
155 | .PP |
156 | The newest version of this document is also available on the World Wide Web at |
156 | The newest version of this document is also available on the World Wide Web at |
157 | <http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>. |
157 | <http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>. |
158 | .SH "FREQUENTLY ASKED QUESTIONS" |
158 | .SH "RXVT\-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS" |
159 | .IX Header "FREQUENTLY ASKED QUESTIONS" |
159 | .IX Header "RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS" |
160 | .Sh "Meta, Features & Commandline Issues" |
160 | .Sh "Meta, Features & Commandline Issues" |
161 | .IX Subsection "Meta, Features & Commandline Issues" |
161 | .IX Subsection "Meta, Features & Commandline Issues" |
162 | \fIMy question isn't answered here, can I ask a human?\fR |
162 | \fIMy question isn't answered here, can I ask a human?\fR |
163 | .IX Subsection "My question isn't answered here, can I ask a human?" |
163 | .IX Subsection "My question isn't answered here, can I ask a human?" |
164 | .PP |
164 | .PP |
… | |
… | |
172 | Beginning with version 7.3, there is a perl extension that implements a |
172 | Beginning with version 7.3, there is a perl extension that implements a |
173 | simple tabbed terminal. It is installed by default, so any of these should |
173 | simple tabbed terminal. It is installed by default, so any of these should |
174 | give you tabs: |
174 | give you tabs: |
175 | .PP |
175 | .PP |
176 | .Vb 1 |
176 | .Vb 1 |
177 | \& @@RXVT_NAME@@ -pe tabbed |
177 | \& @@URXVT_NAME@@ -pe tabbed |
178 | .Ve |
178 | .Ve |
179 | .PP |
179 | .PP |
180 | .Vb 1 |
180 | .Vb 1 |
181 | \& URxvt.perl-ext-common: default,tabbed |
181 | \& URxvt.perl-ext-common: default,tabbed |
182 | .Ve |
182 | .Ve |
… | |
… | |
190 | \fIHow do I know which rxvt-unicode version I'm using?\fR |
190 | \fIHow do I know which rxvt-unicode version I'm using?\fR |
191 | .IX Subsection "How do I know which rxvt-unicode version I'm using?" |
191 | .IX Subsection "How do I know which rxvt-unicode version I'm using?" |
192 | .PP |
192 | .PP |
193 | The version number is displayed with the usage (\-h). Also the escape |
193 | The version number is displayed with the usage (\-h). Also the escape |
194 | sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When |
194 | sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When |
195 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
195 | using the @@URXVT_NAME@@c client, the version displayed is that of the |
196 | daemon. |
196 | daemon. |
197 | .PP |
197 | .PP |
198 | \fIRxvt-unicode uses gobs of memory, how can I reduce that?\fR |
198 | \fIRxvt-unicode uses gobs of memory, how can I reduce that?\fR |
199 | .IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
199 | .IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
200 | .PP |
200 | .PP |
… | |
… | |
209 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
209 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
210 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
210 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
211 | use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as |
211 | use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as |
212 | rxvt-unicode then uses 8 bytes per screen cell. |
212 | rxvt-unicode then uses 8 bytes per screen cell. |
213 | .PP |
213 | .PP |
214 | \fIHow can I start @@RXVT_NAME@@d in a race-free way?\fR |
214 | \fIHow can I start @@URXVT_NAME@@d in a race-free way?\fR |
215 | .IX Subsection "How can I start @@RXVT_NAME@@d in a race-free way?" |
215 | .IX Subsection "How can I start @@URXVT_NAME@@d in a race-free way?" |
216 | .PP |
216 | .PP |
217 | Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the |
217 | Try \f(CW\*(C`@@URXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@URXVT_NAME@@d to open the |
218 | display, create the listening socket and then fork. |
218 | display, create the listening socket and then fork. |
219 | .PP |
219 | .PP |
220 | \fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR |
220 | \fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR |
221 | .IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
221 | .IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
222 | .PP |
222 | .PP |
223 | rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can |
223 | The original rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", |
224 | check and see if that is set. Note that several programs, \s-1JED\s0, slrn, |
224 | so you can check and see if that is set. Note that several programs, \s-1JED\s0, |
225 | Midnight Commander automatically check this variable to decide whether or |
225 | slrn, Midnight Commander automatically check this variable to decide |
226 | not to use color. |
226 | whether or not to use color. |
227 | .PP |
227 | .PP |
228 | \fIHow do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?\fR |
228 | \fIHow do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?\fR |
229 | .IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?" |
229 | .IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?" |
230 | .PP |
230 | .PP |
231 | If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled |
231 | If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled |
… | |
… | |
275 | \& text data bss drs rss filename |
275 | \& text data bss drs rss filename |
276 | \& 98398 1664 24 15695 1824 rxvt --disable-everything |
276 | \& 98398 1664 24 15695 1824 rxvt --disable-everything |
277 | \& 188985 9048 66616 18222 1788 urxvt --disable-everything |
277 | \& 188985 9048 66616 18222 1788 urxvt --disable-everything |
278 | .Ve |
278 | .Ve |
279 | .PP |
279 | .PP |
280 | When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft |
280 | When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which \fIis\fR unfair, as this involves xft |
281 | and full locale/XIM support which are quite bloaty inside libX11 and my |
281 | and full locale/XIM support which are quite bloaty inside libX11 and my |
282 | libc), the two diverge, but not unreasnobaly so. |
282 | libc), the two diverge, but not unreasnobaly so. |
283 | .PP |
283 | .PP |
284 | .Vb 3 |
284 | .Vb 3 |
285 | \& text data bss drs rss filename |
285 | \& text data bss drs rss filename |
… | |
… | |
360 | .PP |
360 | .PP |
361 | 1. Use inheritPixmap: |
361 | 1. Use inheritPixmap: |
362 | .PP |
362 | .PP |
363 | .Vb 2 |
363 | .Vb 2 |
364 | \& Esetroot wallpaper.jpg |
364 | \& Esetroot wallpaper.jpg |
365 | \& @@RXVT_NAME@@ -ip -tint red -sh 40 |
365 | \& @@URXVT_NAME@@ -ip -tint red -sh 40 |
366 | .Ve |
366 | .Ve |
367 | .PP |
367 | .PP |
368 | That works. If you think it doesn't, you lack transparency and tinting |
368 | That works. If you think it doesn't, you lack transparency and tinting |
369 | support, or you are unable to read. |
369 | support, or you are unable to read. |
370 | .PP |
370 | .PP |
… | |
… | |
372 | to use effects other than tinting and shading: Just shade/tint/whatever |
372 | to use effects other than tinting and shading: Just shade/tint/whatever |
373 | your picture with gimp or any other tool: |
373 | your picture with gimp or any other tool: |
374 | .PP |
374 | .PP |
375 | .Vb 2 |
375 | .Vb 2 |
376 | \& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
376 | \& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
377 | \& @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background |
377 | \& @@URXVT_NAME@@ -pixmap background.xpm -pe automove-background |
378 | .Ve |
378 | .Ve |
379 | .PP |
379 | .PP |
380 | That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you |
380 | That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you |
381 | are unable to read. |
381 | are unable to read. |
382 | .PP |
382 | .PP |
383 | 3. Use an \s-1ARGB\s0 visual: |
383 | 3. Use an \s-1ARGB\s0 visual: |
384 | .PP |
384 | .PP |
385 | .Vb 1 |
385 | .Vb 1 |
386 | \& @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
386 | \& @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
387 | .Ve |
387 | .Ve |
388 | .PP |
388 | .PP |
389 | This requires \s-1XFT\s0 support, and the support of your X\-server. If that |
389 | This requires \s-1XFT\s0 support, and the support of your X\-server. If that |
390 | doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't |
390 | doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't |
391 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
391 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
… | |
… | |
400 | .Ve |
400 | .Ve |
401 | .PP |
401 | .PP |
402 | Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR |
402 | Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR |
403 | by other values to change the degree of opacity. If it doesn't work and |
403 | by other values to change the degree of opacity. If it doesn't work and |
404 | your server crashes, you got to keep the pieces. |
404 | your server crashes, you got to keep the pieces. |
405 | .PP |
|
|
406 | \fIWhy do some chinese characters look so different than others?\fR |
|
|
407 | .IX Subsection "Why do some chinese characters look so different than others?" |
|
|
408 | .PP |
|
|
409 | This is because there is a difference between script and language \*(-- |
|
|
410 | rxvt-unicode does not know which language the text that is output is, |
|
|
411 | as it only knows the unicode character codes. If rxvt-unicode first |
|
|
412 | sees a japanese/chinese character, it might choose a japanese font for |
|
|
413 | display. Subsequent japanese characters will use that font. Now, many |
|
|
414 | chinese characters aren't represented in japanese fonts, so when the first |
|
|
415 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
416 | \&\*(-- unfortunately at this point, it will still use the japanese font for |
|
|
417 | chinese characters that are also in the japanese font. |
|
|
418 | .PP |
|
|
419 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
420 | list (see the previous question). The key is to view the font list as |
|
|
421 | a preference list: If you expect more japanese, list a japanese font |
|
|
422 | first. If you expect more chinese, put a chinese font first. |
|
|
423 | .PP |
|
|
424 | In the future it might be possible to switch language preferences at |
|
|
425 | runtime (the internal data structure has no problem with using different |
|
|
426 | fonts for the same character at the same time, but no interface for this |
|
|
427 | has been designed yet). |
|
|
428 | .PP |
|
|
429 | Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document). |
|
|
430 | .PP |
405 | .PP |
431 | \fIWhy does rxvt-unicode sometimes leave pixel droppings?\fR |
406 | \fIWhy does rxvt-unicode sometimes leave pixel droppings?\fR |
432 | .IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?" |
407 | .IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?" |
433 | .PP |
408 | .PP |
434 | Most fonts were not designed for terminal use, which means that character |
409 | Most fonts were not designed for terminal use, which means that character |
… | |
… | |
571 | \& URxvt.color13: #FF00FF |
546 | \& URxvt.color13: #FF00FF |
572 | \& URxvt.color14: #00FFFF |
547 | \& URxvt.color14: #00FFFF |
573 | \& URxvt.color15: #FFFFFF |
548 | \& URxvt.color15: #FFFFFF |
574 | .Ve |
549 | .Ve |
575 | .PP |
550 | .PP |
576 | And here is a more complete set of non-standard colors described (not by |
551 | And here is a more complete set of non-standard colors. |
577 | me) as \*(L"pretty girly\*(R". |
|
|
578 | .PP |
552 | .PP |
579 | .Vb 18 |
553 | .Vb 18 |
580 | \& URxvt.cursorColor: #dc74d1 |
554 | \& URxvt.cursorColor: #dc74d1 |
581 | \& URxvt.pointerColor: #dc74d1 |
555 | \& URxvt.pointerColor: #dc74d1 |
582 | \& URxvt.background: #0e0e0e |
556 | \& URxvt.background: #0e0e0e |
… | |
… | |
595 | \& URxvt.color14: #73f7ff |
569 | \& URxvt.color14: #73f7ff |
596 | \& URxvt.color7: #e1dddd |
570 | \& URxvt.color7: #e1dddd |
597 | \& URxvt.color15: #e1dddd |
571 | \& URxvt.color15: #e1dddd |
598 | .Ve |
572 | .Ve |
599 | .PP |
573 | .PP |
|
|
574 | They have been described (not by me) as \*(L"pretty girly\*(R". |
|
|
575 | .PP |
600 | \fIWhy do some characters look so much different than others?\fR |
576 | \fIWhy do some characters look so much different than others?\fR |
601 | .IX Subsection "Why do some characters look so much different than others?" |
577 | .IX Subsection "Why do some characters look so much different than others?" |
602 | .PP |
578 | .PP |
603 | See next entry. |
579 | See next entry. |
604 | .PP |
580 | .PP |
… | |
… | |
619 | .PP |
595 | .PP |
620 | In that case, select a font of your taste and add it to the font list, |
596 | In that case, select a font of your taste and add it to the font list, |
621 | e.g.: |
597 | e.g.: |
622 | .PP |
598 | .PP |
623 | .Vb 1 |
599 | .Vb 1 |
624 | \& @@RXVT_NAME@@ -fn basefont,font2,font3... |
600 | \& @@URXVT_NAME@@ -fn basefont,font2,font3... |
625 | .Ve |
601 | .Ve |
626 | .PP |
602 | .PP |
627 | When rxvt-unicode sees a character, it will first look at the base |
603 | When rxvt-unicode sees a character, it will first look at the base |
628 | font. If the base font does not contain the character, it will go to the |
604 | font. If the base font does not contain the character, it will go to the |
629 | next font, and so on. Specifying your own fonts will also speed up this |
605 | next font, and so on. Specifying your own fonts will also speed up this |
630 | search and use less resources within rxvt-unicode and the X\-server. |
606 | search and use less resources within rxvt-unicode and the X\-server. |
631 | .PP |
607 | .PP |
632 | The only limitation is that none of the fonts may be larger than the base |
608 | The only limitation is that none of the fonts may be larger than the base |
633 | font, as the base font defines the terminal character cell size, which |
609 | font, as the base font defines the terminal character cell size, which |
634 | must be the same due to the way terminals work. |
610 | must be the same due to the way terminals work. |
|
|
611 | .PP |
|
|
612 | \fIWhy do some chinese characters look so different than others?\fR |
|
|
613 | .IX Subsection "Why do some chinese characters look so different than others?" |
|
|
614 | .PP |
|
|
615 | This is because there is a difference between script and language \*(-- |
|
|
616 | rxvt-unicode does not know which language the text that is output is, |
|
|
617 | as it only knows the unicode character codes. If rxvt-unicode first |
|
|
618 | sees a japanese/chinese character, it might choose a japanese font for |
|
|
619 | display. Subsequent japanese characters will use that font. Now, many |
|
|
620 | chinese characters aren't represented in japanese fonts, so when the first |
|
|
621 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
622 | \&\*(-- unfortunately at this point, it will still use the japanese font for |
|
|
623 | chinese characters that are also in the japanese font. |
|
|
624 | .PP |
|
|
625 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
626 | list (see the previous question). The key is to view the font list as |
|
|
627 | a preference list: If you expect more japanese, list a japanese font |
|
|
628 | first. If you expect more chinese, put a chinese font first. |
|
|
629 | .PP |
|
|
630 | In the future it might be possible to switch language preferences at |
|
|
631 | runtime (the internal data structure has no problem with using different |
|
|
632 | fonts for the same character at the same time, but no interface for this |
|
|
633 | has been designed yet). |
|
|
634 | .PP |
|
|
635 | Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document). |
635 | .Sh "Keyboard, Mouse & User Interaction" |
636 | .Sh "Keyboard, Mouse & User Interaction" |
636 | .IX Subsection "Keyboard, Mouse & User Interaction" |
637 | .IX Subsection "Keyboard, Mouse & User Interaction" |
637 | \fIThe new selection selects pieces that are too big, how can I select single words?\fR |
638 | \fIThe new selection selects pieces that are too big, how can I select single words?\fR |
638 | .IX Subsection "The new selection selects pieces that are too big, how can I select single words?" |
639 | .IX Subsection "The new selection selects pieces that are too big, how can I select single words?" |
639 | .PP |
640 | .PP |
… | |
… | |
663 | \&\fBperl-ext-common\fR resource to the empty string, which also keeps |
664 | \&\fBperl-ext-common\fR resource to the empty string, which also keeps |
664 | rxvt-unicode from initialising perl, saving memory. |
665 | rxvt-unicode from initialising perl, saving memory. |
665 | .PP |
666 | .PP |
666 | If you only want to disable specific features, you first have to |
667 | If you only want to disable specific features, you first have to |
667 | identify which perl extension is responsible. For this, read the section |
668 | identify which perl extension is responsible. For this, read the section |
668 | \&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For |
669 | \&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@URXVT_NAME@@\fIperl\fR\|(3) manpage. For |
669 | example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify |
670 | example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify |
670 | this \fBperl-ext-common\fR resource: |
671 | this \fBperl-ext-common\fR resource: |
671 | .PP |
672 | .PP |
672 | .Vb 1 |
673 | .Vb 1 |
673 | \& URxvt.perl-ext-common: default,-selection-popup,-option-popup |
674 | \& URxvt.perl-ext-common: default,-selection-popup,-option-popup |
… | |
… | |
765 | For starting a new rxvt\-unicode: |
766 | For starting a new rxvt\-unicode: |
766 | .PP |
767 | .PP |
767 | .Vb 3 |
768 | .Vb 3 |
768 | \& # use Backspace = ^H |
769 | \& # use Backspace = ^H |
769 | \& $ stty erase ^H |
770 | \& $ stty erase ^H |
770 | \& $ @@RXVT_NAME@@ |
771 | \& $ @@URXVT_NAME@@ |
771 | .Ve |
772 | .Ve |
772 | .PP |
773 | .PP |
773 | .Vb 3 |
774 | .Vb 3 |
774 | \& # use Backspace = ^? |
775 | \& # use Backspace = ^? |
775 | \& $ stty erase ^? |
776 | \& $ stty erase ^? |
776 | \& $ @@RXVT_NAME@@ |
777 | \& $ @@URXVT_NAME@@ |
777 | .Ve |
778 | .Ve |
778 | .PP |
779 | .PP |
779 | Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR. |
780 | Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR. |
780 | .PP |
781 | .PP |
781 | For an existing rxvt\-unicode: |
782 | For an existing rxvt\-unicode: |
… | |
… | |
814 | .PP |
815 | .PP |
815 | There are some compile-time selections available via configure. Unless |
816 | There are some compile-time selections available via configure. Unless |
816 | you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can |
817 | you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can |
817 | use the `keysym' resource to alter the keystrings associated with keysyms. |
818 | use the `keysym' resource to alter the keystrings associated with keysyms. |
818 | .PP |
819 | .PP |
819 | Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR |
820 | Here's an example for a URxvt session started using \f(CW\*(C`@@URXVT_NAME@@ \-name URxvt\*(C'\fR |
820 | .PP |
821 | .PP |
821 | .Vb 20 |
822 | .Vb 20 |
822 | \& URxvt.keysym.Home: \e033[1~ |
823 | \& URxvt.keysym.Home: \e033[1~ |
823 | \& URxvt.keysym.End: \e033[4~ |
824 | \& URxvt.keysym.End: \e033[4~ |
824 | \& URxvt.keysym.C-apostrophe: \e033<C-'> |
825 | \& URxvt.keysym.C-apostrophe: \e033<C-'> |
… | |
… | |
912 | .Vb 1 |
913 | .Vb 1 |
913 | \& URxvt.termName: rxvt |
914 | \& URxvt.termName: rxvt |
914 | .Ve |
915 | .Ve |
915 | .PP |
916 | .PP |
916 | If you don't plan to use \fBrxvt\fR (quite common...) you could also replace |
917 | If you don't plan to use \fBrxvt\fR (quite common...) you could also replace |
917 | the rxvt terminfo file with the rxvt-unicode one. |
918 | the rxvt terminfo file with the rxvt-unicode one and use \f(CW\*(C`TERM=rxvt\*(C'\fR. |
918 | .PP |
919 | .PP |
919 | \fI\f(CI\*(C`tic\*(C'\fI outputs some error when compiling the terminfo entry.\fR |
920 | \fI\f(CI\*(C`tic\*(C'\fI outputs some error when compiling the terminfo entry.\fR |
920 | .IX Subsection "tic outputs some error when compiling the terminfo entry." |
921 | .IX Subsection "tic outputs some error when compiling the terminfo entry." |
921 | .PP |
922 | .PP |
922 | Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by |
923 | Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by |
923 | \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. |
924 | \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. |
924 | .PP |
925 | .PP |
925 | \fI\f(CI\*(C`bash\*(C'\fI's readline does not work correctly under @@RXVT_NAME@@.\fR |
926 | \fI\f(CI\*(C`bash\*(C'\fI's readline does not work correctly under @@URXVT_NAME@@.\fR |
926 | .IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@." |
927 | .IX Subsection "bash's readline does not work correctly under @@URXVT_NAME@@." |
927 | .PP |
928 | .PP |
928 | See next entry. |
929 | See next entry. |
929 | .PP |
930 | .PP |
930 | \fII need a termcap file entry.\fR |
931 | \fII need a termcap file entry.\fR |
931 | .IX Subsection "I need a termcap file entry." |
932 | .IX Subsection "I need a termcap file entry." |
… | |
… | |
1264 | old libW11 emulation. |
1265 | old libW11 emulation. |
1265 | .PP |
1266 | .PP |
1266 | At the time of this writing, cygwin didn't seem to support any multi-byte |
1267 | At the time of this writing, cygwin didn't seem to support any multi-byte |
1267 | encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited |
1268 | encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited |
1268 | to 8\-bit encodings. |
1269 | to 8\-bit encodings. |
1269 | .SH "RXVT TECHNICAL REFERENCE" |
1270 | .SH "RXVT-UNICODE TECHNICAL REFERENCE" |
1270 | .IX Header "RXVT TECHNICAL REFERENCE" |
1271 | .IX Header "RXVT-UNICODE TECHNICAL REFERENCE" |
1271 | .SH "DESCRIPTION" |
|
|
1272 | .IX Header "DESCRIPTION" |
|
|
1273 | The rest of this document describes various technical aspects of |
1272 | The rest of this document describes various technical aspects of |
1274 | \&\fBrxvt-unicode\fR. First the description of supported command sequences, |
1273 | \&\fBrxvt-unicode\fR. First the description of supported command sequences, |
1275 | followed by pixmap support and last by a description of all features |
1274 | followed by pixmap support and last by a description of all features |
1276 | selectable at \f(CW\*(C`configure\*(C'\fR time. |
1275 | selectable at \f(CW\*(C`configure\*(C'\fR time. |
1277 | .SH "Definitions" |
1276 | .Sh "Definitions" |
1278 | .IX Header "Definitions" |
1277 | .IX Subsection "Definitions" |
1279 | .ie n .IP "\fB\fB""c""\fB\fR" 4 |
1278 | .ie n .IP "\fB\fB""c""\fB\fR" 4 |
1280 | .el .IP "\fB\f(CBc\fB\fR" 4 |
1279 | .el .IP "\fB\f(CBc\fB\fR" 4 |
1281 | .IX Item "c" |
1280 | .IX Item "c" |
1282 | The literal character c. |
1281 | The literal character c. |
1283 | .ie n .IP "\fB\fB""C""\fB\fR" 4 |
1282 | .ie n .IP "\fB\fB""C""\fB\fR" 4 |
… | |
… | |
1296 | parameters, separated by \f(CW\*(C`;\*(C'\fR character(s). |
1295 | parameters, separated by \f(CW\*(C`;\*(C'\fR character(s). |
1297 | .ie n .IP "\fB\fB""Pt""\fB\fR" 4 |
1296 | .ie n .IP "\fB\fB""Pt""\fB\fR" 4 |
1298 | .el .IP "\fB\f(CBPt\fB\fR" 4 |
1297 | .el .IP "\fB\f(CBPt\fB\fR" 4 |
1299 | .IX Item "Pt" |
1298 | .IX Item "Pt" |
1300 | A text parameter composed of printable characters. |
1299 | A text parameter composed of printable characters. |
1301 | .SH "Values" |
1300 | .Sh "Values" |
1302 | .IX Header "Values" |
1301 | .IX Subsection "Values" |
1303 | .ie n .IP "\fB\fB""ENQ""\fB\fR" 4 |
1302 | .ie n .IP "\fB\fB""ENQ""\fB\fR" 4 |
1304 | .el .IP "\fB\f(CBENQ\fB\fR" 4 |
1303 | .el .IP "\fB\f(CBENQ\fB\fR" 4 |
1305 | .IX Item "ENQ" |
1304 | .IX Item "ENQ" |
1306 | Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0) |
1305 | Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0) |
1307 | request attributes from terminal. See \fB\f(CB\*(C`ESC [ Ps c\*(C'\fB\fR. |
1306 | request attributes from terminal. See \fB\f(CB\*(C`ESC [ Ps c\*(C'\fB\fR. |
… | |
… | |
1345 | Switch to Standard Character Set |
1344 | Switch to Standard Character Set |
1346 | .ie n .IP "\fB\fB""SPC""\fB\fR" 4 |
1345 | .ie n .IP "\fB\fB""SPC""\fB\fR" 4 |
1347 | .el .IP "\fB\f(CBSPC\fB\fR" 4 |
1346 | .el .IP "\fB\f(CBSPC\fB\fR" 4 |
1348 | .IX Item "SPC" |
1347 | .IX Item "SPC" |
1349 | Space Character |
1348 | Space Character |
1350 | .SH "Escape Sequences" |
1349 | .Sh "Escape Sequences" |
1351 | .IX Header "Escape Sequences" |
1350 | .IX Subsection "Escape Sequences" |
1352 | .ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4 |
1351 | .ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4 |
1353 | .el .IP "\fB\f(CBESC # 8\fB\fR" 4 |
1352 | .el .IP "\fB\f(CBESC # 8\fB\fR" 4 |
1354 | .IX Item "ESC # 8" |
1353 | .IX Item "ESC # 8" |
1355 | \&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0) |
1354 | \&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0) |
1356 | .ie n .IP "\fB\fB""ESC 7""\fB\fR" 4 |
1355 | .ie n .IP "\fB\fB""ESC 7""\fB\fR" 4 |
… | |
… | |
1449 | .TE |
1448 | .TE |
1450 | |
1449 | |
1451 | .PP |
1450 | .PP |
1452 | |
1451 | |
1453 | .IX Xref "CSI" |
1452 | .IX Xref "CSI" |
1454 | .SH "CSI (Command Sequence Introducer) Sequences" |
1453 | .Sh "\s-1CSI\s0 (Command Sequence Introducer) Sequences" |
1455 | .IX Header "CSI (Command Sequence Introducer) Sequences" |
1454 | .IX Subsection "CSI (Command Sequence Introducer) Sequences" |
1456 | .ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4 |
1455 | .ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4 |
1457 | .el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4 |
1456 | .el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4 |
1458 | .IX Item "ESC [ Ps @" |
1457 | .IX Item "ESC [ Ps @" |
1459 | Insert \fB\f(CB\*(C`Ps\*(C'\fB\fR (Blank) Character(s) [default: 1] (\s-1ICH\s0) |
1458 | Insert \fB\f(CB\*(C`Ps\*(C'\fB\fR (Blank) Character(s) [default: 1] (\s-1ICH\s0) |
1460 | .IX Xref "ESCOBPsA" |
1459 | .IX Xref "ESCOBPsA" |
… | |
… | |
1723 | .IX Item "ESC [ Ps x" |
1722 | .IX Item "ESC [ Ps x" |
1724 | Request Terminal Parameters (\s-1DECREQTPARM\s0) |
1723 | Request Terminal Parameters (\s-1DECREQTPARM\s0) |
1725 | .PP |
1724 | .PP |
1726 | |
1725 | |
1727 | .IX Xref "PrivateModes" |
1726 | .IX Xref "PrivateModes" |
1728 | .SH "DEC Private Modes" |
1727 | .Sh "\s-1DEC\s0 Private Modes" |
1729 | .IX Header "DEC Private Modes" |
1728 | .IX Subsection "DEC Private Modes" |
1730 | .ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4 |
1729 | .ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4 |
1731 | .el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4 |
1730 | .el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4 |
1732 | .IX Item "ESC [ ? Pm h" |
1731 | .IX Item "ESC [ ? Pm h" |
1733 | \&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0) |
1732 | \&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0) |
1734 | .ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4 |
1733 | .ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4 |
… | |
… | |
2001 | .RE |
2000 | .RE |
2002 | .PD |
2001 | .PD |
2003 | .PP |
2002 | .PP |
2004 | |
2003 | |
2005 | .IX Xref "XTerm" |
2004 | .IX Xref "XTerm" |
2006 | .SH "XTerm Operating System Commands" |
2005 | .Sh "XTerm Operating System Commands" |
2007 | .IX Header "XTerm Operating System Commands" |
2006 | .IX Subsection "XTerm Operating System Commands" |
2008 | .ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4 |
2007 | .ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4 |
2009 | .el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4 |
2008 | .el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4 |
2010 | .IX Item "ESC ] Ps;Pt ST" |
2009 | .IX Item "ESC ] Ps;Pt ST" |
2011 | Set XTerm Parameters. 8\-bit \s-1ST:\s0 0x9c, 7\-bit \s-1ST\s0 sequence: \s-1ESC\s0 \e (0x1b, |
2010 | Set XTerm Parameters. 8\-bit \s-1ST:\s0 0x9c, 7\-bit \s-1ST\s0 sequence: \s-1ESC\s0 \e (0x1b, |
2012 | 0x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any |
2011 | 0x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any |
… | |
… | |
2044 | Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). |
2043 | Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). |
2045 | Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). |
2044 | Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). |
2046 | Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl). |
2045 | Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl). |
2047 | .TE |
2046 | .TE |
2048 | |
2047 | |
2049 | .PP |
|
|
2050 | |
|
|
2051 | .IX Xref "XPM" |
|
|
2052 | .SH "XPM" |
2048 | .SH "XPM" |
2053 | .IX Header "XPM" |
2049 | .IX Header "XPM" |
2054 | For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value |
2050 | For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value |
2055 | of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a |
2051 | of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a |
2056 | sequence of scaling/positioning commands separated by semi\-colons. The |
2052 | sequence of scaling/positioning commands separated by semi\-colons. The |
… | |
… | |
2126 | .TS |
2122 | .TS |
2127 | l l . |
2123 | l l . |
2128 | 4 Shift |
2124 | 4 Shift |
2129 | 8 Meta |
2125 | 8 Meta |
2130 | 16 Control |
2126 | 16 Control |
2131 | 32 Double Click (Rxvt extension) |
2127 | 32 Double Click (rxvt extension) |
2132 | .TE |
2128 | .TE |
2133 | |
2129 | |
2134 | Col = \fB\f(CB\*(C`<x> \- SPACE\*(C'\fB\fR |
2130 | Col = \fB\f(CB\*(C`<x> \- SPACE\*(C'\fB\fR |
2135 | .Sp |
2131 | .Sp |
2136 | Row = \fB\f(CB\*(C`<y> \- SPACE\*(C'\fB\fR |
2132 | Row = \fB\f(CB\*(C`<y> \- SPACE\*(C'\fB\fR |