… | |
… | |
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 | |
… | |
… | |
91 | |
90 | |
92 | # Bourne/Korn/POSIX family of shells: |
91 | # Bourne/Korn/POSIX family of shells: |
93 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
92 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
94 | if [ ${TERM:-foo} = xterm ]; then |
93 | if [ ${TERM:-foo} = xterm ]; then |
95 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
94 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
96 | echo -n '^[Z' |
95 | printf "\eZ" |
97 | read term_id |
96 | read term_id |
98 | stty icanon echo |
97 | stty icanon echo |
99 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
98 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
100 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
99 | printf '\e[7n' # query the rxvt we are in for the DISPLAY string |
101 | read DISPLAY # set it in our local shell |
100 | read DISPLAY # set it in our local shell |
102 | fi |
101 | fi |
103 | fi |
102 | fi |
104 | |
103 | |
105 | How do I compile the manual pages on my own? |
104 | How do I compile the manual pages on my own? |
106 | You need to have a recent version of perl installed as /usr/bin/perl, |
105 | You need to have a recent version of perl installed as /usr/bin/perl, |
… | |
… | |
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 | |
… | |
… | |
482 | You can permanently switch this feature off by disabling the "readline" |
501 | You can permanently switch this feature off by disabling the "readline" |
483 | extension: |
502 | extension: |
484 | |
503 | |
485 | URxvt.perl-ext-common: default,-readline |
504 | URxvt.perl-ext-common: default,-readline |
486 | |
505 | |
487 | My numerical keypad acts weird and generates differing output? |
506 | My numeric keypad acts weird and generates differing output? |
488 | Some Debian GNUL/Linux users seem to have this problem, although no |
507 | 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 |
508 | 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 |
509 | 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 |
510 | how this can happen are unknown, as "TERM=rxvt" should offer a |
492 | compatible keymap. See the answer to the previous question, and please |
511 | compatible keymap. See the answer to the previous question, and please |
493 | report if that helped. |
512 | report if that helped. |
494 | |
513 | |
495 | My Compose (Multi_key) key is no longer working. |
514 | My Compose (Multi_key) key is no longer working. |
496 | The most common causes for this are that either your locale is not set |
515 | The most common causes for this are that either your locale is not set |
497 | correctly, or you specified a preeditStyle that is not supported by your |
516 | correctly, or you specified a preeditType that is not supported by your |
498 | input method. For example, if you specified OverTheSpot and your input |
517 | input method. For example, if you specified OverTheSpot and your input |
499 | method (e.g. the default input method handling Compose keys) does not |
518 | method (e.g. the default input method handling Compose keys) does not |
500 | support this (for instance because it is not visual), then rxvt-unicode |
519 | support this (for instance because it is not visual), then rxvt-unicode |
501 | will continue without an input method. |
520 | will continue without an input method. |
502 | |
521 | |
503 | In this case either do not specify a preeditStyle or specify more than |
522 | In this case either do not specify a preeditType or specify more than |
504 | one pre-edit style, such as OverTheSpot,Root,None. |
523 | one pre-edit style, such as OverTheSpot,Root,None. |
505 | |
524 | |
506 | If it still doesn't work, then maybe your input method doesn't support |
525 | If it still doesn't work, then maybe your input method doesn't support |
507 | compose sequences - to fall back to the built-in one, make sure you |
526 | compose sequences - to fall back to the built-in one, make sure you |
508 | don't specify an input method via "-im" or "XMODIFIERS". |
527 | don't specify an input method via "-im" or "XMODIFIERS". |
… | |
… | |
532 | It is possible to toggle between "^H" and "^?" with the DECBKM private |
551 | It is possible to toggle between "^H" and "^?" with the DECBKM private |
533 | mode: |
552 | mode: |
534 | |
553 | |
535 | # use Backspace = ^H |
554 | # use Backspace = ^H |
536 | $ stty erase ^H |
555 | $ stty erase ^H |
537 | $ echo -n "^[[?67h" |
556 | $ printf "\e[?67h" |
538 | |
557 | |
539 | # use Backspace = ^? |
558 | # use Backspace = ^? |
540 | $ stty erase ^? |
559 | $ stty erase ^? |
541 | $ echo -n "^[[?67l" |
560 | $ printf "\e[?67l" |
542 | |
561 | |
543 | This helps satisfy some of the Backspace discrepancies that occur, but |
562 | This helps satisfy some of the Backspace discrepancies that occur, but |
544 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
563 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
545 | properly reflects that. |
564 | properly reflects that. |
546 | |
565 | |
… | |
… | |
774 | |
793 | |
775 | REMOTE=remotesystem.domain |
794 | REMOTE=remotesystem.domain |
776 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
795 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
777 | |
796 | |
778 | One some systems you might need to set $TERMINFO to the full path of |
797 | 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 |
798 | $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 | |
799 | |
784 | If you cannot or do not want to do this, then you can simply set |
800 | 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 |
801 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
786 | problems arising, which includes wrong keymapping, less and different |
802 | problems arising, which includes wrong keymapping, less and different |
787 | colours and some refresh errors in fullscreen applications. It's a nice |
803 | colours and some refresh errors in fullscreen applications. It's a nice |
… | |
… | |
843 | Why doesn't vim/emacs etc. make use of italic? |
859 | Why doesn't vim/emacs etc. make use of italic? |
844 | See next entry. |
860 | See next entry. |
845 | |
861 | |
846 | Why are the secondary screen-related options not working properly? |
862 | Why are the secondary screen-related options not working properly? |
847 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
863 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
848 | distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
864 | distributions break rxvt-unicode by setting "TERM" to "rxvt", which |
849 | setting "TERM" to "rxvt", which doesn't have these extra features. |
865 | 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 |
866 | 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 |
867 | 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 |
868 | to another system it tells me about missing terminfo data? on how to do |
854 | this). |
869 | this). |
855 | |
870 | |
… | |
… | |
966 | For scim, use "@im=SCIM". You can see what input method servers are |
981 | For scim, use "@im=SCIM". You can see what input method servers are |
967 | running with this command: |
982 | running with this command: |
968 | |
983 | |
969 | xprop -root XIM_SERVERS |
984 | xprop -root XIM_SERVERS |
970 | |
985 | |
971 | |
|
|
972 | |
|
|
973 | My input method wants <some encoding> but I want UTF-8, what can I do? |
986 | My input method wants <some encoding> but I want UTF-8, what can I do? |
974 | You can specify separate locales for the input method and the rest of |
987 | You can specify separate locales for the input method and the rest of |
975 | the terminal, using the resource "imlocale": |
988 | the terminal, using the resource "imlocale": |
976 | |
989 | |
977 | URxvt.imlocale: ja_JP.EUC-JP |
990 | URxvt.imlocale: ja_JP.EUC-JP |
… | |
… | |
990 | cannot be completely avoided even if both sides cooperate. |
1003 | cannot be completely avoided even if both sides cooperate. |
991 | |
1004 | |
992 | So the only workaround is not to kill your Input Method Servers. |
1005 | So the only workaround is not to kill your Input Method Servers. |
993 | |
1006 | |
994 | Operating Systems / Package Maintaining |
1007 | Operating Systems / Package Maintaining |
995 | I am using Debian GNU/Linux and have a problem... |
|
|
996 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
997 | patches that considerably change the behaviour of rxvt-unicode (but |
|
|
998 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
999 | the original rxvt-unicode author please download and install the genuine |
|
|
1000 | version (<http://software.schmorp.de/pkg/rxvt-unicode.html>) and try to |
|
|
1001 | reproduce the problem. If you cannot, chances are that the problems are |
|
|
1002 | specific to Debian GNU/Linux, in which case it should be reported via |
|
|
1003 | the Debian Bug Tracking System (use "reportbug" to report the bug). |
|
|
1004 | |
|
|
1005 | For other problems that also affect the Debian package, you can and |
|
|
1006 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
1007 | bug in the Debian version and it serves as a reminder for other users |
|
|
1008 | that might encounter the same issue. |
|
|
1009 | |
|
|
1010 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1008 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1011 | You should build one binary with the default options. configure now |
1009 | You should build one binary with the default options. configure now |
1012 | enables most useful options, and the trend goes to making them |
1010 | enables most useful options, and the trend goes to making them |
1013 | runtime-switchable, too, so there is usually no drawback to enabling |
1011 | runtime-switchable, too, so there is usually no drawback to enabling |
1014 | them, except higher disk and possibly memory usage. The perl interpreter |
1012 | them, except higher disk and possibly memory usage. The perl interpreter |