| … | |
… | |
| 199 | other combination either by setting the \fBsearchable-scrollback\fR resource: |
199 | other combination either by setting the \fBsearchable-scrollback\fR resource: |
| 200 | .PP |
200 | .PP |
| 201 | .Vb 1 |
201 | .Vb 1 |
| 202 | \& URxvt.searchable-scrollback: CM-s |
202 | \& URxvt.searchable-scrollback: CM-s |
| 203 | .Ve |
203 | .Ve |
|
|
204 | .PP |
| 204 | .Sh "The cursor moves when selecting text in the current input line, how do I switch this off?" |
205 | \fIThe cursor moves when selecting text in the current input line, how do I switch this off?\fR |
| 205 | .IX Subsection "The cursor moves when selecting text in the current input line, how do I switch this off?" |
206 | .IX Subsection "The cursor moves when selecting text in the current input line, how do I switch this off?" |
|
|
207 | .PP |
|
|
208 | See next entry. |
| 206 | .Sh "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?" |
209 | .Sh "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?" |
| 207 | .IX Subsection "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?" |
210 | .IX Subsection "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?" |
| 208 | These are caused by the \f(CW\*(C`readline\*(C'\fR perl extension. Under normal |
211 | These are caused by the \f(CW\*(C`readline\*(C'\fR perl extension. Under normal |
| 209 | circumstances, it will move your cursor around when you click into the |
212 | circumstances, it will move your cursor around when you click into the |
| 210 | line that contains it. It tries hard not to do this at the wrong moment, |
213 | line that contains it. It tries hard not to do this at the wrong moment, |
| … | |
… | |
| 486 | Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by |
489 | Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by |
| 487 | \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. |
490 | \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. |
| 488 | .ie n .Sh """bash""'s readline does not work correctly under @@RXVT_NAME@@." |
491 | .ie n .Sh """bash""'s readline does not work correctly under @@RXVT_NAME@@." |
| 489 | .el .Sh "\f(CWbash\fP's readline does not work correctly under @@RXVT_NAME@@." |
492 | .el .Sh "\f(CWbash\fP's readline does not work correctly under @@RXVT_NAME@@." |
| 490 | .IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@." |
493 | .IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@." |
|
|
494 | See next entry. |
| 491 | .Sh "I need a termcap file entry." |
495 | .Sh "I need a termcap file entry." |
| 492 | .IX Subsection "I need a termcap file entry." |
496 | .IX Subsection "I need a termcap file entry." |
| 493 | One reason you might want this is that some distributions or operating |
497 | One reason you might want this is that some distributions or operating |
| 494 | systems still compile some programs using the long-obsoleted termcap |
498 | systems still compile some programs using the long-obsoleted termcap |
| 495 | library (Fedora Core's bash is one example) and rely on a termcap entry |
499 | library (Fedora Core's bash is one example) and rely on a termcap entry |
| … | |
… | |
| 546 | .Ve |
550 | .Ve |
| 547 | .PP |
551 | .PP |
| 548 | to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR. |
552 | to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR. |
| 549 | .Sh "Why doesn't vim/emacs etc. use the 88 colour mode?" |
553 | .Sh "Why doesn't vim/emacs etc. use the 88 colour mode?" |
| 550 | .IX Subsection "Why doesn't vim/emacs etc. use the 88 colour mode?" |
554 | .IX Subsection "Why doesn't vim/emacs etc. use the 88 colour mode?" |
|
|
555 | See next entry. |
| 551 | .Sh "Why doesn't vim/emacs etc. make use of italic?" |
556 | .Sh "Why doesn't vim/emacs etc. make use of italic?" |
| 552 | .IX Subsection "Why doesn't vim/emacs etc. make use of italic?" |
557 | .IX Subsection "Why doesn't vim/emacs etc. make use of italic?" |
|
|
558 | See next entry. |
| 553 | .Sh "Why are the secondary screen-related options not working properly?" |
559 | .Sh "Why are the secondary screen-related options not working properly?" |
| 554 | .IX Subsection "Why are the secondary screen-related options not working properly?" |
560 | .IX Subsection "Why are the secondary screen-related options not working properly?" |
| 555 | Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged |
561 | Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged |
| 556 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
562 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
| 557 | by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra |
563 | by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra |
| … | |
… | |
| 568 | this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible |
574 | this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible |
| 569 | keymap. See the answer to the previous question, and please report if that |
575 | keymap. See the answer to the previous question, and please report if that |
| 570 | helped. |
576 | helped. |
| 571 | .Sh "Rxvt-unicode does not seem to understand the selected encoding?" |
577 | .Sh "Rxvt-unicode does not seem to understand the selected encoding?" |
| 572 | .IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?" |
578 | .IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?" |
|
|
579 | See next entry. |
| 573 | .Sh "Unicode does not seem to work?" |
580 | .Sh "Unicode does not seem to work?" |
| 574 | .IX Subsection "Unicode does not seem to work?" |
581 | .IX Subsection "Unicode does not seem to work?" |
| 575 | If you encounter strange problems like typing an accented character but |
582 | If you encounter strange problems like typing an accented character but |
| 576 | getting two unrelated other characters or similar, or if program output is |
583 | getting two unrelated other characters or similar, or if program output is |
| 577 | subtly garbled, then you should check your locale settings. |
584 | subtly garbled, then you should check your locale settings. |
| … | |
… | |
| 603 | If nothing works and you are sure that everything is set correctly then |
610 | If nothing works and you are sure that everything is set correctly then |
| 604 | you will need to remember a little known fact: Some programs just don't |
611 | you will need to remember a little known fact: Some programs just don't |
| 605 | support locales :( |
612 | support locales :( |
| 606 | .Sh "Why do some characters look so much different than others?" |
613 | .Sh "Why do some characters look so much different than others?" |
| 607 | .IX Subsection "Why do some characters look so much different than others?" |
614 | .IX Subsection "Why do some characters look so much different than others?" |
|
|
615 | See next entry. |
| 608 | .Sh "How does rxvt-unicode choose fonts?" |
616 | .Sh "How does rxvt-unicode choose fonts?" |
| 609 | .IX Subsection "How does rxvt-unicode choose fonts?" |
617 | .IX Subsection "How does rxvt-unicode choose fonts?" |
| 610 | Most fonts do not contain the full range of Unicode, which is |
618 | Most fonts do not contain the full range of Unicode, which is |
| 611 | fine. Chances are that the font you (or the admin/package maintainer of |
619 | fine. Chances are that the font you (or the admin/package maintainer of |
| 612 | your system/os) have specified does not cover all the characters you want |
620 | your system/os) have specified does not cover all the characters you want |
| … | |
… | |
| 774 | At the time of this writing, cygwin didn't seem to support any multi-byte |
782 | At the time of this writing, cygwin didn't seem to support any multi-byte |
| 775 | encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited |
783 | encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited |
| 776 | to 8\-bit encodings. |
784 | to 8\-bit encodings. |
| 777 | .Sh "How does rxvt-unicode determine the encoding to use?" |
785 | .Sh "How does rxvt-unicode determine the encoding to use?" |
| 778 | .IX Subsection "How does rxvt-unicode determine the encoding to use?" |
786 | .IX Subsection "How does rxvt-unicode determine the encoding to use?" |
|
|
787 | See next entry. |
| 779 | .Sh "Is there an option to switch encodings?" |
788 | .Sh "Is there an option to switch encodings?" |
| 780 | .IX Subsection "Is there an option to switch encodings?" |
789 | .IX Subsection "Is there an option to switch encodings?" |
| 781 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
790 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
| 782 | specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about |
791 | specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about |
| 783 | \&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O. |
792 | \&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O. |
