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.63 by root, Mon Dec 13 16:47:27 2010 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
75xterm? I need this to decide about setting colours etc.
64 The original rxvt and rxvt-unicode always export the variable 76 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 77 "COLORTERM", so you can check and see if that is set. Note that several
66 programs, JED, slrn, Midnight Commander automatically check this 78 programs, JED, slrn, Midnight Commander automatically check this
67 variable to decide whether or not to use color. 79 variable to decide whether or not to use colour.
68 80
69 How do I set the correct, full IP address for the DISPLAY variable? 81 How do I set the correct, full IP address for the DISPLAY variable?
70 If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled 82 If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
71 insecure mode then it is possible to use the following shell script 83 insecure mode then it is possible to use the following shell script
72 snippets to correctly set the display. If your version of rxvt-unicode 84 snippets to correctly set the display. If your version of rxvt-unicode
90 fi 102 fi
91 fi 103 fi
92 104
93 How do I compile the manual pages on my own? 105 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, 106 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 107 one that comes with pod2man, pod2text and pod2xhtml (from Pod::Xhtml).
96 subdirectory and enter "make alldoc". 108 Then go to the doc subdirectory and enter "make alldoc".
97 109
98 Isn't rxvt-unicode supposed to be small? Don't all those features bloat? 110 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 111 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 112 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 113 that the urxvt binary is larger (due to some encoding tables always
108 98398 1664 24 15695 1824 rxvt --disable-everything 120 98398 1664 24 15695 1824 rxvt --disable-everything
109 188985 9048 66616 18222 1788 urxvt --disable-everything 121 188985 9048 66616 18222 1788 urxvt --disable-everything
110 122
111 When you "--enable-everything" (which *is* unfair, as this involves xft 123 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 124 and full locale/XIM support which are quite bloaty inside libX11 and my
113 libc), the two diverge, but not unreasnobaly so. 125 libc), the two diverge, but not unreasonably so.
114 126
115 text data bss drs rss filename 127 text data bss drs rss filename
116 163431 2152 24 20123 2060 rxvt --enable-everything 128 163431 2152 24 20123 2060 rxvt --enable-everything
117 1035683 49680 66648 29096 3680 urxvt --enable-everything 129 1035683 49680 66648 29096 3680 urxvt --enable-everything
118 130
146 the case of rxvt-unicode this hardly matters, as its portability limits 158 the case of rxvt-unicode this hardly matters, as its portability limits
147 are defined by things like X11, pseudo terminals, locale support and 159 are defined by things like X11, pseudo terminals, locale support and
148 unix domain sockets, which are all less portable than C++ itself. 160 unix domain sockets, which are all less portable than C++ itself.
149 161
150 Regarding the bloat, see the above question: It's easy to write programs 162 Regarding the bloat, see the above question: It's easy to write programs
151 in C that use gobs of memory, an certainly possible to write programs in 163 in C that use gobs of memory, and certainly possible to write programs
152 C++ that don't. C++ also often comes with large libraries, but this is 164 in C++ that don't. C++ also often comes with large libraries, but this
153 not necessarily the case with GCC. Here is what rxvt links against on my 165 is not necessarily the case with GCC. Here is what rxvt links against on
154 system with a minimal config: 166 my system with a minimal config:
155 167
156 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 168 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
157 libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) 169 libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
158 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) 170 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
159 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) 171 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
160 172
161 And here is rxvt-unicode: 173 And here is rxvt-unicode:
162 174
163 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 175 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
164 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) 176 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
165 libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) 177 libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
166 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) 178 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
167 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) 179 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
168 180
169 No large bloated libraries (of course, none were linked in statically), 181 No large bloated libraries (of course, none were linked in statically),
170 except maybe libX11 :) 182 except maybe libX11 :)
171 183
177 rite of passage: ... and you failed. 189 rite of passage: ... and you failed.
178 190
179 Here are four ways to get transparency. Do read the manpage and option 191 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! 192 descriptions for the programs mentioned and rxvt-unicode. Really, do it!
181 193
182 1. Use inheritPixmap: 194 1. Use transparent mode:
183 195
184 Esetroot wallpaper.jpg 196 Esetroot wallpaper.jpg
185 urxvt -ip -tint red -sh 40 197 urxvt -tr -tint red -sh 40
186 198
187 That works. If you think it doesn't, you lack transparency and tinting 199 That works. If you think it doesn't, you lack transparency and tinting
188 support, or you are unable to read. 200 support, or you are unable to read. This method requires that the
201 background-setting program sets the _XROOTPMAP_ID or ESETROOT_PMAP_ID
202 property. Compatible programs are Esetroot, hsetroot and feh.
189 203
190 2. Use a simple pixmap and emulate pseudo-transparency. This enables you 204 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 205 to use effects other than tinting and shading: Just shade/tint/whatever
192 your picture with gimp or any other tool: 206 your picture with gimp or any other tool:
193 207
194 convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm 208 convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
195 urxvt -pixmap background.xpm -pe automove-background 209 urxvt -pixmap "background.jpg;:root"
196 210
197 That works. If you think it doesn't, you lack XPM and Perl support, or 211 That works. If you think it doesn't, you lack libAfterImage or
198 you are unable to read. 212 GDK-PixBuf support, or you are unable to read.
199 213
200 3. Use an ARGB visual: 214 3. Use an ARGB visual:
201 215
202 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc 216 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
203 217
204 This requires XFT support, and the support of your X-server. If that 218 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 219 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 220 there yet, no matter what they claim. Rxvt-Unicode contains the
207 neccessary bugfixes and workarounds for Xft and Xlib to make it work, 221 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. 222 that doesn't mean that your WM has the required kludges in place.
209 223
210 4. Use xcompmgr and let it do the job: 224 4. Use xcompmgr and let it do the job:
211 225
212 xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ 226 xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
213 -set _NET_WM_WINDOW_OPACITY 0xc0000000 227 -set _NET_WM_WINDOW_OPACITY 0xc0000000
228 however: Xft fonts often draw glyphs larger than their acclaimed 242 however: Xft fonts often draw glyphs larger than their acclaimed
229 bounding box, and rxvt-unicode has no way of detecting this (the correct 243 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 244 way is to ask for the character bounding box, which unfortunately is
231 wrong in these cases). 245 wrong in these cases).
232 246
233 It's not clear (to me at least), wether this is a bug in Xft, freetype, 247 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 248 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 249 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. 250 work, you might be forced to use a different font.
237 251
238 All of this is not a problem when using X11 core fonts, as their 252 All of this is not a problem when using X11 core fonts, as their
297 What's with this bold/blink stuff? 311 What's with this bold/blink stuff?
298 If no bold colour is set via "colorBD:", bold will invert text using the 312 If no bold colour is set via "colorBD:", bold will invert text using the
299 standard foreground colour. 313 standard foreground colour.
300 314
301 For the standard background colour, blinking will actually make the text 315 For the standard background colour, blinking will actually make the text
302 blink when compiled with "--enable-blinking". with standard colours. 316 blink when compiled with "--enable-text-blink". Without
303 Without "--enable-blinking", the blink attribute will be ignored. 317 "--enable-text-blink", the blink attribute will be ignored.
304 318
305 On ANSI colours, bold/blink attributes are used to set high-intensity 319 On ANSI colours, bold/blink attributes are used to set high-intensity
306 foreground/background colors. 320 foreground/background colours.
307 321
308 color0-7 are the low-intensity colors. 322 color0-7 are the low-intensity colours.
309 323
310 color8-15 are the corresponding high-intensity colors. 324 color8-15 are the corresponding high-intensity colours.
311 325
312 I don't like the screen colors. How do I change them? 326 I don't like the screen colours. How do I change them?
313 You can change the screen colors at run-time using ~/.Xdefaults 327 You can change the screen colours at run-time using ~/.Xdefaults
314 resources (or as long-options). 328 resources (or as long-options).
315 329
316 Here are values that are supposed to resemble a VGA screen, including 330 Here are values that are supposed to resemble a VGA screen, including
317 the murky brown that passes for low-intensity yellow: 331 the murky brown that passes for low-intensity yellow:
318 332
332 URxvt.color12: #0000FF 346 URxvt.color12: #0000FF
333 URxvt.color13: #FF00FF 347 URxvt.color13: #FF00FF
334 URxvt.color14: #00FFFF 348 URxvt.color14: #00FFFF
335 URxvt.color15: #FFFFFF 349 URxvt.color15: #FFFFFF
336 350
337 And here is a more complete set of non-standard colors. 351 And here is a more complete set of non-standard colours.
338 352
339 URxvt.cursorColor: #dc74d1 353 URxvt.cursorColor: #dc74d1
340 URxvt.pointerColor: #dc74d1 354 URxvt.pointerColor: #dc74d1
341 URxvt.background: #0e0e0e 355 URxvt.background: #0e0e0e
342 URxvt.foreground: #4ad5e1 356 URxvt.foreground: #4ad5e1
409 has been designed yet). 423 has been designed yet).
410 424
411 Until then, you might get away with switching fonts at runtime (see "Can 425 Until then, you might get away with switching fonts at runtime (see "Can
412 I switch the fonts at runtime?" later in this document). 426 I switch the fonts at runtime?" later in this document).
413 427
428 How can I make mplayer display video correctly?
429 We are working on it, in the meantime, as a workaround, use something
430 like:
431
432 urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
433
414 Keyboard, Mouse & User Interaction 434 Keyboard, Mouse & User Interaction
415 The new selection selects pieces that are too big, how can I select single words? 435 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 436 If you want to select e.g. alphanumeric words, you can use the following
417 setting: 437 setting:
418 438
424 To get a selection that is very similar to the old code, try this 444 To get a selection that is very similar to the old code, try this
425 pattern: 445 pattern:
426 446
427 URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) 447 URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
428 448
429 Please also note that the *LeftClick Shift-LeftClik* combination also 449 Please also note that the *LeftClick Shift-LeftClick* combination also
430 selects words like the old code. 450 selects words like the old code.
431 451
432 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? 452 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 453 You can disable the perl extension completely by setting the
434 perl-ext-common resource to the empty string, which also keeps 454 perl-ext-common resource to the empty string, which also keeps
457 circumstances, it will move your cursor around when you click into the 477 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, 478 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 479 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. 480 some cases during rlogin sessions, it fails to detect this properly.
461 481
462 You can permamently switch this feature off by disabling the "readline" 482 You can permanently switch this feature off by disabling the "readline"
463 extension: 483 extension:
464 484
465 URxvt.perl-ext-common: default,-readline 485 URxvt.perl-ext-common: default,-readline
466 486
467 My numerical keypad acts weird and generates differing output? 487 My numerical keypad acts weird and generates differing output?
468 Some Debian GNUL/Linux users seem to have this problem, although no 488 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 489 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 490 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 491 how this can happen are unknown, as "TERM=rxvt" should offer a
472 compatible keymap. See the answer to the previous question, and please 492 compatible keymap. See the answer to the previous question, and please
473 report if that helped. 493 report if that helped.
474 494
475 My Compose (Multi_key) key is no longer working. 495 My Compose (Multi_key) key is no longer working.
481 will continue without an input method. 501 will continue without an input method.
482 502
483 In this case either do not specify a preeditStyle or specify more than 503 In this case either do not specify a preeditStyle or specify more than
484 one pre-edit style, such as OverTheSpot,Root,None. 504 one pre-edit style, such as OverTheSpot,Root,None.
485 505
506 If it still doesn't work, then maybe your input method doesn't support
507 compose sequences - to fall back to the built-in one, make sure you
508 don't specify an input method via "-im" or "XMODIFIERS".
509
486 I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 510 I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755
487 Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on 511 Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on
488 international keyboards) or simply use ISO 14755 support to your 512 international keyboards) or simply use ISO 14755 support to your
489 advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for 513 advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for
490 other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet 514 other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet
496 that tcsh may use mouse reporting unless it otherwise specified. A quick 520 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 521 check is to see if cut/paste works when the Alt or Shift keys are
498 depressed. 522 depressed.
499 523
500 What's with the strange Backspace/Delete key behaviour? 524 What's with the strange Backspace/Delete key behaviour?
501 Assuming that the physical Backspace key corresponds to the BackSpace 525 Assuming that the physical Backspace key corresponds to the Backspace
502 keysym (not likely for Linux ... see the following question) there are 526 keysym (not likely for Linux ... see the following question) there are
503 two standard values that can be used for Backspace: "^H" and "^?". 527 two standard values that can be used for Backspace: "^H" and "^?".
504 528
505 Historically, either value is correct, but rxvt-unicode adopts the 529 Historically, either value is correct, but rxvt-unicode adopts the
506 debian policy of using "^?" when unsure, because it's the one only only 530 debian policy of using "^?" when unsure, because it's the one and only
507 correct choice :). 531 correct choice :).
508 532
509 Rxvt-unicode tries to inherit the current stty settings and uses the 533 It is possible to toggle between "^H" and "^?" with the DECBKM private
510 value of `erase' to guess the value for backspace. If rxvt-unicode 534 mode:
511 wasn't started from a terminal (say, from a menu or by remote shell),
512 then the system value of `erase', which corresponds to CERASE in
513 <termios.h>, will be used (which may not be the same as your stty
514 setting).
515
516 For starting a new rxvt-unicode:
517 535
518 # use Backspace = ^H 536 # use Backspace = ^H
519 $ stty erase ^H 537 $ stty erase ^H
520 $ urxvt 538 $ echo -n "^[[?67h"
521 539
522 # use Backspace = ^? 540 # use Backspace = ^?
523 $ stty erase ^? 541 $ stty erase ^?
524 $ urxvt
525
526 Toggle with "ESC [ 36 h" / "ESC [ 36 l".
527
528 For an existing rxvt-unicode:
529
530 # use Backspace = ^H
531 $ stty erase ^H
532 $ echo -n "^[[36h"
533
534 # use Backspace = ^?
535 $ stty erase ^?
536 $ echo -n "^[[36l" 542 $ echo -n "^[[?67l"
537 543
538 This helps satisfy some of the Backspace discrepancies that occur, but 544 This helps satisfy some of the Backspace discrepancies that occur, but
539 if you use Backspace = "^H", make sure that the termcap/terminfo value 545 if you use Backspace = "^H", make sure that the termcap/terminfo value
540 properly reflects that. 546 properly reflects that.
541 547
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 to the 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
713 (Non-bold) font is already bold, and I want to see a difference between 719 (Non-bold) font is already bold, and I want to see a difference between
714 bold and normal fonts. 720 bold and normal fonts.
715 721
716 Please note that I used the "urxvt" instance name and not the "URxvt" 722 Please note that I used the "urxvt" instance name and not the "URxvt"
717 class name. Thats because I use different configs for different 723 class name. That is because I use different configs for different
718 purposes, for example, my IRC window is started with "-name IRC", and 724 purposes, for example, my IRC window is started with "-name IRC", and
719 uses these defaults: 725 uses these defaults:
720 726
721 IRC*title: IRC 727 IRC*title: IRC
722 IRC*geometry: 87x12+535+542 728 IRC*geometry: 87x12+535+542
726 IRC*boldFont: suxuseuro 732 IRC*boldFont: suxuseuro
727 IRC*colorBD: white 733 IRC*colorBD: white
728 IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 734 IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
729 IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 735 IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
730 736
731 "Alt-Shift-1" and "Alt-Shift-2" switch between two different font sizes. 737 "Alt-Ctrl-1" and "Alt-Ctrl-2" switch between two different font sizes.
732 "suxuseuro" allows me to keep an eye (and actually read) stuff while 738 "suxuseuro" allows me to keep an eye (and actually read) stuff while
733 keeping a very small window. If somebody pastes something complicated 739 keeping a very small window. If somebody pastes something complicated
734 (e.g. japanese), I temporarily switch to a larger font. 740 (e.g. japanese), I temporarily switch to a larger font.
735 741
736 The above is all in my ".Xdefaults" (I don't use ".Xresources" nor 742 The above is all in my ".Xdefaults" (I don't use ".Xresources" nor
737 "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" 743 "xrdb"). I also have some resources in a separate ".Xdefaults-hostname"
738 file for different hosts, for example, on ym main desktop, I use: 744 file for different hosts, for example, on my main desktop, I use:
739 745
740 URxvt.keysym.C-M-q: command:\033[3;5;5t 746 URxvt.keysym.C-M-q: command:\033[3;5;5t
741 URxvt.keysym.C-M-y: command:\033[3;5;606t 747 URxvt.keysym.C-M-y: command:\033[3;5;606t
742 URxvt.keysym.C-M-e: command:\033[3;1605;5t 748 URxvt.keysym.C-M-e: command:\033[3;1605;5t
743 URxvt.keysym.C-M-c: command:\033[3;1605;606t 749 URxvt.keysym.C-M-c: command:\033[3;1605;606t
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 by simply installing rxvt-unicode on the remote system as
784 well (in case you have a nice package manager ready), or you can install
785 the terminfo database manually like this (with ncurses infocmp. works as
786 user and root):
778 787
779 REMOTE=remotesystem.domain 788 REMOTE=remotesystem.domain
780 infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" 789 infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
781 790
782 ... or by installing rxvt-unicode normally on the remote system, 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
794 URxvt.termName: rxvt 804 URxvt.termName: rxvt
795 805
796 If you don't plan to use rxvt (quite common...) you could also replace 806 If you don't plan to use rxvt (quite common...) you could also replace
797 the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". 807 the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt".
798 808
809 nano fails with "Error opening terminal: rxvt-unicode"
810 This exceptionally confusing and useless error message is printed by
811 nano when it can't find the terminfo database. Nothing is wrong with
812 your terminal, read the previous answer for a solution.
813
799 "tic" outputs some error when compiling the terminfo entry. 814 "tic" outputs some error when compiling the terminfo entry.
800 Most likely it's the empty definition for "enacs=". Just replace it by 815 Most likely it's the empty definition for "enacs=". Just replace it by
801 "enacs=\E[0@" and try again. 816 "enacs=\E[0@" and try again.
802 817
803 "bash"'s readline does not work correctly under urxvt. 818 "bash"'s readline does not work correctly under urxvt.
807 One reason you might want this is that some distributions or operating 822 One reason you might want this is that some distributions or operating
808 systems still compile some programs using the long-obsoleted termcap 823 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 824 library (Fedora Core's bash is one example) and rely on a termcap entry
810 for "rxvt-unicode". 825 for "rxvt-unicode".
811 826
812 You could use rxvt's termcap entry with resonable results in many cases. 827 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 828 cases. You can also create a termcap entry by using terminfo's infocmp
814 like this: 829 program like this:
815 830
816 infocmp -C rxvt-unicode 831 infocmp -C rxvt-unicode
817 832
818 Or you could use this termcap entry, generated by the command above: 833 Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap,
819 834 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 835
841 Why does "ls" no longer have coloured output? 836 Why does "ls" no longer have coloured output?
842 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 837 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to
843 decide wether a terminal has colour, but uses its own configuration 838 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 839 file. Needless to say, "rxvt-unicode" is not in its default file (among
845 with most other terminals supporting colour). Either add: 840 with most other terminals supporting colour). Either add:
846 841
847 TERM rxvt-unicode 842 TERM rxvt-unicode
848 843
876 If you encounter strange problems like typing an accented character but 871 If you encounter strange problems like typing an accented character but
877 getting two unrelated other characters or similar, or if program output 872 getting two unrelated other characters or similar, or if program output
878 is subtly garbled, then you should check your locale settings. 873 is subtly garbled, then you should check your locale settings.
879 874
880 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 875 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 876 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 877 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 878 the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
884 going to work. 879 is not going to work, and is the most common cause for problems.
885 880
886 The best thing is to fix your startup environment, as you will likely 881 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 882 run into other problems. If nothing works you can try this in your
888 .profile. 883 .profile.
889 884
890 printf '\33]701;%s\007' "$LC_CTYPE" 885 printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too
891 886
892 If this doesn't work, then maybe you use a "LC_CTYPE" specification not 887 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 888 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 889 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 890 it will complain loudly if it cannot set the locale). If it displays
976 971
977 - Make sure your XIM server is actually running. 972 - Make sure your XIM server is actually running.
978 - Make sure the "XMODIFIERS" environment variable is set correctly when 973 - Make sure the "XMODIFIERS" environment variable is set correctly when
979 *starting* rxvt-unicode. 974 *starting* rxvt-unicode.
980 When you want to use e.g. kinput2, it must be set to "@im=kinput2". 975 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 976 For scim, use "@im=SCIM". You can see what input method servers are
982 running with this command: 977 running with this command:
983 978
984 xprop -root XIM_SERVERS 979 xprop -root XIM_SERVERS
985 980
986 981
1010 I am using Debian GNU/Linux and have a problem... 1005 I am using Debian GNU/Linux and have a problem...
1011 The Debian GNU/Linux package of rxvt-unicode in sarge contains large 1006 The Debian GNU/Linux package of rxvt-unicode in sarge contains large
1012 patches that considerably change the behaviour of rxvt-unicode (but 1007 patches that considerably change the behaviour of rxvt-unicode (but
1013 unfortunately this notice has been removed). Before reporting a bug to 1008 unfortunately this notice has been removed). Before reporting a bug to
1014 the original rxvt-unicode author please download and install the genuine 1009 the original rxvt-unicode author please download and install the genuine
1015 version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce 1010 version (<http://software.schmorp.de/pkg/rxvt-unicode.html>) and try to
1016 the problem. If you cannot, chances are that the problems are specific 1011 reproduce the problem. If you cannot, chances are that the problems are
1017 to Debian GNU/Linux, in which case it should be reported via the Debian 1012 specific to Debian GNU/Linux, in which case it should be reported via
1018 Bug Tracking System (use "reportbug" to report the bug). 1013 the Debian Bug Tracking System (use "reportbug" to report the bug).
1019 1014
1020 For other problems that also affect the Debian package, you can and 1015 For other problems that also affect the Debian package, you can and
1021 probably should use the Debian BTS, too, because, after all, it's also a 1016 probably should use the Debian BTS, too, because, after all, it's also a
1022 bug in the Debian version and it serves as a reminder for other users 1017 bug in the Debian version and it serves as a reminder for other users
1023 that might encounter the same issue. 1018 that might encounter the same issue.
1024 1019
1025 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? 1020 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
1026 You should build one binary with the default options. configure now 1021 You should build one binary with the default options. configure now
1027 enables most useful options, and the trend goes to making them 1022 enables most useful options, and the trend goes to making them
1028 runtime-switchable, too, so there is usually no drawback to enbaling 1023 runtime-switchable, too, so there is usually no drawback to enabling
1029 them, except higher disk and possibly memory usage. The perl interpreter 1024 them, except higher disk and possibly memory usage. The perl interpreter
1030 should be enabled, as important functionality (menus, selection, likely 1025 should be enabled, as important functionality (menus, selection, likely
1031 more in the future) depends on it. 1026 more in the future) depends on it.
1032 1027
1033 You should not overwrite the "perl-ext-common" snd "perl-ext" resources 1028 You should not overwrite the "perl-ext-common" and "perl-ext" resources
1034 system-wide (except maybe with "defaults"). This will result in useful 1029 system-wide (except maybe with "defaults"). This will result in useful
1035 behaviour. If your distribution aims at low memory, add an empty 1030 behaviour. If your distribution aims at low memory, add an empty
1036 "perl-ext-common" resource to the app-defaults file. This will keep the 1031 "perl-ext-common" resource to the app-defaults file. This will keep the
1037 perl interpreter disabled until the user enables it. 1032 perl interpreter disabled until the user enables it.
1038 1033
1055 This forking is done as the very first within main(), which is very 1050 This forking is done as the very first within main(), which is very
1056 early and reduces possible bugs to initialisation code run before 1051 early and reduces possible bugs to initialisation code run before
1057 main(), or things like the dynamic loader of your system, which should 1052 main(), or things like the dynamic loader of your system, which should
1058 result in very little risk. 1053 result in very little risk.
1059 1054
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. 1055 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 1056 Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in
1069 your compile environment, or an implementation that implements it, 1057 your compile environment, or an implementation that implements it,
1070 wether it defines the symbol or not. "__STDC_ISO_10646__" requires that 1058 whether it defines the symbol or not. "__STDC_ISO_10646__" requires that
1071 wchar_t is represented as unicode. 1059 wchar_t is represented as unicode.
1072 1060
1073 As you might have guessed, FreeBSD does neither define this symobl nor 1061 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 1062 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. 1063 wchar_t. This is, of course, completely fine with respect to standards.
1076 1064
1077 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and 1065 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. 1066 "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t).
1079 1067
1080 "__STDC_ISO_10646__" is the only sane way to support multi-language apps 1068 "__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) 1069 in an OS, as using a locale-dependent (and non-standardized)
1082 representation of wchar_t makes it impossible to convert between wchar_t 1070 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 1071 (as used by X11 and your applications) and any other encoding without
1093 1081
1094 The rxvt-unicode author insists that the right way to fix this is in the 1082 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 1083 system libraries once and for all, instead of forcing every app to carry
1096 complete replacements for them :) 1084 complete replacements for them :)
1097 1085
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? 1086 How can I use rxvt-unicode under cygwin?
1103 rxvt-unicode should compile and run out of the box on cygwin, using the 1087 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 1088 X11 libraries that come with cygwin. libW11 emulation is no longer
1105 supported (and makes no sense, either, as it only supported a single 1089 supported (and makes no sense, either, as it only supported a single
1106 font). I recommend starting the X-server in "-multiwindow" or 1090 font). I recommend starting the X-server in "-multiwindow" or
1109 1093
1110 At the time of this writing, cygwin didn't seem to support any 1094 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 1095 multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
1112 likely limited to 8-bit encodings. 1096 likely limited to 8-bit encodings.
1113 1097
1098 Character widths are not correct.
1099 urxvt uses the system wcwidth function to know the information about the
1100 width of characters, so on systems with incorrect locale data you will
1101 likely get bad results. Two notorious examples are Solaris 9, where
1102 single-width characters like U+2514 are reported as double-width, and
1103 Darwin 8, where combining chars are reported having width 1.
1104
1105 The solution is to upgrade your system or switch to a better one. A
1106 possibly working workaround is to use a wcwidth implementation like
1107
1108 http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
1109

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines