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.51 by root, Mon Nov 19 12:02:35 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
… …
160 160
161 And here is rxvt-unicode: 161 And here is rxvt-unicode:
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
173 I can't get transparency working, what am I doing wrong? 173 I can't get transparency working, what am I doing wrong?
174 First of all, transparency isn't officially supported in rxvt-unicode, 174 First of all, please address all transparency related issues to Sasha
175 so you are mostly on your own. Do not bug the author about it (but you 175 Vasko at sasha@aftercode.net and do not bug the author about it. Also,
176 may bug everybody else). Also, if you can't get it working consider it a 176 if you can't get it working consider it a rite of passage: ... and you
177 rite of passage: ... and you failed. 177 failed.
178 178
179 Here are four ways to get transparency. Do read the manpage and option 179 Here are four ways to get transparency. Do read the manpage and option
180 descriptions for the programs mentioned and rxvt-unicode. Really, do it! 180 descriptions for the programs mentioned and rxvt-unicode. Really, do it!
181 181
182 1. Use inheritPixmap: 182 1. Use transparent mode:
183 183
184 Esetroot wallpaper.jpg 184 Esetroot wallpaper.jpg
185 urxvt -ip -tint red -sh 40 185 urxvt -tr -tint red -sh 40
186 186
187 That works. If you think it doesn't, you lack transparency and tinting 187 That works. If you think it doesn't, you lack transparency and tinting
188 support, or you are unable to read. 188 support, or you are unable to read.
189 189
190 2. Use a simple pixmap and emulate pseudo-transparency. This enables you 190 2. Use a simple pixmap and emulate pseudo-transparency. This enables you
191 to use effects other than tinting and shading: Just shade/tint/whatever 191 to use effects other than tinting and shading: Just shade/tint/whatever
192 your picture with gimp or any other tool: 192 your picture with gimp or any other tool:
193 193
194 convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm 194 convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
195 urxvt -pixmap background.xpm -pe automove-background 195 urxvt -pixmap "background.jpg;:root"
196 196
197 That works. If you think it doesn't, you lack XPM and Perl support, or 197 That works. If you think it doesn't, you lack AfterImage support, or you
198 you are unable to read. 198 are unable to read.
199 199
200 3. Use an ARGB visual: 200 3. Use an ARGB visual:
201 201
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
… …
409 has been designed yet). 409 has been designed yet).
410 410
411 Until then, you might get away with switching fonts at runtime (see "Can 411 Until then, you might get away with switching fonts at runtime (see "Can
412 I switch the fonts at runtime?" later in this document). 412 I switch the fonts at runtime?" later in this document).
413 413
414 How can I make mplayer display video correctly?
415 We are working on it, in the meantime, as a workaround, use something
416 like:
417
418 urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
419
414 Keyboard, Mouse & User Interaction 420 Keyboard, Mouse & User Interaction
415 The new selection selects pieces that are too big, how can I select single words? 421 The new selection selects pieces that are too big, how can I select single words?
416 If you want to select e.g. alphanumeric words, you can use the following 422 If you want to select e.g. alphanumeric words, you can use the following
417 setting: 423 setting:
418 424
… …
457 circumstances, it will move your cursor around when you click into the 463 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, 464 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 465 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. 466 some cases during rlogin sessions, it fails to detect this properly.
461 467
462 You can permamently switch this feature off by disabling the "readline" 468 You can permanently switch this feature off by disabling the "readline"
463 extension: 469 extension:
464 470
465 URxvt.perl-ext-common: default,-readline 471 URxvt.perl-ext-common: default,-readline
466 472
467 My numerical keypad acts weird and generates differing output? 473 My numerical keypad acts weird and generates differing output?
468 Some Debian GNUL/Linux users seem to have this problem, although no 474 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 475 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 476 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 477 how this can happen are unknown, as "TERM=rxvt" should offer a
472 compatible keymap. See the answer to the previous question, and please 478 compatible keymap. See the answer to the previous question, and please
473 report if that helped. 479 report if that helped.
474 480
475 My Compose (Multi_key) key is no longer working. 481 My Compose (Multi_key) key is no longer working.
… …
496 that tcsh may use mouse reporting unless it otherwise specified. A quick 502 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 503 check is to see if cut/paste works when the Alt or Shift keys are
498 depressed. 504 depressed.
499 505
500 What's with the strange Backspace/Delete key behaviour? 506 What's with the strange Backspace/Delete key behaviour?
501 Assuming that the physical Backspace key corresponds to the BackSpace 507 Assuming that the physical Backspace key corresponds to the Backspace
502 keysym (not likely for Linux ... see the following question) there are 508 keysym (not likely for Linux ... see the following question) there are
503 two standard values that can be used for Backspace: "^H" and "^?". 509 two standard values that can be used for Backspace: "^H" and "^?".
504 510
505 Historically, either value is correct, but rxvt-unicode adopts the 511 Historically, either value is correct, but rxvt-unicode adopts the
506 debian policy of using "^?" when unsure, because it's the one only only 512 debian policy of using "^?" when unsure, because it's the one and only
507 correct choice :). 513 correct choice :).
508 514
509 Rxvt-unicode tries to inherit the current stty settings and uses the 515 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 516 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), 517 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 634 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 635 develop for myself mostly, so I actually use most of the extensions I
630 write. 636 write.
631 637
632 The selection stuff mainly makes the selection perl-error-message aware 638 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 639 and tells it to convert perl error messages into vi-commands to load the
634 relevant file and go tot he error line number. 640 relevant file and go tot he error line number.
635 641
636 URxvt.scrollstyle: plain 642 URxvt.scrollstyle: plain
637 URxvt.secondaryScroll: true 643 URxvt.secondaryScroll: true
638 644
639 As the documentation says: plain is the preferred scrollbar for the 645 As the documentation says: plain is the preferred scrollbar for the
640 author. The "secondaryScroll" confgiures urxvt to scroll in full-screen 646 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 647 apps, like screen, so lines scrolled out of screen end up in urxvt's
642 scrollback buffer. 648 scrollback buffer.
643 649
644 URxvt.background: #000000 650 URxvt.background: #000000
645 URxvt.foreground: gray90 651 URxvt.foreground: gray90
646 URxvt.color7: gray90 652 URxvt.color7: gray90
… …
697 urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 703 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 704 urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
699 urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 705 urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
700 706
701 I wrote rxvt-unicode to be able to specify fonts exactly. So don't be 707 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 708 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 709 the version from XFree-3.3, as XFree-4 replaced it by a totally
704 different font (different glyphs for ";" and many other harmless 710 different font (different glyphs for ";" and many other harmless
705 characters), while the second font is actually the "9x15bold" from 711 characters), while the second font is actually the "9x15bold" from
706 XFree4/XOrg. The bold version has less chars than the medium version, so 712 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 713 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 714 italic for comments and other stuff, which looks quite good with
709 Bitstream Vera anti-aliased. 715 Bitstream Vera anti-aliased.
710 716
711 Terminus is a quite bad font (many very wrong glyphs), but for most of 717 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 718 my purposes, it works, and gives a different look, as my normal
… …
763 Also consider the form resources have to use: 769 Also consider the form resources have to use:
764 770
765 URxvt.resource: value 771 URxvt.resource: value
766 772
767 If you want to use another form (there are lots of different ways of 773 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. 774 specifying resources), make sure you understand whether and why it
769 If unsure, use the form above. 775 works. If unsure, use the form above.
770 776
771 When I log-in to another system it tells me about missing terminfo data? 777 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 778 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 779 as that for xterm, or even rxvt (for which the same problem often
774 arises). 780 arises).
775 781
776 The correct solution for this problem is to install the terminfo, this 782 The correct solution for this problem is to install the terminfo, this
777 can be done like this (with ncurses' infocmp): 783 can be done like this (with ncurses' infocmp and works as user and
784 admin):
778 785
779 REMOTE=remotesystem.domain 786 REMOTE=remotesystem.domain
780 infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" 787 infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
781 788
782 ... or by installing rxvt-unicode normally on the remote system, 789 ... or by installing rxvt-unicode normally on the remote system,
790
791 One some systems you might need to set $TERMINFO to the full path of
792 $HOME/.terminfo for this to work.
783 793
784 If you cannot or do not want to do this, then you can simply set 794 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 795 "TERM=rxvt" or even "TERM=xterm", and live with the small number of
786 problems arising, which includes wrong keymapping, less and different 796 problems arising, which includes wrong keymapping, less and different
787 colours and some refresh errors in fullscreen applications. It's a nice 797 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 817 One reason you might want this is that some distributions or operating
808 systems still compile some programs using the long-obsoleted termcap 818 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 819 library (Fedora Core's bash is one example) and rely on a termcap entry
810 for "rxvt-unicode". 820 for "rxvt-unicode".
811 821
812 You could use rxvt's termcap entry with resonable results in many cases. 822 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 823 cases. You can also create a termcap entry by using terminfo's infocmp
814 like this: 824 program like this:
815 825
816 infocmp -C rxvt-unicode 826 infocmp -C rxvt-unicode
817 827
818 Or you could use this termcap entry, generated by the command above: 828 Or you could use this termcap entry, generated by the command above:
819 829
… …
838 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ 848 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
839 :vs=\E[?25h: 849 :vs=\E[?25h:
840 850
841 Why does "ls" no longer have coloured output? 851 Why does "ls" no longer have coloured output?
842 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 852 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to
843 decide wether a terminal has colour, but uses its own configuration 853 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 854 file. Needless to say, "rxvt-unicode" is not in its default file (among
845 with most other terminals supporting colour). Either add: 855 with most other terminals supporting colour). Either add:
846 856
847 TERM rxvt-unicode 857 TERM rxvt-unicode
848 858
… …
876 If you encounter strange problems like typing an accented character but 886 If you encounter strange problems like typing an accented character but
877 getting two unrelated other characters or similar, or if program output 887 getting two unrelated other characters or similar, or if program output
878 is subtly garbled, then you should check your locale settings. 888 is subtly garbled, then you should check your locale settings.
879 889
880 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 890 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 891 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 892 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 893 the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
884 going to work. 894 is not going to work, and is the most common cause for problems.
885 895
886 The best thing is to fix your startup environment, as you will likely 896 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 897 run into other problems. If nothing works you can try this in your
888 .profile. 898 .profile.
889 899
890 printf '\33]701;%s\007' "$LC_CTYPE" 900 printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
891 901
892 If this doesn't work, then maybe you use a "LC_CTYPE" specification not 902 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 903 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 904 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 905 it will complain loudly if it cannot set the locale). If it displays
… …
976 986
977 - Make sure your XIM server is actually running. 987 - Make sure your XIM server is actually running.
978 - Make sure the "XMODIFIERS" environment variable is set correctly when 988 - Make sure the "XMODIFIERS" environment variable is set correctly when
979 *starting* rxvt-unicode. 989 *starting* rxvt-unicode.
980 When you want to use e.g. kinput2, it must be set to "@im=kinput2". 990 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 991 For scim, use "@im=SCIM". You can see what input method servers are
982 running with this command: 992 running with this command:
983 993
984 xprop -root XIM_SERVERS 994 xprop -root XIM_SERVERS
985 995
986 996 *
987 997
988 My input method wants <some encoding> but I want UTF-8, what can I do? 998 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 999 You can specify separate locales for the input method and the rest of
990 the terminal, using the resource "imlocale": 1000 the terminal, using the resource "imlocale":
991 1001
… …
1023 that might encounter the same issue. 1033 that might encounter the same issue.
1024 1034
1025 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? 1035 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
1026 You should build one binary with the default options. configure now 1036 You should build one binary with the default options. configure now
1027 enables most useful options, and the trend goes to making them 1037 enables most useful options, and the trend goes to making them
1028 runtime-switchable, too, so there is usually no drawback to enbaling 1038 runtime-switchable, too, so there is usually no drawback to enabling
1029 them, except higher disk and possibly memory usage. The perl interpreter 1039 them, except higher disk and possibly memory usage. The perl interpreter
1030 should be enabled, as important functionality (menus, selection, likely 1040 should be enabled, as important functionality (menus, selection, likely
1031 more in the future) depends on it. 1041 more in the future) depends on it.
1032 1042
1033 You should not overwrite the "perl-ext-common" snd "perl-ext" resources 1043 You should not overwrite the "perl-ext-common" snd "perl-ext" resources
… …
1055 This forking is done as the very first within main(), which is very 1065 This forking is done as the very first within main(), which is very
1056 early and reduces possible bugs to initialisation code run before 1066 early and reduces possible bugs to initialisation code run before
1057 main(), or things like the dynamic loader of your system, which should 1067 main(), or things like the dynamic loader of your system, which should
1058 result in very little risk. 1068 result in very little risk.
1059 1069
1060 On Solaris 9, many line-drawing characters are too wide.
1061 Seems to be a known bug, read
1062 <http://nixdoc.net/files/forum/about34198.html>. Some people use the
1063 following ugly workaround to get non-double-wide-characters working:
1064
1065 #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
1066
1067 I am on FreeBSD and rxvt-unicode does not seem to work at all. 1070 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 1071 Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in
1069 your compile environment, or an implementation that implements it, 1072 your compile environment, or an implementation that implements it,
1070 wether it defines the symbol or not. "__STDC_ISO_10646__" requires that 1073 whether it defines the symbol or not. "__STDC_ISO_10646__" requires that
1071 wchar_t is represented as unicode. 1074 wchar_t is represented as unicode.
1072 1075
1073 As you might have guessed, FreeBSD does neither define this symobl nor 1076 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 1077 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. 1078 wchar_t. This is, of course, completely fine with respect to standards.
1076 1079
1077 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and 1080 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. 1081 "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.
… …
1093 1096
1094 The rxvt-unicode author insists that the right way to fix this is in the 1097 The rxvt-unicode author insists that the right way to fix this is in the
1095 system libraries once and for all, instead of forcing every app to carry 1098 system libraries once and for all, instead of forcing every app to carry
1096 complete replacements for them :) 1099 complete replacements for them :)
1097 1100
1098 I use Solaris 9 and it doesn't compile/work/etc.
1099 Try the diff in doc/solaris9.patch as a base. It fixes the worst
1100 problems with "wcwidth" and a compile problem.
1101
1102 How can I use rxvt-unicode under cygwin? 1101 How can I use rxvt-unicode under cygwin?
1103 rxvt-unicode should compile and run out of the box on cygwin, using the 1102 rxvt-unicode should compile and run out of the box on cygwin, using the
1104 X11 libraries that come with cygwin. libW11 emulation is no longer 1103 X11 libraries that come with cygwin. libW11 emulation is no longer
1105 supported (and makes no sense, either, as it only supported a single 1104 supported (and makes no sense, either, as it only supported a single
1106 font). I recommend starting the X-server in "-multiwindow" or 1105 font). I recommend starting the X-server in "-multiwindow" or
… …
1109 1108
1110 At the time of this writing, cygwin didn't seem to support any 1109 At the time of this writing, cygwin didn't seem to support any
1111 multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are 1110 multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
1112 likely limited to 8-bit encodings. 1111 likely limited to 8-bit encodings.
1113 1112
1113 Character widths are not correct.
1114 urxvt uses the system wcwidth function to know the information about the
1115 width of characters, so on systems with incorrect locale data you will
1116 likely get bad results. Two notorious examples are Solaris 9, where
1117 single-width characters like U+2514 are reported as double-width, and
1118 Darwin 8, where combining chars are reported having width 1.
1119
1120 The solution is to upgrade your system or switch to a better one. A
1121 possibly working workaround is to use a wcwidth implementation like
1122
1123 http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
1124

Diff Legend

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