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.56 by root, Tue Nov 4 23:00:43 2008 UTC

… …
2 Meta, Features & Commandline Issues 2 Meta, Features & Commandline Issues
3 My question isn't answered here, can I ask a human? 3 My question isn't answered here, can I ask a human?
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
8 I use Gentoo, and I have a problem...
9 There are three big problems with Gentoo Linux: first of all, most if
10 not all Gentoo systems are completely broken (missing or mismatched
11 header files, broken compiler etc. are just the tip of the iceberg);
12 secondly, the Gentoo maintainer thinks it is a good idea to add broken
13 patches to the code; and lastly, it should be called Gentoo GNU/Linux.
14
15 For these reasons, it is impossible to support rxvt-unicode on Gentoo.
16 Problems appearing on Gentoo systems will usually simply be ignored
17 unless they can be reproduced on non-Gentoo systems.
7 18
8 Does it support tabs, can I have a tabbed rxvt-unicode? 19 Does it support tabs, can I have a tabbed rxvt-unicode?
9 Beginning with version 7.3, there is a perl extension that implements a 20 Beginning with version 7.3, there is a perl extension that implements a
10 simple tabbed terminal. It is installed by default, so any of these 21 simple tabbed terminal. It is installed by default, so any of these
11 should give you tabs: 22 should give you tabs:
… …
42 53
43 How can I start urxvtd in a race-free way? 54 How can I start urxvtd in a race-free way?
44 Try "urxvtd -f -o", which tells urxvtd to open the display, create the 55 Try "urxvtd -f -o", which tells urxvtd to open the display, create the
45 listening socket and then fork. 56 listening socket and then fork.
46 57
47 How can I start urxvtd automatically when I run URXVT_NAME@@c? 58 How can I start urxvtd automatically when I run urxvtc?
48 If you want to start urxvtd automatically whenever you run urxvtc and 59 If you want to start urxvtd automatically whenever you run urxvtc and
49 the daemon isn't running yet, use this script: 60 the daemon isn't running yet, use this script:
50 61
51 #!/bin/sh 62 #!/bin/sh
52 urxvtc "$@" 63 urxvtc "$@"
… …
58 This tries to create a new terminal, and if fails with exit status 2, 69 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 70 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 71 re-run the command. Subsequent invocations of the script will re-use the
61 existing daemon. 72 existing daemon.
62 73
63 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. 74 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 75 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 76 "COLORTERM", so you can check and see if that is set. Note that several
66 programs, JED, slrn, Midnight Commander automatically check this 77 programs, JED, slrn, Midnight Commander automatically check this
67 variable to decide whether or not to use color. 78 variable to decide whether or not to use color.
68 79
… …
90 fi 101 fi
91 fi 102 fi
92 103
93 How do I compile the manual pages on my own? 104 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, 105 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 106 one that comes with pod2man, pod2text and pod2xhtml (from Pod::Xhtml).
96 subdirectory and enter "make alldoc". 107 Then go to the doc subdirectory and enter "make alldoc".
97 108
98 Isn't rxvt-unicode supposed to be small? Don't all those features bloat? 109 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 110 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 111 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 112 that the urxvt binary is larger (due to some encoding tables always
… …
108 98398 1664 24 15695 1824 rxvt --disable-everything 119 98398 1664 24 15695 1824 rxvt --disable-everything
109 188985 9048 66616 18222 1788 urxvt --disable-everything 120 188985 9048 66616 18222 1788 urxvt --disable-everything
110 121
111 When you "--enable-everything" (which *is* unfair, as this involves xft 122 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 123 and full locale/XIM support which are quite bloaty inside libX11 and my
113 libc), the two diverge, but not unreasnobaly so. 124 libc), the two diverge, but not unreasonably so.
114 125
115 text data bss drs rss filename 126 text data bss drs rss filename
116 163431 2152 24 20123 2060 rxvt --enable-everything 127 163431 2152 24 20123 2060 rxvt --enable-everything
117 1035683 49680 66648 29096 3680 urxvt --enable-everything 128 1035683 49680 66648 29096 3680 urxvt --enable-everything
118 129
… …
160 171
161 And here is rxvt-unicode: 172 And here is rxvt-unicode:
162 173
163 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 174 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
164 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) 175 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
165 libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) 176 libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
166 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) 177 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
167 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) 178 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
168 179
169 No large bloated libraries (of course, none were linked in statically), 180 No large bloated libraries (of course, none were linked in statically),
170 except maybe libX11 :) 181 except maybe libX11 :)
171 182
172 Rendering, Font & Look and Feel Issues 183 Rendering, Font & Look and Feel Issues
173 I can't get transparency working, what am I doing wrong? 184 I can't get transparency working, what am I doing wrong?
174 First of all, transparency isn't officially supported in rxvt-unicode, 185 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 186 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 187 if you can't get it working consider it a rite of passage: ... and you
177 rite of passage: ... and you failed. 188 failed.
178 189
179 Here are four ways to get transparency. Do read the manpage and option 190 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! 191 descriptions for the programs mentioned and rxvt-unicode. Really, do it!
181 192
182 1. Use inheritPixmap: 193 1. Use transparent mode:
183 194
184 Esetroot wallpaper.jpg 195 Esetroot wallpaper.jpg
185 urxvt -ip -tint red -sh 40 196 urxvt -tr -tint red -sh 40
186 197
187 That works. If you think it doesn't, you lack transparency and tinting 198 That works. If you think it doesn't, you lack transparency and tinting
188 support, or you are unable to read. 199 support, or you are unable to read.
189 200
190 2. Use a simple pixmap and emulate pseudo-transparency. This enables you 201 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 202 to use effects other than tinting and shading: Just shade/tint/whatever
192 your picture with gimp or any other tool: 203 your picture with gimp or any other tool:
193 204
194 convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm 205 convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
195 urxvt -pixmap background.xpm -pe automove-background 206 urxvt -pixmap "background.jpg;:root"
196 207
197 That works. If you think it doesn't, you lack XPM and Perl support, or 208 That works. If you think it doesn't, you lack AfterImage support, or you
198 you are unable to read. 209 are unable to read.
199 210
200 3. Use an ARGB visual: 211 3. Use an ARGB visual:
201 212
202 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc 213 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
203 214
204 This requires XFT support, and the support of your X-server. If that 215 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 216 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 217 there yet, no matter what they claim. Rxvt-Unicode contains the
207 neccessary bugfixes and workarounds for Xft and Xlib to make it work, 218 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. 219 that doesn't mean that your WM has the required kludges in place.
209 220
210 4. Use xcompmgr and let it do the job: 221 4. Use xcompmgr and let it do the job:
211 222
212 xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ 223 xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
213 -set _NET_WM_WINDOW_OPACITY 0xc0000000 224 -set _NET_WM_WINDOW_OPACITY 0xc0000000
… …
228 however: Xft fonts often draw glyphs larger than their acclaimed 239 however: Xft fonts often draw glyphs larger than their acclaimed
229 bounding box, and rxvt-unicode has no way of detecting this (the correct 240 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 241 way is to ask for the character bounding box, which unfortunately is
231 wrong in these cases). 242 wrong in these cases).
232 243
233 It's not clear (to me at least), wether this is a bug in Xft, freetype, 244 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 245 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 246 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. 247 work, you might be forced to use a different font.
237 248
238 All of this is not a problem when using X11 core fonts, as their 249 All of this is not a problem when using X11 core fonts, as their
… …
297 What's with this bold/blink stuff? 308 What's with this bold/blink stuff?
298 If no bold colour is set via "colorBD:", bold will invert text using the 309 If no bold colour is set via "colorBD:", bold will invert text using the
299 standard foreground colour. 310 standard foreground colour.
300 311
301 For the standard background colour, blinking will actually make the text 312 For the standard background colour, blinking will actually make the text
302 blink when compiled with "--enable-blinking". with standard colours. 313 blink when compiled with "--enable-text-blink". Without
303 Without "--enable-blinking", the blink attribute will be ignored. 314 "--enable-text-blink", the blink attribute will be ignored.
304 315
305 On ANSI colours, bold/blink attributes are used to set high-intensity 316 On ANSI colours, bold/blink attributes are used to set high-intensity
306 foreground/background colors. 317 foreground/background colors.
307 318
308 color0-7 are the low-intensity colors. 319 color0-7 are the low-intensity colors.
… …
409 has been designed yet). 420 has been designed yet).
410 421
411 Until then, you might get away with switching fonts at runtime (see "Can 422 Until then, you might get away with switching fonts at runtime (see "Can
412 I switch the fonts at runtime?" later in this document). 423 I switch the fonts at runtime?" later in this document).
413 424
425 How can I make mplayer display video correctly?
426 We are working on it, in the meantime, as a workaround, use something
427 like:
428
429 urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
430
414 Keyboard, Mouse & User Interaction 431 Keyboard, Mouse & User Interaction
415 The new selection selects pieces that are too big, how can I select single words? 432 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 433 If you want to select e.g. alphanumeric words, you can use the following
417 setting: 434 setting:
418 435
… …
424 To get a selection that is very similar to the old code, try this 441 To get a selection that is very similar to the old code, try this
425 pattern: 442 pattern:
426 443
427 URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) 444 URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
428 445
429 Please also note that the *LeftClick Shift-LeftClik* combination also 446 Please also note that the *LeftClick Shift-LeftClick* combination also
430 selects words like the old code. 447 selects words like the old code.
431 448
432 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? 449 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?
433 You can disable the perl extension completely by setting the 450 You can disable the perl extension completely by setting the
434 perl-ext-common resource to the empty string, which also keeps 451 perl-ext-common resource to the empty string, which also keeps
… …
457 circumstances, it will move your cursor around when you click into the 474 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, 475 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 476 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. 477 some cases during rlogin sessions, it fails to detect this properly.
461 478
462 You can permamently switch this feature off by disabling the "readline" 479 You can permanently switch this feature off by disabling the "readline"
463 extension: 480 extension:
464 481
465 URxvt.perl-ext-common: default,-readline 482 URxvt.perl-ext-common: default,-readline
466 483
467 My numerical keypad acts weird and generates differing output? 484 My numerical keypad acts weird and generates differing output?
468 Some Debian GNUL/Linux users seem to have this problem, although no 485 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 486 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 487 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 488 how this can happen are unknown, as "TERM=rxvt" should offer a
472 compatible keymap. See the answer to the previous question, and please 489 compatible keymap. See the answer to the previous question, and please
473 report if that helped. 490 report if that helped.
474 491
475 My Compose (Multi_key) key is no longer working. 492 My Compose (Multi_key) key is no longer working.
… …
496 that tcsh may use mouse reporting unless it otherwise specified. A quick 513 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 514 check is to see if cut/paste works when the Alt or Shift keys are
498 depressed. 515 depressed.
499 516
500 What's with the strange Backspace/Delete key behaviour? 517 What's with the strange Backspace/Delete key behaviour?
501 Assuming that the physical Backspace key corresponds to the BackSpace 518 Assuming that the physical Backspace key corresponds to the Backspace
502 keysym (not likely for Linux ... see the following question) there are 519 keysym (not likely for Linux ... see the following question) there are
503 two standard values that can be used for Backspace: "^H" and "^?". 520 two standard values that can be used for Backspace: "^H" and "^?".
504 521
505 Historically, either value is correct, but rxvt-unicode adopts the 522 Historically, either value is correct, but rxvt-unicode adopts the
506 debian policy of using "^?" when unsure, because it's the one only only 523 debian policy of using "^?" when unsure, because it's the one and only
507 correct choice :). 524 correct choice :).
508 525
509 Rxvt-unicode tries to inherit the current stty settings and uses the 526 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 527 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), 528 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 645 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 646 develop for myself mostly, so I actually use most of the extensions I
630 write. 647 write.
631 648
632 The selection stuff mainly makes the selection perl-error-message aware 649 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 650 and tells it to convert perl error messages into vi-commands to load the
634 relevant file and go tot he error line number. 651 relevant file and go tot he error line number.
635 652
636 URxvt.scrollstyle: plain 653 URxvt.scrollstyle: plain
637 URxvt.secondaryScroll: true 654 URxvt.secondaryScroll: true
638 655
639 As the documentation says: plain is the preferred scrollbar for the 656 As the documentation says: plain is the preferred scrollbar for the
640 author. The "secondaryScroll" confgiures urxvt to scroll in full-screen 657 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 658 apps, like screen, so lines scrolled out of screen end up in urxvt's
642 scrollback buffer. 659 scrollback buffer.
643 660
644 URxvt.background: #000000 661 URxvt.background: #000000
645 URxvt.foreground: gray90 662 URxvt.foreground: gray90
646 URxvt.color7: gray90 663 URxvt.color7: gray90
… …
697 urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 714 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 715 urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
699 urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 716 urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
700 717
701 I wrote rxvt-unicode to be able to specify fonts exactly. So don't be 718 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 719 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 720 the version from XFree-3.3, as XFree-4 replaced it by a totally
704 different font (different glyphs for ";" and many other harmless 721 different font (different glyphs for ";" and many other harmless
705 characters), while the second font is actually the "9x15bold" from 722 characters), while the second font is actually the "9x15bold" from
706 XFree4/XOrg. The bold version has less chars than the medium version, so 723 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 724 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 725 italic for comments and other stuff, which looks quite good with
709 Bitstream Vera anti-aliased. 726 Bitstream Vera anti-aliased.
710 727
711 Terminus is a quite bad font (many very wrong glyphs), but for most of 728 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 729 my purposes, it works, and gives a different look, as my normal
… …
763 Also consider the form resources have to use: 780 Also consider the form resources have to use:
764 781
765 URxvt.resource: value 782 URxvt.resource: value
766 783
767 If you want to use another form (there are lots of different ways of 784 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. 785 specifying resources), make sure you understand whether and why it
769 If unsure, use the form above. 786 works. If unsure, use the form above.
770 787
771 When I log-in to another system it tells me about missing terminfo data? 788 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 789 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 790 as that for xterm, or even rxvt (for which the same problem often
774 arises). 791 arises).
775 792
776 The correct solution for this problem is to install the terminfo, this 793 The correct solution for this problem is to install the terminfo, this
777 can be done like this (with ncurses' infocmp): 794 can be done like this (with ncurses' infocmp and works as user and
795 admin):
778 796
779 REMOTE=remotesystem.domain 797 REMOTE=remotesystem.domain
780 infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" 798 infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
781 799
782 ... or by installing rxvt-unicode normally on the remote system, 800 ... or by installing rxvt-unicode normally on the remote system,
801
802 One some systems you might need to set $TERMINFO to the full path of
803 $HOME/.terminfo for this to work.
783 804
784 If you cannot or do not want to do this, then you can simply set 805 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 806 "TERM=rxvt" or even "TERM=xterm", and live with the small number of
786 problems arising, which includes wrong keymapping, less and different 807 problems arising, which includes wrong keymapping, less and different
787 colours and some refresh errors in fullscreen applications. It's a nice 808 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 828 One reason you might want this is that some distributions or operating
808 systems still compile some programs using the long-obsoleted termcap 829 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 830 library (Fedora Core's bash is one example) and rely on a termcap entry
810 for "rxvt-unicode". 831 for "rxvt-unicode".
811 832
812 You could use rxvt's termcap entry with resonable results in many cases. 833 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 834 cases. You can also create a termcap entry by using terminfo's infocmp
814 like this: 835 program like this:
815 836
816 infocmp -C rxvt-unicode 837 infocmp -C rxvt-unicode
817 838
818 Or you could use this termcap entry, generated by the command above: 839 Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap,
819 840 generated by the command above.
820 rxvt-unicode|rxvt-unicode terminal (X Window System):\
821 :am:bw:eo:km:mi:ms:xn:xo:\
822 :co#80:it#8:li#24:lm#0:\
823 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
824 :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
825 :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
826 :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
827 :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
828 :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
829 :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
830 :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
831 :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
832 :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
833 :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
834 :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
835 :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
836 :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
837 :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
838 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
839 :vs=\E[?25h:
840 841
841 Why does "ls" no longer have coloured output? 842 Why does "ls" no longer have coloured output?
842 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 843 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to
843 decide wether a terminal has colour, but uses its own configuration 844 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 845 file. Needless to say, "rxvt-unicode" is not in its default file (among
845 with most other terminals supporting colour). Either add: 846 with most other terminals supporting colour). Either add:
846 847
847 TERM rxvt-unicode 848 TERM rxvt-unicode
848 849
… …
876 If you encounter strange problems like typing an accented character but 877 If you encounter strange problems like typing an accented character but
877 getting two unrelated other characters or similar, or if program output 878 getting two unrelated other characters or similar, or if program output
878 is subtly garbled, then you should check your locale settings. 879 is subtly garbled, then you should check your locale settings.
879 880
880 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 881 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 882 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 883 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 884 the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
884 going to work. 885 is not going to work, and is the most common cause for problems.
885 886
886 The best thing is to fix your startup environment, as you will likely 887 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 888 run into other problems. If nothing works you can try this in your
888 .profile. 889 .profile.
889 890
890 printf '\33]701;%s\007' "$LC_CTYPE" 891 printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
891 892
892 If this doesn't work, then maybe you use a "LC_CTYPE" specification not 893 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 894 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 895 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 896 it will complain loudly if it cannot set the locale). If it displays
… …
976 977
977 - Make sure your XIM server is actually running. 978 - Make sure your XIM server is actually running.
978 - Make sure the "XMODIFIERS" environment variable is set correctly when 979 - Make sure the "XMODIFIERS" environment variable is set correctly when
979 *starting* rxvt-unicode. 980 *starting* rxvt-unicode.
980 When you want to use e.g. kinput2, it must be set to "@im=kinput2". 981 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 982 For scim, use "@im=SCIM". You can see what input method servers are
982 running with this command: 983 running with this command:
983 984
984 xprop -root XIM_SERVERS 985 xprop -root XIM_SERVERS
985 986
986 987
… …
1023 that might encounter the same issue. 1024 that might encounter the same issue.
1024 1025
1025 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? 1026 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
1026 You should build one binary with the default options. configure now 1027 You should build one binary with the default options. configure now
1027 enables most useful options, and the trend goes to making them 1028 enables most useful options, and the trend goes to making them
1028 runtime-switchable, too, so there is usually no drawback to enbaling 1029 runtime-switchable, too, so there is usually no drawback to enabling
1029 them, except higher disk and possibly memory usage. The perl interpreter 1030 them, except higher disk and possibly memory usage. The perl interpreter
1030 should be enabled, as important functionality (menus, selection, likely 1031 should be enabled, as important functionality (menus, selection, likely
1031 more in the future) depends on it. 1032 more in the future) depends on it.
1032 1033
1033 You should not overwrite the "perl-ext-common" snd "perl-ext" resources 1034 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 1056 This forking is done as the very first within main(), which is very
1056 early and reduces possible bugs to initialisation code run before 1057 early and reduces possible bugs to initialisation code run before
1057 main(), or things like the dynamic loader of your system, which should 1058 main(), or things like the dynamic loader of your system, which should
1058 result in very little risk. 1059 result in very little risk.
1059 1060
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. 1061 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 1062 Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in
1069 your compile environment, or an implementation that implements it, 1063 your compile environment, or an implementation that implements it,
1070 wether it defines the symbol or not. "__STDC_ISO_10646__" requires that 1064 whether it defines the symbol or not. "__STDC_ISO_10646__" requires that
1071 wchar_t is represented as unicode. 1065 wchar_t is represented as unicode.
1072 1066
1073 As you might have guessed, FreeBSD does neither define this symobl nor 1067 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 1068 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. 1069 wchar_t. This is, of course, completely fine with respect to standards.
1076 1070
1077 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and 1071 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. 1072 "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t).
1079 1073
1080 "__STDC_ISO_10646__" is the only sane way to support multi-language apps 1074 "__STDC_ISO_10646__" is the only sane way to support multi-language apps
1081 in an OS, as using a locale-dependent (and non-standardized) 1075 in an OS, as using a locale-dependent (and non-standardized)
1082 representation of wchar_t makes it impossible to convert between wchar_t 1076 representation of wchar_t makes it impossible to convert between wchar_t
1083 (as used by X11 and your applications) and any other encoding without 1077 (as used by X11 and your applications) and any other encoding without
… …
1093 1087
1094 The rxvt-unicode author insists that the right way to fix this is in the 1088 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 1089 system libraries once and for all, instead of forcing every app to carry
1096 complete replacements for them :) 1090 complete replacements for them :)
1097 1091
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? 1092 How can I use rxvt-unicode under cygwin?
1103 rxvt-unicode should compile and run out of the box on cygwin, using the 1093 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 1094 X11 libraries that come with cygwin. libW11 emulation is no longer
1105 supported (and makes no sense, either, as it only supported a single 1095 supported (and makes no sense, either, as it only supported a single
1106 font). I recommend starting the X-server in "-multiwindow" or 1096 font). I recommend starting the X-server in "-multiwindow" or
… …
1109 1099
1110 At the time of this writing, cygwin didn't seem to support any 1100 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 1101 multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
1112 likely limited to 8-bit encodings. 1102 likely limited to 8-bit encodings.
1113 1103
1104 Character widths are not correct.
1105 urxvt uses the system wcwidth function to know the information about the
1106 width of characters, so on systems with incorrect locale data you will
1107 likely get bad results. Two notorious examples are Solaris 9, where
1108 single-width characters like U+2514 are reported as double-width, and
1109 Darwin 8, where combining chars are reported having width 1.
1110
1111 The solution is to upgrade your system or switch to a better one. A
1112 possibly working workaround is to use a wcwidth implementation like
1113
1114 http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
1115

Diff Legend

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