… | |
… | |
90 | This tries to create a new terminal, and if fails with exit status 2, |
90 | This tries to create a new terminal, and if fails with exit status 2, |
91 | meaning it couldn't connect to the daemon, it will start the daemon and |
91 | meaning it couldn't connect to the daemon, it will start the daemon and |
92 | re-run the command. Subsequent invocations of the script will re-use the |
92 | re-run the command. Subsequent invocations of the script will re-use the |
93 | existing daemon. |
93 | existing daemon. |
94 | |
94 | |
95 | =head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
95 | =head3 How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
96 | |
96 | |
97 | The original rxvt and rxvt-unicode always export the variable "COLORTERM", |
97 | The original rxvt and rxvt-unicode always export the variable "COLORTERM", |
98 | so you can check and see if that is set. Note that several programs, JED, |
98 | so you can check and see if that is set. Note that several programs, JED, |
99 | slrn, Midnight Commander automatically check this variable to decide |
99 | slrn, Midnight Commander automatically check this variable to decide |
100 | whether or not to use color. |
100 | whether or not to use color. |
… | |
… | |
144 | 98398 1664 24 15695 1824 rxvt --disable-everything |
144 | 98398 1664 24 15695 1824 rxvt --disable-everything |
145 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
145 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
146 | |
146 | |
147 | When you C<--enable-everything> (which I<is> unfair, as this involves xft |
147 | When you C<--enable-everything> (which I<is> unfair, as this involves xft |
148 | and full locale/XIM support which are quite bloaty inside libX11 and my |
148 | and full locale/XIM support which are quite bloaty inside libX11 and my |
149 | libc), the two diverge, but not unreasnobaly so. |
149 | libc), the two diverge, but not unreasonably so. |
150 | |
150 | |
151 | text data bss drs rss filename |
151 | text data bss drs rss filename |
152 | 163431 2152 24 20123 2060 rxvt --enable-everything |
152 | 163431 2152 24 20123 2060 rxvt --enable-everything |
153 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
153 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
154 | |
154 | |
… | |
… | |
241 | |
241 | |
242 | @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
242 | @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
243 | |
243 | |
244 | This requires XFT support, and the support of your X-server. If that |
244 | This requires XFT support, and the support of your X-server. If that |
245 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
245 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
246 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
246 | there yet, no matter what they claim. Rxvt-Unicode contains the necessary |
247 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
247 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
248 | doesn't mean that your WM has the required kludges in place. |
248 | doesn't mean that your WM has the required kludges in place. |
249 | |
249 | |
250 | 4. Use xcompmgr and let it do the job: |
250 | 4. Use xcompmgr and let it do the job: |
251 | |
251 | |
… | |
… | |
268 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
268 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
269 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
269 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
270 | ask for the character bounding box, which unfortunately is wrong in these |
270 | ask for the character bounding box, which unfortunately is wrong in these |
271 | cases). |
271 | cases). |
272 | |
272 | |
273 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
273 | It's not clear (to me at least), whether this is a bug in Xft, freetype, |
274 | or the respective font. If you encounter this problem you might try using |
274 | or the respective font. If you encounter this problem you might try using |
275 | the C<-lsp> option to give the font more height. If that doesn't work, you |
275 | the C<-lsp> option to give the font more height. If that doesn't work, you |
276 | might be forced to use a different font. |
276 | might be forced to use a different font. |
277 | |
277 | |
278 | All of this is not a problem when using X11 core fonts, as their bounding |
278 | All of this is not a problem when using X11 core fonts, as their bounding |
… | |
… | |
512 | circumstances, it will move your cursor around when you click into the |
512 | circumstances, it will move your cursor around when you click into the |
513 | line that contains it. It tries hard not to do this at the wrong moment, |
513 | line that contains it. It tries hard not to do this at the wrong moment, |
514 | but when running a program that doesn't parse cursor movements or in some |
514 | but when running a program that doesn't parse cursor movements or in some |
515 | cases during rlogin sessions, it fails to detect this properly. |
515 | cases during rlogin sessions, it fails to detect this properly. |
516 | |
516 | |
517 | You can permamently switch this feature off by disabling the C<readline> |
517 | You can permanently switch this feature off by disabling the C<readline> |
518 | extension: |
518 | extension: |
519 | |
519 | |
520 | URxvt.perl-ext-common: default,-readline |
520 | URxvt.perl-ext-common: default,-readline |
521 | |
521 | |
522 | =head3 My numerical keypad acts weird and generates differing output? |
522 | =head3 My numerical keypad acts weird and generates differing output? |
523 | |
523 | |
524 | Some Debian GNUL/Linux users seem to have this problem, although no |
524 | Some Debian GNUL/Linux users seem to have this problem, although no |
525 | specific details were reported so far. It is possible that this is caused |
525 | specific details were reported so far. It is possible that this is caused |
526 | by the wrong C<TERM> setting, although the details of wether and how |
526 | by the wrong C<TERM> setting, although the details of whether and how |
527 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
527 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
528 | keymap. See the answer to the previous question, and please report if that |
528 | keymap. See the answer to the previous question, and please report if that |
529 | helped. |
529 | helped. |
530 | |
530 | |
531 | =head3 My Compose (Multi_key) key is no longer working. |
531 | =head3 My Compose (Multi_key) key is no longer working. |
… | |
… | |
557 | depressed. |
557 | depressed. |
558 | |
558 | |
559 | =head3 What's with the strange Backspace/Delete key behaviour? |
559 | =head3 What's with the strange Backspace/Delete key behaviour? |
560 | |
560 | |
561 | Assuming that the physical Backspace key corresponds to the |
561 | Assuming that the physical Backspace key corresponds to the |
562 | BackSpace keysym (not likely for Linux ... see the following |
562 | Backspace keysym (not likely for Linux ... see the following |
563 | question) there are two standard values that can be used for |
563 | question) there are two standard values that can be used for |
564 | Backspace: C<^H> and C<^?>. |
564 | Backspace: C<^H> and C<^?>. |
565 | |
565 | |
566 | Historically, either value is correct, but rxvt-unicode adopts the debian |
566 | Historically, either value is correct, but rxvt-unicode adopts the debian |
567 | policy of using C<^?> when unsure, because it's the one only only correct |
567 | policy of using C<^?> when unsure, because it's the one only only correct |
… | |
… | |
694 | directory and also tells urxvt to use a large number of extensions. I |
694 | directory and also tells urxvt to use a large number of extensions. I |
695 | develop for myself mostly, so I actually use most of the extensions I |
695 | develop for myself mostly, so I actually use most of the extensions I |
696 | write. |
696 | write. |
697 | |
697 | |
698 | The selection stuff mainly makes the selection perl-error-message aware |
698 | The selection stuff mainly makes the selection perl-error-message aware |
699 | and tells it to convert pelr error mssages into vi-commands to load the |
699 | and tells it to convert perl error messages into vi-commands to load the |
700 | relevant file and go tot he error line number. |
700 | relevant file and go tot he error line number. |
701 | |
701 | |
702 | URxvt.scrollstyle: plain |
702 | URxvt.scrollstyle: plain |
703 | URxvt.secondaryScroll: true |
703 | URxvt.secondaryScroll: true |
704 | |
704 | |
705 | As the documentation says: plain is the preferred scrollbar for the |
705 | As the documentation says: plain is the preferred scrollbar for the |
706 | author. The C<secondaryScroll> confgiures urxvt to scroll in full-screen |
706 | author. The C<secondaryScroll> configures urxvt to scroll in full-screen |
707 | apps, like screen, so lines scorlled out of screen end up in urxvt's |
707 | apps, like screen, so lines scrolled out of screen end up in urxvt's |
708 | scrollback buffer. |
708 | scrollback buffer. |
709 | |
709 | |
710 | URxvt.background: #000000 |
710 | URxvt.background: #000000 |
711 | URxvt.foreground: gray90 |
711 | URxvt.foreground: gray90 |
712 | URxvt.color7: gray90 |
712 | URxvt.color7: gray90 |
… | |
… | |
763 | urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 |
763 | urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 |
764 | urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
764 | urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
765 | urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
765 | urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
766 | |
766 | |
767 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
767 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
768 | overwhelmed. A special note: the C<9x15bold> mentioend above is actually |
768 | overwhelmed. A special note: the C<9x15bold> mentioned above is actually |
769 | the version from XFree-3.3, as XFree-4 replaced it by a totally different |
769 | the version from XFree-3.3, as XFree-4 replaced it by a totally different |
770 | font (different glyphs for C<;> and many other harmless characters), |
770 | font (different glyphs for C<;> and many other harmless characters), |
771 | while the second font is actually the C<9x15bold> from XFree4/XOrg. The |
771 | while the second font is actually the C<9x15bold> from XFree4/XOrg. The |
772 | bold version has less chars than the medium version, so I use it for rare |
772 | bold version has less chars than the medium version, so I use it for rare |
773 | characters, too. Whene ditign sources with vim, I use italic for comments |
773 | characters, too. When editing sources with vim, I use italic for comments |
774 | and other stuff, which looks quite good with Bitstream Vera anti-aliased. |
774 | and other stuff, which looks quite good with Bitstream Vera anti-aliased. |
775 | |
775 | |
776 | Terminus is a quite bad font (many very wrong glyphs), but for most of my |
776 | Terminus is a quite bad font (many very wrong glyphs), but for most of my |
777 | purposes, it works, and gives a different look, as my normal (Non-bold) |
777 | purposes, it works, and gives a different look, as my normal (Non-bold) |
778 | font is already bold, and I want to see a difference between bold and |
778 | font is already bold, and I want to see a difference between bold and |
… | |
… | |
829 | Also consider the form resources have to use: |
829 | Also consider the form resources have to use: |
830 | |
830 | |
831 | URxvt.resource: value |
831 | URxvt.resource: value |
832 | |
832 | |
833 | If you want to use another form (there are lots of different ways of |
833 | If you want to use another form (there are lots of different ways of |
834 | specifying resources), make sure you understand wether and why it |
834 | specifying resources), make sure you understand whether and why it |
835 | works. If unsure, use the form above. |
835 | works. If unsure, use the form above. |
836 | |
836 | |
837 | =head3 When I log-in to another system it tells me about missing terminfo data? |
837 | =head3 When I log-in to another system it tells me about missing terminfo data? |
838 | |
838 | |
839 | The terminal description used by rxvt-unicode is not as widely available |
839 | The terminal description used by rxvt-unicode is not as widely available |
… | |
… | |
876 | One reason you might want this is that some distributions or operating |
876 | One reason you might want this is that some distributions or operating |
877 | systems still compile some programs using the long-obsoleted termcap |
877 | systems still compile some programs using the long-obsoleted termcap |
878 | library (Fedora Core's bash is one example) and rely on a termcap entry |
878 | library (Fedora Core's bash is one example) and rely on a termcap entry |
879 | for C<rxvt-unicode>. |
879 | for C<rxvt-unicode>. |
880 | |
880 | |
881 | You could use rxvt's termcap entry with resonable results in many cases. |
881 | You could use rxvt's termcap entry with reasonable results in many cases. |
882 | You can also create a termcap entry by using terminfo's infocmp program |
882 | You can also create a termcap entry by using terminfo's infocmp program |
883 | like this: |
883 | like this: |
884 | |
884 | |
885 | infocmp -C rxvt-unicode |
885 | infocmp -C rxvt-unicode |
886 | |
886 | |
… | |
… | |
908 | :vs=\E[?25h: |
908 | :vs=\E[?25h: |
909 | |
909 | |
910 | =head3 Why does C<ls> no longer have coloured output? |
910 | =head3 Why does C<ls> no longer have coloured output? |
911 | |
911 | |
912 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
912 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
913 | decide wether a terminal has colour, but uses its own configuration |
913 | decide whether a terminal has colour, but uses its own configuration |
914 | file. Needless to say, C<rxvt-unicode> is not in its default file (among |
914 | file. Needless to say, C<rxvt-unicode> is not in its default file (among |
915 | with most other terminals supporting colour). Either add: |
915 | with most other terminals supporting colour). Either add: |
916 | |
916 | |
917 | TERM rxvt-unicode |
917 | TERM rxvt-unicode |
918 | |
918 | |
… | |
… | |
1059 | =item - Make sure your XIM server is actually running. |
1059 | =item - Make sure your XIM server is actually running. |
1060 | |
1060 | |
1061 | =item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode. |
1061 | =item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode. |
1062 | |
1062 | |
1063 | When you want to use e.g. B<kinput2>, it must be set to |
1063 | When you want to use e.g. B<kinput2>, it must be set to |
1064 | C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. Youc an see what input |
1064 | C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. You can see what input |
1065 | method servers are running with this command: |
1065 | method servers are running with this command: |
1066 | |
1066 | |
1067 | xprop -root XIM_SERVERS |
1067 | xprop -root XIM_SERVERS |
1068 | |
1068 | |
1069 | =item |
1069 | =item |
… | |
… | |
1114 | |
1114 | |
1115 | =head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1115 | =head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1116 | |
1116 | |
1117 | You should build one binary with the default options. F<configure> |
1117 | You should build one binary with the default options. F<configure> |
1118 | now enables most useful options, and the trend goes to making them |
1118 | now enables most useful options, and the trend goes to making them |
1119 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
1119 | runtime-switchable, too, so there is usually no drawback to enabling them, |
1120 | except higher disk and possibly memory usage. The perl interpreter should |
1120 | except higher disk and possibly memory usage. The perl interpreter should |
1121 | be enabled, as important functionality (menus, selection, likely more in |
1121 | be enabled, as important functionality (menus, selection, likely more in |
1122 | the future) depends on it. |
1122 | the future) depends on it. |
1123 | |
1123 | |
1124 | You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources |
1124 | You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources |
… | |
… | |
1159 | |
1159 | |
1160 | =head3 I am on FreeBSD and rxvt-unicode does not seem to work at all. |
1160 | =head3 I am on FreeBSD and rxvt-unicode does not seem to work at all. |
1161 | |
1161 | |
1162 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
1162 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
1163 | in your compile environment, or an implementation that implements it, |
1163 | in your compile environment, or an implementation that implements it, |
1164 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
1164 | whether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
1165 | B<wchar_t> is represented as unicode. |
1165 | B<wchar_t> is represented as unicode. |
1166 | |
1166 | |
1167 | As you might have guessed, FreeBSD does neither define this symobl nor |
1167 | As you might have guessed, FreeBSD does neither define this symbol nor |
1168 | does it support it. Instead, it uses its own internal representation of |
1168 | does it support it. Instead, it uses its own internal representation of |
1169 | B<wchar_t>. This is, of course, completely fine with respect to standards. |
1169 | B<wchar_t>. This is, of course, completely fine with respect to standards. |
1170 | |
1170 | |
1171 | However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and |
1171 | However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and |
1172 | C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>. |
1172 | C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>. |