… | |
… | |
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, |
… | |
… | |
206 | your picture with gimp or any other tool: |
205 | your picture with gimp or any other tool: |
207 | |
206 | |
208 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
207 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
209 | urxvt -pixmap "background.jpg;:root" |
208 | urxvt -pixmap "background.jpg;:root" |
210 | |
209 | |
211 | That works. If you think it doesn't, you lack libAfterImage or |
210 | That works. If you think it doesn't, you lack GDK-PixBuf support, or you |
212 | GDK-PixBuf support, or you are unable to read. |
211 | are unable to read. |
213 | |
212 | |
214 | 3. Use an ARGB visual: |
213 | 3. Use an ARGB visual: |
215 | |
214 | |
216 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
215 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
217 | |
216 | |
… | |
… | |
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. |
494 | |
516 | |
495 | My Compose (Multi_key) key is no longer working. |
517 | My Compose (Multi_key) key is no longer working. |
496 | The most common causes for this are that either your locale is not set |
518 | 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 |
519 | correctly, or you specified a preeditType that is not supported by your |
498 | input method. For example, if you specified OverTheSpot and your input |
520 | input method. For example, if you specified OverTheSpot and your input |
499 | method (e.g. the default input method handling Compose keys) does not |
521 | 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 |
522 | support this (for instance because it is not visual), then rxvt-unicode |
501 | will continue without an input method. |
523 | will continue without an input method. |
502 | |
524 | |
503 | In this case either do not specify a preeditStyle or specify more than |
525 | In this case either do not specify a preeditType or specify more than |
504 | one pre-edit style, such as OverTheSpot,Root,None. |
526 | one pre-edit style, such as OverTheSpot,Root,None. |
505 | |
527 | |
506 | If it still doesn't work, then maybe your input method doesn't support |
528 | 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 |
529 | compose sequences - to fall back to the built-in one, make sure you |
508 | don't specify an input method via "-im" or "XMODIFIERS". |
530 | don't specify an input method via "-im" or "XMODIFIERS". |
… | |
… | |
532 | It is possible to toggle between "^H" and "^?" with the DECBKM private |
554 | It is possible to toggle between "^H" and "^?" with the DECBKM private |
533 | mode: |
555 | mode: |
534 | |
556 | |
535 | # use Backspace = ^H |
557 | # use Backspace = ^H |
536 | $ stty erase ^H |
558 | $ stty erase ^H |
537 | $ echo -n "^[[?67h" |
559 | $ printf "\e[?67h" |
538 | |
560 | |
539 | # use Backspace = ^? |
561 | # use Backspace = ^? |
540 | $ stty erase ^? |
562 | $ stty erase ^? |
541 | $ echo -n "^[[?67l" |
563 | $ printf "\e[?67l" |
542 | |
564 | |
543 | This helps satisfy some of the Backspace discrepancies that occur, but |
565 | This helps satisfy some of the Backspace discrepancies that occur, but |
544 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
566 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
545 | properly reflects that. |
567 | properly reflects that. |
546 | |
568 | |
… | |
… | |
806 | See next entry. |
828 | See next entry. |
807 | |
829 | |
808 | I need a termcap file entry. |
830 | I need a termcap file entry. |
809 | 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 |
810 | systems still compile some programs using the long-obsoleted termcap |
832 | systems still compile some programs using the long-obsoleted termcap |
811 | 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 |
812 | for "rxvt-unicode". |
834 | "rxvt-unicode". |
813 | |
835 | |
814 | 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 |
815 | 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 |
816 | program like this: |
838 | program like this: |
817 | |
839 | |
… | |
… | |
840 | Why doesn't vim/emacs etc. make use of italic? |
862 | Why doesn't vim/emacs etc. make use of italic? |
841 | See next entry. |
863 | See next entry. |
842 | |
864 | |
843 | Why are the secondary screen-related options not working properly? |
865 | Why are the secondary screen-related options not working properly? |
844 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
866 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
845 | distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
867 | distributions break rxvt-unicode by setting "TERM" to "rxvt", which |
846 | setting "TERM" to "rxvt", which doesn't have these extra features. |
868 | doesn't have these extra features. Unfortunately, some of these |
847 | Unfortunately, some of these (most notably, again, Debian GNU/Linux) |
|
|
848 | furthermore fail to even install the "rxvt-unicode" terminfo file, so |
869 | furthermore fail to even install the "rxvt-unicode" terminfo file, so |
849 | 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 |
850 | 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 |
851 | this). |
872 | this). |
852 | |
873 | |
… | |
… | |
963 | For scim, use "@im=SCIM". You can see what input method servers are |
984 | For scim, use "@im=SCIM". You can see what input method servers are |
964 | running with this command: |
985 | running with this command: |
965 | |
986 | |
966 | xprop -root XIM_SERVERS |
987 | xprop -root XIM_SERVERS |
967 | |
988 | |
968 | |
|
|
969 | |
|
|
970 | My input method wants <some encoding> but I want UTF-8, what can I do? |
989 | My input method wants <some encoding> but I want UTF-8, what can I do? |
971 | You can specify separate locales for the input method and the rest of |
990 | You can specify separate locales for the input method and the rest of |
972 | the terminal, using the resource "imlocale": |
991 | the terminal, using the resource "imlocale": |
973 | |
992 | |
974 | URxvt.imlocale: ja_JP.EUC-JP |
993 | URxvt.imlocale: ja_JP.EUC-JP |
… | |
… | |
987 | cannot be completely avoided even if both sides cooperate. |
1006 | cannot be completely avoided even if both sides cooperate. |
988 | |
1007 | |
989 | 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. |
990 | |
1009 | |
991 | Operating Systems / Package Maintaining |
1010 | Operating Systems / Package Maintaining |
992 | I am using Debian GNU/Linux and have a problem... |
|
|
993 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
994 | patches that considerably change the behaviour of rxvt-unicode (but |
|
|
995 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
996 | the original rxvt-unicode author please download and install the genuine |
|
|
997 | version (<http://software.schmorp.de/pkg/rxvt-unicode.html>) and try to |
|
|
998 | reproduce the problem. If you cannot, chances are that the problems are |
|
|
999 | specific to Debian GNU/Linux, in which case it should be reported via |
|
|
1000 | the Debian Bug Tracking System (use "reportbug" to report the bug). |
|
|
1001 | |
|
|
1002 | For other problems that also affect the Debian package, you can and |
|
|
1003 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
1004 | bug in the Debian version and it serves as a reminder for other users |
|
|
1005 | that might encounter the same issue. |
|
|
1006 | |
|
|
1007 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1011 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1008 | You should build one binary with the default options. configure now |
1012 | You should build one binary with the default options. configure now |
1009 | enables most useful options, and the trend goes to making them |
1013 | enables most useful options, and the trend goes to making them |
1010 | runtime-switchable, too, so there is usually no drawback to enabling |
1014 | runtime-switchable, too, so there is usually no drawback to enabling |
1011 | them, except higher disk and possibly memory usage. The perl interpreter |
1015 | them, except higher disk and possibly memory usage. The perl interpreter |