| … | |
… | |
| 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 | |
| … | |
… | |
| 482 | You can permanently switch this feature off by disabling the "readline" |
481 | You can permanently switch this feature off by disabling the "readline" |
| 483 | extension: |
482 | extension: |
| 484 | |
483 | |
| 485 | URxvt.perl-ext-common: default,-readline |
484 | URxvt.perl-ext-common: default,-readline |
| 486 | |
485 | |
| 487 | My numerical keypad acts weird and generates differing output? |
486 | My numeric keypad acts weird and generates differing output? |
| 488 | Some Debian GNUL/Linux users seem to have this problem, although no |
487 | 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 |
488 | 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 |
489 | 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 |
490 | how this can happen are unknown, as "TERM=rxvt" should offer a |
| 492 | compatible keymap. See the answer to the previous question, and please |
491 | compatible keymap. See the answer to the previous question, and please |
| 493 | report if that helped. |
492 | report if that helped. |
| … | |
… | |
| 774 | |
773 | |
| 775 | REMOTE=remotesystem.domain |
774 | REMOTE=remotesystem.domain |
| 776 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
775 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
| 777 | |
776 | |
| 778 | One some systems you might need to set $TERMINFO to the full path of |
777 | 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 |
778 | $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 | |
779 | |
| 784 | If you cannot or do not want to do this, then you can simply set |
780 | 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 |
781 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
| 786 | problems arising, which includes wrong keymapping, less and different |
782 | problems arising, which includes wrong keymapping, less and different |
| 787 | colours and some refresh errors in fullscreen applications. It's a nice |
783 | colours and some refresh errors in fullscreen applications. It's a nice |
| … | |
… | |
| 843 | Why doesn't vim/emacs etc. make use of italic? |
839 | Why doesn't vim/emacs etc. make use of italic? |
| 844 | See next entry. |
840 | See next entry. |
| 845 | |
841 | |
| 846 | Why are the secondary screen-related options not working properly? |
842 | Why are the secondary screen-related options not working properly? |
| 847 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
843 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
| 848 | distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
844 | distributions break rxvt-unicode by setting "TERM" to "rxvt", which |
| 849 | setting "TERM" to "rxvt", which doesn't have these extra features. |
845 | 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 |
846 | 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 |
847 | 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 |
848 | to another system it tells me about missing terminfo data? on how to do |
| 854 | this). |
849 | this). |
| 855 | |
850 | |
| … | |
… | |
| 988 | cannot be completely avoided even if both sides cooperate. |
983 | cannot be completely avoided even if both sides cooperate. |
| 989 | |
984 | |
| 990 | So the only workaround is not to kill your Input Method Servers. |
985 | So the only workaround is not to kill your Input Method Servers. |
| 991 | |
986 | |
| 992 | Operating Systems / Package Maintaining |
987 | 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? |
988 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
| 1009 | You should build one binary with the default options. configure now |
989 | You should build one binary with the default options. configure now |
| 1010 | enables most useful options, and the trend goes to making them |
990 | enables most useful options, and the trend goes to making them |
| 1011 | runtime-switchable, too, so there is usually no drawback to enabling |
991 | runtime-switchable, too, so there is usually no drawback to enabling |
| 1012 | them, except higher disk and possibly memory usage. The perl interpreter |
992 | them, except higher disk and possibly memory usage. The perl interpreter |
