ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/README.FAQ
(Generate patch)

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.42 by root, Thu Jul 6 19:43:21 2006 UTC vs.
Revision 1.48 by root, Tue Jun 26 00:40:18 2007 UTC

… …
42 42
43 How can I start urxvtd in a race-free way? 43 How can I start urxvtd in a race-free way?
44 Try "urxvtd -f -o", which tells urxvtd to open the display, create the 44 Try "urxvtd -f -o", which tells urxvtd to open the display, create the
45 listening socket and then fork. 45 listening socket and then fork.
46 46
47 How can I start urxvtd automatically when I run URXVT_NAME@@c? 47 How can I start urxvtd automatically when I run urxvtc?
48 If you want to start urxvtd automatically whenever you run urxvtc and 48 If you want to start urxvtd automatically whenever you run urxvtc and
49 the daemon isn't running yet, use this script: 49 the daemon isn't running yet, use this script:
50 50
51 #!/bin/sh 51 #!/bin/sh
52 urxvtc "$@" 52 urxvtc "$@"
… …
58 This tries to create a new terminal, and if fails with exit status 2, 58 This tries to create a new terminal, and if fails with exit status 2,
59 meaning it couldn't connect to the daemon, it will start the daemon and 59 meaning it couldn't connect to the daemon, it will start the daemon and
60 re-run the command. Subsequent invocations of the script will re-use the 60 re-run the command. Subsequent invocations of the script will re-use the
61 existing daemon. 61 existing daemon.
62 62
63 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. 63 How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
64 The original rxvt and rxvt-unicode always export the variable 64 The original rxvt and rxvt-unicode always export the variable
65 "COLORTERM", so you can check and see if that is set. Note that several 65 "COLORTERM", so you can check and see if that is set. Note that several
66 programs, JED, slrn, Midnight Commander automatically check this 66 programs, JED, slrn, Midnight Commander automatically check this
67 variable to decide whether or not to use color. 67 variable to decide whether or not to use color.
68 68
… …
90 fi 90 fi
91 fi 91 fi
92 92
93 How do I compile the manual pages on my own? 93 How do I compile the manual pages on my own?
94 You need to have a recent version of perl installed as /usr/bin/perl, 94 You need to have a recent version of perl installed as /usr/bin/perl,
95 one that comes with pod2man, pod2text and pod2html. Then go to the doc 95 one that comes with pod2man, pod2text and pod2xhtml (from Pod::XHTML).
96 subdirectory and enter "make alldoc". 96 Then go to the doc subdirectory and enter "make alldoc".
97 97
98 Isn't rxvt-unicode supposed to be small? Don't all those features bloat? 98 Isn't rxvt-unicode supposed to be small? Don't all those features bloat?
99 I often get asked about this, and I think, no, they didn't cause extra 99 I often get asked about this, and I think, no, they didn't cause extra
100 bloat. If you compare a minimal rxvt and a minimal urxvt, you can see 100 bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
101 that the urxvt binary is larger (due to some encoding tables always 101 that the urxvt binary is larger (due to some encoding tables always
… …
108 98398 1664 24 15695 1824 rxvt --disable-everything 108 98398 1664 24 15695 1824 rxvt --disable-everything
109 188985 9048 66616 18222 1788 urxvt --disable-everything 109 188985 9048 66616 18222 1788 urxvt --disable-everything
110 110
111 When you "--enable-everything" (which *is* unfair, as this involves xft 111 When you "--enable-everything" (which *is* unfair, as this involves xft
112 and full locale/XIM support which are quite bloaty inside libX11 and my 112 and full locale/XIM support which are quite bloaty inside libX11 and my
113 libc), the two diverge, but not unreasnobaly so. 113 libc), the two diverge, but not unreasonably so.
114 114
115 text data bss drs rss filename 115 text data bss drs rss filename
116 163431 2152 24 20123 2060 rxvt --enable-everything 116 163431 2152 24 20123 2060 rxvt --enable-everything
117 1035683 49680 66648 29096 3680 urxvt --enable-everything 117 1035683 49680 66648 29096 3680 urxvt --enable-everything
118 118
… …
162 162
163 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 163 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
164 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) 164 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
165 libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) 165 libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
166 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) 166 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
167 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) 167 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
168 168
169 No large bloated libraries (of course, none were linked in statically), 169 No large bloated libraries (of course, none were linked in statically),
170 except maybe libX11 :) 170 except maybe libX11 :)
171 171
172 Rendering, Font & Look and Feel Issues 172 Rendering, Font & Look and Feel Issues
… …
202 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc 202 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
203 203
204 This requires XFT support, and the support of your X-server. If that 204 This requires XFT support, and the support of your X-server. If that
205 doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't 205 doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
206 there yet, no matter what they claim. Rxvt-Unicode contains the 206 there yet, no matter what they claim. Rxvt-Unicode contains the
207 neccessary bugfixes and workarounds for Xft and Xlib to make it work, 207 necessary bugfixes and workarounds for Xft and Xlib to make it work, but
208 but that doesn't mean that your WM has the required kludges in place. 208 that doesn't mean that your WM has the required kludges in place.
209 209
210 4. Use xcompmgr and let it do the job: 210 4. Use xcompmgr and let it do the job:
211 211
212 xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ 212 xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
213 -set _NET_WM_WINDOW_OPACITY 0xc0000000 213 -set _NET_WM_WINDOW_OPACITY 0xc0000000
… …
228 however: Xft fonts often draw glyphs larger than their acclaimed 228 however: Xft fonts often draw glyphs larger than their acclaimed
229 bounding box, and rxvt-unicode has no way of detecting this (the correct 229 bounding box, and rxvt-unicode has no way of detecting this (the correct
230 way is to ask for the character bounding box, which unfortunately is 230 way is to ask for the character bounding box, which unfortunately is
231 wrong in these cases). 231 wrong in these cases).
232 232
233 It's not clear (to me at least), wether this is a bug in Xft, freetype, 233 It's not clear (to me at least), whether this is a bug in Xft, freetype,
234 or the respective font. If you encounter this problem you might try 234 or the respective font. If you encounter this problem you might try
235 using the "-lsp" option to give the font more height. If that doesn't 235 using the "-lsp" option to give the font more height. If that doesn't
236 work, you might be forced to use a different font. 236 work, you might be forced to use a different font.
237 237
238 All of this is not a problem when using X11 core fonts, as their 238 All of this is not a problem when using X11 core fonts, as their
… …
457 circumstances, it will move your cursor around when you click into the 457 circumstances, it will move your cursor around when you click into the
458 line that contains it. It tries hard not to do this at the wrong moment, 458 line that contains it. It tries hard not to do this at the wrong moment,
459 but when running a program that doesn't parse cursor movements or in 459 but when running a program that doesn't parse cursor movements or in
460 some cases during rlogin sessions, it fails to detect this properly. 460 some cases during rlogin sessions, it fails to detect this properly.
461 461
462 You can permamently switch this feature off by disabling the "readline" 462 You can permanently switch this feature off by disabling the "readline"
463 extension: 463 extension:
464 464
465 URxvt.perl-ext-common: default,-readline 465 URxvt.perl-ext-common: default,-readline
466 466
467 My numerical keypad acts weird and generates differing output? 467 My numerical keypad acts weird and generates differing output?
468 Some Debian GNUL/Linux users seem to have this problem, although no 468 Some Debian GNUL/Linux users seem to have this problem, although no
469 specific details were reported so far. It is possible that this is 469 specific details were reported so far. It is possible that this is
470 caused by the wrong "TERM" setting, although the details of wether and 470 caused by the wrong "TERM" setting, although the details of whether and
471 how this can happen are unknown, as "TERM=rxvt" should offer a 471 how this can happen are unknown, as "TERM=rxvt" should offer a
472 compatible keymap. See the answer to the previous question, and please 472 compatible keymap. See the answer to the previous question, and please
473 report if that helped. 473 report if that helped.
474 474
475 My Compose (Multi_key) key is no longer working. 475 My Compose (Multi_key) key is no longer working.
… …
496 that tcsh may use mouse reporting unless it otherwise specified. A quick 496 that tcsh may use mouse reporting unless it otherwise specified. A quick
497 check is to see if cut/paste works when the Alt or Shift keys are 497 check is to see if cut/paste works when the Alt or Shift keys are
498 depressed. 498 depressed.
499 499
500 What's with the strange Backspace/Delete key behaviour? 500 What's with the strange Backspace/Delete key behaviour?
501 Assuming that the physical Backspace key corresponds to the BackSpace 501 Assuming that the physical Backspace key corresponds to the Backspace
502 keysym (not likely for Linux ... see the following question) there are 502 keysym (not likely for Linux ... see the following question) there are
503 two standard values that can be used for Backspace: "^H" and "^?". 503 two standard values that can be used for Backspace: "^H" and "^?".
504 504
505 Historically, either value is correct, but rxvt-unicode adopts the 505 Historically, either value is correct, but rxvt-unicode adopts the
506 debian policy of using "^?" when unsure, because it's the one only only 506 debian policy of using "^?" when unsure, because it's the one and only
507 correct choice :). 507 correct choice :).
508 508
509 Rxvt-unicode tries to inherit the current stty settings and uses the 509 Rxvt-unicode tries to inherit the current stty settings and uses the
510 value of `erase' to guess the value for backspace. If rxvt-unicode 510 value of `erase' to guess the value for backspace. If rxvt-unicode
511 wasn't started from a terminal (say, from a menu or by remote shell), 511 wasn't started from a terminal (say, from a menu or by remote shell),
… …
628 directory and also tells urxvt to use a large number of extensions. I 628 directory and also tells urxvt to use a large number of extensions. I
629 develop for myself mostly, so I actually use most of the extensions I 629 develop for myself mostly, so I actually use most of the extensions I
630 write. 630 write.
631 631
632 The selection stuff mainly makes the selection perl-error-message aware 632 The selection stuff mainly makes the selection perl-error-message aware
633 and tells it to convert pelr error mssages into vi-commands to load the 633 and tells it to convert perl error messages into vi-commands to load the
634 relevant file and go tot he error line number. 634 relevant file and go tot he error line number.
635 635
636 URxvt.scrollstyle: plain 636 URxvt.scrollstyle: plain
637 URxvt.secondaryScroll: true 637 URxvt.secondaryScroll: true
638 638
639 As the documentation says: plain is the preferred scrollbar for the 639 As the documentation says: plain is the preferred scrollbar for the
640 author. The "secondaryScroll" confgiures urxvt to scroll in full-screen 640 author. The "secondaryScroll" configures urxvt to scroll in full-screen
641 apps, like screen, so lines scorlled out of screen end up in urxvt's 641 apps, like screen, so lines scrolled out of screen end up in urxvt's
642 scrollback buffer. 642 scrollback buffer.
643 643
644 URxvt.background: #000000 644 URxvt.background: #000000
645 URxvt.foreground: gray90 645 URxvt.foreground: gray90
646 URxvt.color7: gray90 646 URxvt.color7: gray90
… …
697 urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 697 urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
698 urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 698 urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
699 urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 699 urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
700 700
701 I wrote rxvt-unicode to be able to specify fonts exactly. So don't be 701 I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
702 overwhelmed. A special note: the "9x15bold" mentioend above is actually 702 overwhelmed. A special note: the "9x15bold" mentioned above is actually
703 the version from XFree-3.3, as XFree-4 replaced it by a totally 703 the version from XFree-3.3, as XFree-4 replaced it by a totally
704 different font (different glyphs for ";" and many other harmless 704 different font (different glyphs for ";" and many other harmless
705 characters), while the second font is actually the "9x15bold" from 705 characters), while the second font is actually the "9x15bold" from
706 XFree4/XOrg. The bold version has less chars than the medium version, so 706 XFree4/XOrg. The bold version has less chars than the medium version, so
707 I use it for rare characters, too. Whene ditign sources with vim, I use 707 I use it for rare characters, too. When editing sources with vim, I use
708 italic for comments and other stuff, which looks quite good with 708 italic for comments and other stuff, which looks quite good with
709 Bitstream Vera anti-aliased. 709 Bitstream Vera anti-aliased.
710 710
711 Terminus is a quite bad font (many very wrong glyphs), but for most of 711 Terminus is a quite bad font (many very wrong glyphs), but for most of
712 my purposes, it works, and gives a different look, as my normal 712 my purposes, it works, and gives a different look, as my normal
… …
763 Also consider the form resources have to use: 763 Also consider the form resources have to use:
764 764
765 URxvt.resource: value 765 URxvt.resource: value
766 766
767 If you want to use another form (there are lots of different ways of 767 If you want to use another form (there are lots of different ways of
768 specifying resources), make sure you understand wether and why it works. 768 specifying resources), make sure you understand whether and why it
769 If unsure, use the form above. 769 works. If unsure, use the form above.
770 770
771 When I log-in to another system it tells me about missing terminfo data? 771 When I log-in to another system it tells me about missing terminfo data?
772 The terminal description used by rxvt-unicode is not as widely available 772 The terminal description used by rxvt-unicode is not as widely available
773 as that for xterm, or even rxvt (for which the same problem often 773 as that for xterm, or even rxvt (for which the same problem often
774 arises). 774 arises).
775 775
776 The correct solution for this problem is to install the terminfo, this 776 The correct solution for this problem is to install the terminfo, this
777 can be done like this (with ncurses' infocmp): 777 can be done like this (with ncurses' infocmp and works as user and
778 admin):
778 779
779 REMOTE=remotesystem.domain 780 REMOTE=remotesystem.domain
780 infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" 781 infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
781 782
782 ... or by installing rxvt-unicode normally on the remote system, 783 ... or by installing rxvt-unicode normally on the remote system,
784
785 One some systems you might need to set $TERMINFO to the full path of
786 $HOME/.terminfo for this to work.
783 787
784 If you cannot or do not want to do this, then you can simply set 788 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 789 "TERM=rxvt" or even "TERM=xterm", and live with the small number of
786 problems arising, which includes wrong keymapping, less and different 790 problems arising, which includes wrong keymapping, less and different
787 colours and some refresh errors in fullscreen applications. It's a nice 791 colours and some refresh errors in fullscreen applications. It's a nice
… …
807 One reason you might want this is that some distributions or operating 811 One reason you might want this is that some distributions or operating
808 systems still compile some programs using the long-obsoleted termcap 812 systems still compile some programs using the long-obsoleted termcap
809 library (Fedora Core's bash is one example) and rely on a termcap entry 813 library (Fedora Core's bash is one example) and rely on a termcap entry
810 for "rxvt-unicode". 814 for "rxvt-unicode".
811 815
812 You could use rxvt's termcap entry with resonable results in many cases. 816 You could use rxvt's termcap entry with reasonable results in many
813 You can also create a termcap entry by using terminfo's infocmp program 817 cases. You can also create a termcap entry by using terminfo's infocmp
814 like this: 818 program like this:
815 819
816 infocmp -C rxvt-unicode 820 infocmp -C rxvt-unicode
817 821
818 Or you could use this termcap entry, generated by the command above: 822 Or you could use this termcap entry, generated by the command above:
819 823
… …
838 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ 842 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
839 :vs=\E[?25h: 843 :vs=\E[?25h:
840 844
841 Why does "ls" no longer have coloured output? 845 Why does "ls" no longer have coloured output?
842 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 846 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to
843 decide wether a terminal has colour, but uses its own configuration 847 decide whether a terminal has colour, but uses its own configuration
844 file. Needless to say, "rxvt-unicode" is not in its default file (among 848 file. Needless to say, "rxvt-unicode" is not in its default file (among
845 with most other terminals supporting colour). Either add: 849 with most other terminals supporting colour). Either add:
846 850
847 TERM rxvt-unicode 851 TERM rxvt-unicode
848 852
… …
876 If you encounter strange problems like typing an accented character but 880 If you encounter strange problems like typing an accented character but
877 getting two unrelated other characters or similar, or if program output 881 getting two unrelated other characters or similar, or if program output
878 is subtly garbled, then you should check your locale settings. 882 is subtly garbled, then you should check your locale settings.
879 883
880 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 884 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the
881 programs. Often rxvt-unicode is started in the "C" locale, while the 885 programs running in it. Often rxvt-unicode is started in the "C" locale,
882 login script running within the rxvt-unicode window changes the locale 886 while the login script running within the rxvt-unicode window changes
883 to something else, e.g. "en_GB.UTF-8". Needless to say, this is not 887 the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
884 going to work. 888 is not going to work, and is the most common cause for problems.
885 889
886 The best thing is to fix your startup environment, as you will likely 890 The best thing is to fix your startup environment, as you will likely
887 run into other problems. If nothing works you can try this in your 891 run into other problems. If nothing works you can try this in your
888 .profile. 892 .profile.
889 893
890 printf '\33]701;%s\007' "$LC_CTYPE" 894 printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
891 895
892 If this doesn't work, then maybe you use a "LC_CTYPE" specification not 896 If this doesn't work, then maybe you use a "LC_CTYPE" specification not
893 supported on your systems. Some systems have a "locale" command which 897 supported on your systems. Some systems have a "locale" command which
894 displays this (also, "perl -e0" can be used to check locale settings, as 898 displays this (also, "perl -e0" can be used to check locale settings, as
895 it will complain loudly if it cannot set the locale). If it displays 899 it will complain loudly if it cannot set the locale). If it displays
… …
976 980
977 - Make sure your XIM server is actually running. 981 - Make sure your XIM server is actually running.
978 - Make sure the "XMODIFIERS" environment variable is set correctly when 982 - Make sure the "XMODIFIERS" environment variable is set correctly when
979 *starting* rxvt-unicode. 983 *starting* rxvt-unicode.
980 When you want to use e.g. kinput2, it must be set to "@im=kinput2". 984 When you want to use e.g. kinput2, it must be set to "@im=kinput2".
981 For scim, use "@im=SCIM". Youc an see what input method servers are 985 For scim, use "@im=SCIM". You can see what input method servers are
982 running with this command: 986 running with this command:
983 987
984 xprop -root XIM_SERVERS 988 xprop -root XIM_SERVERS
985 989
986 990 *
987 991
988 My input method wants <some encoding> but I want UTF-8, what can I do? 992 My input method wants <some encoding> but I want UTF-8, what can I do?
989 You can specify separate locales for the input method and the rest of 993 You can specify separate locales for the input method and the rest of
990 the terminal, using the resource "imlocale": 994 the terminal, using the resource "imlocale":
991 995
… …
1023 that might encounter the same issue. 1027 that might encounter the same issue.
1024 1028
1025 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? 1029 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
1026 You should build one binary with the default options. configure now 1030 You should build one binary with the default options. configure now
1027 enables most useful options, and the trend goes to making them 1031 enables most useful options, and the trend goes to making them
1028 runtime-switchable, too, so there is usually no drawback to enbaling 1032 runtime-switchable, too, so there is usually no drawback to enabling
1029 them, except higher disk and possibly memory usage. The perl interpreter 1033 them, except higher disk and possibly memory usage. The perl interpreter
1030 should be enabled, as important functionality (menus, selection, likely 1034 should be enabled, as important functionality (menus, selection, likely
1031 more in the future) depends on it. 1035 more in the future) depends on it.
1032 1036
1033 You should not overwrite the "perl-ext-common" snd "perl-ext" resources 1037 You should not overwrite the "perl-ext-common" snd "perl-ext" resources
… …
1065 #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) 1069 #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
1066 1070
1067 I am on FreeBSD and rxvt-unicode does not seem to work at all. 1071 I am on FreeBSD and rxvt-unicode does not seem to work at all.
1068 Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in 1072 Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in
1069 your compile environment, or an implementation that implements it, 1073 your compile environment, or an implementation that implements it,
1070 wether it defines the symbol or not. "__STDC_ISO_10646__" requires that 1074 whether it defines the symbol or not. "__STDC_ISO_10646__" requires that
1071 wchar_t is represented as unicode. 1075 wchar_t is represented as unicode.
1072 1076
1073 As you might have guessed, FreeBSD does neither define this symobl nor 1077 As you might have guessed, FreeBSD does neither define this symbol nor
1074 does it support it. Instead, it uses its own internal representation of 1078 does it support it. Instead, it uses its own internal representation of
1075 wchar_t. This is, of course, completely fine with respect to standards. 1079 wchar_t. This is, of course, completely fine with respect to standards.
1076 1080
1077 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and 1081 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and
1078 "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. 1082 "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines