… | |
… | |
4 | Before sending me mail, you could go to IRC: "irc.freenode.net", channel |
4 | Before sending me mail, you could go to IRC: "irc.freenode.net", channel |
5 | "#rxvt-unicode" has some rxvt-unicode enthusiasts that might be |
5 | "#rxvt-unicode" has some rxvt-unicode enthusiasts that might be |
6 | interested in learning about new and exciting problems (but not FAQs :). |
6 | interested in learning about new and exciting problems (but not FAQs :). |
7 | |
7 | |
8 | I use Gentoo, and I have a problem... |
8 | I use Gentoo, and I have a problem... |
9 | There are three big problems with Gentoo Linux: first of all, most if |
9 | There are two big problems with Gentoo Linux: first, most if not all |
10 | not all Gentoo systems are completely broken (missing or mismatched |
10 | Gentoo systems are completely broken (missing or mismatched header |
11 | header files, broken compiler etc. are just the tip of the iceberg); |
11 | files, broken compiler etc. are just the tip of the iceberg); secondly, |
12 | secondly, the Gentoo maintainer thinks it is a good idea to add broken |
12 | it should be called Gentoo GNU/Linux. |
13 | patches to the code; and lastly, it should be called Gentoo GNU/Linux. |
|
|
14 | |
13 | |
15 | For these reasons, it is impossible to support rxvt-unicode on Gentoo. |
14 | For these reasons, it is impossible to support rxvt-unicode on Gentoo. |
16 | Problems appearing on Gentoo systems will usually simply be ignored |
15 | Problems appearing on Gentoo systems will usually simply be ignored |
17 | unless they can be reproduced on non-Gentoo systems. |
16 | unless they can be reproduced on non-Gentoo systems. |
18 | |
17 | |
… | |
… | |
429 | We are working on it, in the meantime, as a workaround, use something |
428 | We are working on it, in the meantime, as a workaround, use something |
430 | like: |
429 | like: |
431 | |
430 | |
432 | urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...' |
431 | urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...' |
433 | |
432 | |
|
|
433 | Why is the cursor now blinking in emacs/vi/...? |
|
|
434 | This is likely caused by your editor/program's use of the "cvvis" |
|
|
435 | terminfo capability. Emacs uses it by default, as well as some versions |
|
|
436 | of vi and possibly other programs. |
|
|
437 | |
|
|
438 | In emacs, you can switch that off by adding this to your ".emacs" file: |
|
|
439 | |
|
|
440 | (setq visible-cursor nil) |
|
|
441 | |
|
|
442 | For other programs, if they do not have an option, your have to remove |
|
|
443 | the "cvvis" capability from the terminfo description. |
|
|
444 | |
|
|
445 | When urxvt first added the blinking cursor option, it didn't add a |
|
|
446 | "cvvis" capability, which served no purpose before. Version 9.21 |
|
|
447 | introduced "cvvis" (and the ability to control blinking independent of |
|
|
448 | cursor shape) for compatibility with other terminals, which |
|
|
449 | traditionally use a blinking cursor for "cvvis". This also reflects the |
|
|
450 | intent of programs such as emacs, who expect "cvvis" to enable a |
|
|
451 | blinking cursor. |
|
|
452 | |
434 | Keyboard, Mouse & User Interaction |
453 | Keyboard, Mouse & User Interaction |
435 | The new selection selects pieces that are too big, how can I select single words? |
454 | The new selection selects pieces that are too big, how can I select single words? |
436 | If you want to select e.g. alphanumeric words, you can use the following |
455 | If you want to select e.g. alphanumeric words, you can use the following |
437 | setting: |
456 | setting: |
438 | |
457 | |
… | |
… | |
463 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
482 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
464 | |
483 | |
465 | This will keep the default extensions, but disable the two popup |
484 | This will keep the default extensions, but disable the two popup |
466 | extensions. Some extensions can also be configured, for example, |
485 | extensions. Some extensions can also be configured, for example, |
467 | scrollback search mode is triggered by M-s. You can move it to any other |
486 | scrollback search mode is triggered by M-s. You can move it to any other |
468 | combination either by setting the searchable-scrollback resource: |
487 | combination by adding a keysym resource that binds the desired |
|
|
488 | combination to the "start" action of "searchable-scrollback" and another |
|
|
489 | one that binds M-s to the "builtin:" action: |
469 | |
490 | |
470 | URxvt.searchable-scrollback: CM-s |
491 | URxvt.keysym.CM-s: searchable-scrollback:start |
|
|
492 | URxvt.keysym.M-s: builtin: |
471 | |
493 | |
472 | The cursor moves when selecting text in the current input line, how do I switch this off? |
494 | The cursor moves when selecting text in the current input line, how do I switch this off? |
473 | See next entry. |
495 | See next entry. |
474 | |
496 | |
475 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
497 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
… | |
… | |
482 | You can permanently switch this feature off by disabling the "readline" |
504 | You can permanently switch this feature off by disabling the "readline" |
483 | extension: |
505 | extension: |
484 | |
506 | |
485 | URxvt.perl-ext-common: default,-readline |
507 | URxvt.perl-ext-common: default,-readline |
486 | |
508 | |
487 | My numerical keypad acts weird and generates differing output? |
509 | My numeric keypad acts weird and generates differing output? |
488 | Some Debian GNUL/Linux users seem to have this problem, although no |
510 | Some Debian GNU/Linux users seem to have this problem, although no |
489 | specific details were reported so far. It is possible that this is |
511 | specific details were reported so far. It is possible that this is |
490 | caused by the wrong "TERM" setting, although the details of whether and |
512 | caused by the wrong "TERM" setting, although the details of whether and |
491 | how this can happen are unknown, as "TERM=rxvt" should offer a |
513 | how this can happen are unknown, as "TERM=rxvt" should offer a |
492 | compatible keymap. See the answer to the previous question, and please |
514 | compatible keymap. See the answer to the previous question, and please |
493 | report if that helped. |
515 | report if that helped. |
… | |
… | |
774 | |
796 | |
775 | REMOTE=remotesystem.domain |
797 | REMOTE=remotesystem.domain |
776 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
798 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
777 | |
799 | |
778 | One some systems you might need to set $TERMINFO to the full path of |
800 | One some systems you might need to set $TERMINFO to the full path of |
779 | $HOME/.terminfo for this to work. Debian systems have a broken tic which |
801 | $HOME/.terminfo for this to work. |
780 | will not be able to overwrite the existing rxvt-unicode terminfo entry - |
|
|
781 | you might have to manually delete all traces of rxvt-unicode* from |
|
|
782 | /etc/terminfo. |
|
|
783 | |
802 | |
784 | If you cannot or do not want to do this, then you can simply set |
803 | If you cannot or do not want to do this, then you can simply set |
785 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
804 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
786 | problems arising, which includes wrong keymapping, less and different |
805 | problems arising, which includes wrong keymapping, less and different |
787 | colours and some refresh errors in fullscreen applications. It's a nice |
806 | colours and some refresh errors in fullscreen applications. It's a nice |
… | |
… | |
809 | See next entry. |
828 | See next entry. |
810 | |
829 | |
811 | I need a termcap file entry. |
830 | I need a termcap file entry. |
812 | One reason you might want this is that some distributions or operating |
831 | One reason you might want this is that some distributions or operating |
813 | systems still compile some programs using the long-obsoleted termcap |
832 | systems still compile some programs using the long-obsoleted termcap |
814 | library (Fedora Core's bash is one example) and rely on a termcap entry |
833 | library (Fedora's bash is one example) and rely on a termcap entry for |
815 | for "rxvt-unicode". |
834 | "rxvt-unicode". |
816 | |
835 | |
817 | You could use rxvt's termcap entry with reasonable results in many |
836 | You could use rxvt's termcap entry with reasonable results in many |
818 | cases. You can also create a termcap entry by using terminfo's infocmp |
837 | cases. You can also create a termcap entry by using terminfo's infocmp |
819 | program like this: |
838 | program like this: |
820 | |
839 | |
… | |
… | |
843 | Why doesn't vim/emacs etc. make use of italic? |
862 | Why doesn't vim/emacs etc. make use of italic? |
844 | See next entry. |
863 | See next entry. |
845 | |
864 | |
846 | Why are the secondary screen-related options not working properly? |
865 | Why are the secondary screen-related options not working properly? |
847 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
866 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
848 | distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
867 | distributions break rxvt-unicode by setting "TERM" to "rxvt", which |
849 | setting "TERM" to "rxvt", which doesn't have these extra features. |
868 | doesn't have these extra features. Unfortunately, some of these |
850 | Unfortunately, some of these (most notably, again, Debian GNU/Linux) |
|
|
851 | furthermore fail to even install the "rxvt-unicode" terminfo file, so |
869 | furthermore fail to even install the "rxvt-unicode" terminfo file, so |
852 | you will need to install it on your own (See the question When I log-in |
870 | you will need to install it on your own (See the question When I log-in |
853 | to another system it tells me about missing terminfo data? on how to do |
871 | to another system it tells me about missing terminfo data? on how to do |
854 | this). |
872 | this). |
855 | |
873 | |
… | |
… | |
988 | cannot be completely avoided even if both sides cooperate. |
1006 | cannot be completely avoided even if both sides cooperate. |
989 | |
1007 | |
990 | So the only workaround is not to kill your Input Method Servers. |
1008 | So the only workaround is not to kill your Input Method Servers. |
991 | |
1009 | |
992 | Operating Systems / Package Maintaining |
1010 | Operating Systems / Package Maintaining |
993 | I am using Debian GNU/Linux and have a problem... |
|
|
994 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
995 | patches that considerably change the behaviour of rxvt-unicode (but |
|
|
996 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
997 | the original rxvt-unicode author please download and install the genuine |
|
|
998 | version (<http://software.schmorp.de/pkg/rxvt-unicode.html>) and try to |
|
|
999 | reproduce the problem. If you cannot, chances are that the problems are |
|
|
1000 | specific to Debian GNU/Linux, in which case it should be reported via |
|
|
1001 | the Debian Bug Tracking System (use "reportbug" to report the bug). |
|
|
1002 | |
|
|
1003 | For other problems that also affect the Debian package, you can and |
|
|
1004 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
1005 | bug in the Debian version and it serves as a reminder for other users |
|
|
1006 | that might encounter the same issue. |
|
|
1007 | |
|
|
1008 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1011 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1009 | You should build one binary with the default options. configure now |
1012 | You should build one binary with the default options. configure now |
1010 | enables most useful options, and the trend goes to making them |
1013 | enables most useful options, and the trend goes to making them |
1011 | runtime-switchable, too, so there is usually no drawback to enabling |
1014 | runtime-switchable, too, so there is usually no drawback to enabling |
1012 | them, except higher disk and possibly memory usage. The perl interpreter |
1015 | them, except higher disk and possibly memory usage. The perl interpreter |