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.56 by root, Tue Nov 4 23:00:43 2008 UTC vs.
Revision 1.75 by root, Sun Nov 14 17:59:19 2021 UTC

1RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 1RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
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.libera.chat", 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 7
8 I use Gentoo, and I have a problem... 8 I use Gentoo, and I have a problem...
9 There are three big problems with Gentoo Linux: first of all, most if 9 There are two big problems with Gentoo Linux: first, most if not all
10 not all Gentoo systems are completely broken (missing or mismatched 10 Gentoo systems are completely broken (missing or mismatched header
11 header files, broken compiler etc. are just the tip of the iceberg); 11 files, broken compiler etc. are just the tip of the iceberg); secondly,
12 secondly, the Gentoo maintainer thinks it is a good idea to add broken 12 it should be called Gentoo GNU/Linux.
13 patches to the code; and lastly, it should be called Gentoo GNU/Linux.
14 13
15 For these reasons, it is impossible to support rxvt-unicode on Gentoo. 14 For these reasons, it is impossible to support rxvt-unicode on Gentoo.
16 Problems appearing on Gentoo systems will usually simply be ignored 15 Problems appearing on Gentoo systems will usually simply be ignored
17 unless they can be reproduced on non-Gentoo systems. 16 unless they can be reproduced on non-Gentoo systems.
18 17
… …
69 This tries to create a new terminal, and if fails with exit status 2, 68 This tries to create a new terminal, and if fails with exit status 2,
70 meaning it couldn't connect to the daemon, it will start the daemon and 69 meaning it couldn't connect to the daemon, it will start the daemon and
71 re-run the command. Subsequent invocations of the script will re-use the 70 re-run the command. Subsequent invocations of the script will re-use the
72 existing daemon. 71 existing daemon.
73 72
74 How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. 73 Another option is to use systemd socket-based activation (see
74 systemd.socket(5)). Here is an example of a service unit file and of a
75 socket unit file for the default socket path:
76
77 urxvtd.service
78 [Unit]
79 Description=urxvt terminal daemon
80 Requires=urxvtd.socket
81
82 [Service]
83 ExecStart=/usr/bin/urxvtd -o
84
85 urxvtd.socket
86 [Unit]
87 Description=urxvt terminal daemon socket
88
89 [Socket]
90 ListenStream=%h/.urxvt/urxvtd-%H
91
92 [Install]
93 WantedBy=sockets.target
94
95 How do I distinguish whether I'm running rxvt-unicode or a regular
96xterm? I need this to decide about setting colours etc.
75 The original rxvt and rxvt-unicode always export the variable 97 The original rxvt and rxvt-unicode always export the variable
76 "COLORTERM", so you can check and see if that is set. Note that several 98 "COLORTERM", so you can check and see if that is set. Note that several
77 programs, JED, slrn, Midnight Commander automatically check this 99 programs, JED, slrn, Midnight Commander automatically check this
78 variable to decide whether or not to use color. 100 variable to decide whether or not to use colour.
79 101
80 How do I set the correct, full IP address for the DISPLAY variable? 102 How do I set the correct, full IP address for the DISPLAY variable?
81 If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled 103 If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
82 insecure mode then it is possible to use the following shell script 104 insecure mode then it is possible to use the following shell script
83 snippets to correctly set the display. If your version of rxvt-unicode 105 snippets to correctly set the display. If your version of rxvt-unicode
… …
90 112
91 # Bourne/Korn/POSIX family of shells: 113 # Bourne/Korn/POSIX family of shells:
92 [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know 114 [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
93 if [ ${TERM:-foo} = xterm ]; then 115 if [ ${TERM:-foo} = xterm ]; then
94 stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not 116 stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
95 echo -n '^[Z' 117 printf "\eZ"
96 read term_id 118 read term_id
97 stty icanon echo 119 stty icanon echo
98 if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then 120 if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
99 echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string 121 printf '\e[7n' # query the rxvt we are in for the DISPLAY string
100 read DISPLAY # set it in our local shell 122 read DISPLAY # set it in our local shell
101 fi 123 fi
102 fi 124 fi
103 125
104 How do I compile the manual pages on my own? 126 How do I compile the manual pages on my own?
105 You need to have a recent version of perl installed as /usr/bin/perl, 127 You need to have a recent version of perl installed as /usr/bin/perl,
… …
157 the case of rxvt-unicode this hardly matters, as its portability limits 179 the case of rxvt-unicode this hardly matters, as its portability limits
158 are defined by things like X11, pseudo terminals, locale support and 180 are defined by things like X11, pseudo terminals, locale support and
159 unix domain sockets, which are all less portable than C++ itself. 181 unix domain sockets, which are all less portable than C++ itself.
160 182
161 Regarding the bloat, see the above question: It's easy to write programs 183 Regarding the bloat, see the above question: It's easy to write programs
162 in C that use gobs of memory, an certainly possible to write programs in 184 in C that use gobs of memory, and certainly possible to write programs
163 C++ that don't. C++ also often comes with large libraries, but this is 185 in C++ that don't. C++ also often comes with large libraries, but this
164 not necessarily the case with GCC. Here is what rxvt links against on my 186 is not necessarily the case with GCC. Here is what rxvt links against on
165 system with a minimal config: 187 my system with a minimal config:
166 188
167 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 189 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
168 libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) 190 libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
169 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) 191 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
170 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) 192 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
… …
180 No large bloated libraries (of course, none were linked in statically), 202 No large bloated libraries (of course, none were linked in statically),
181 except maybe libX11 :) 203 except maybe libX11 :)
182 204
183 Rendering, Font & Look and Feel Issues 205 Rendering, Font & Look and Feel Issues
184 I can't get transparency working, what am I doing wrong? 206 I can't get transparency working, what am I doing wrong?
185 First of all, please address all transparency related issues to Sasha 207 First of all, transparency isn't officially supported in rxvt-unicode,
186 Vasko at sasha@aftercode.net and do not bug the author about it. Also, 208 so you are mostly on your own. Do not bug the author about it (but you
187 if you can't get it working consider it a rite of passage: ... and you 209 may bug everybody else). Also, if you can't get it working consider it a
188 failed. 210 rite of passage: ... and you failed.
189 211
190 Here are four ways to get transparency. Do read the manpage and option 212 Here are four ways to get transparency. Do read the manpage and option
191 descriptions for the programs mentioned and rxvt-unicode. Really, do it! 213 descriptions for the programs mentioned and rxvt-unicode. Really, do it!
192 214
193 1. Use transparent mode: 215 1. Use pseudo-transparency:
194 216
195 Esetroot wallpaper.jpg 217 Esetroot wallpaper.jpg
196 urxvt -tr -tint red -sh 40 218 urxvt -tr -tint red -sh 40
197 219
198 That works. If you think it doesn't, you lack transparency and tinting 220 That works. If you think it doesn't, you lack transparency and tinting
199 support, or you are unable to read. 221 support, or you are unable to read. This method requires that the
222 background-setting program sets the _XROOTPMAP_ID or ESETROOT_PMAP_ID
223 property. Compatible programs are Esetroot, hsetroot and feh.
200 224
201 2. Use a simple pixmap and emulate pseudo-transparency. This enables you 225 2. Use a simple pixmap and emulate pseudo-transparency. This enables you
202 to use effects other than tinting and shading: Just shade/tint/whatever 226 to use effects other than tinting and shading: Just shade/tint/whatever
203 your picture with gimp or any other tool: 227 your picture with gimp or any other tool:
204 228
205 convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg 229 convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
206 urxvt -pixmap "background.jpg;:root" 230 urxvt -pixmap "background.jpg;:root"
207 231
208 That works. If you think it doesn't, you lack AfterImage support, or you 232 That works. If you think it doesn't, you lack GDK-PixBuf support, or you
209 are unable to read. 233 are unable to read.
210 234
211 3. Use an ARGB visual: 235 3. Use an ARGB visual:
212 236
213 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc 237 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
214 238
215 This requires XFT support, and the support of your X-server. If that 239 This requires XFT support, and the support of your X-server. If that
216 doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't 240 doesn't work for you, find a working composite manager or window
217 there yet, no matter what they claim. Rxvt-Unicode contains the 241 manager, both are required to support ARGB visuals for client windows.
218 necessary bugfixes and workarounds for Xft and Xlib to make it work, but
219 that doesn't mean that your WM has the required kludges in place.
220 242
221 4. Use xcompmgr and let it do the job: 243 4. Use xcompmgr and let it do the job:
222 244
223 xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ 245 xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
224 -set _NET_WM_WINDOW_OPACITY 0xc0000000 246 -set _NET_WM_WINDOW_OPACITY 0xc0000000
… …
312 For the standard background colour, blinking will actually make the text 334 For the standard background colour, blinking will actually make the text
313 blink when compiled with "--enable-text-blink". Without 335 blink when compiled with "--enable-text-blink". Without
314 "--enable-text-blink", the blink attribute will be ignored. 336 "--enable-text-blink", the blink attribute will be ignored.
315 337
316 On ANSI colours, bold/blink attributes are used to set high-intensity 338 On ANSI colours, bold/blink attributes are used to set high-intensity
317 foreground/background colors. 339 foreground/background colours.
318 340
319 color0-7 are the low-intensity colors. 341 color0-7 are the low-intensity colours.
320 342
321 color8-15 are the corresponding high-intensity colors. 343 color8-15 are the corresponding high-intensity colours.
322 344
323 I don't like the screen colors. How do I change them? 345 I don't like the screen colours. How do I change them?
324 You can change the screen colors at run-time using ~/.Xdefaults 346 You can change the screen colours at run-time using ~/.Xdefaults
325 resources (or as long-options). 347 resources (or as long-options).
326 348
327 Here are values that are supposed to resemble a VGA screen, including 349 Here are values that are supposed to resemble a VGA screen, including
328 the murky brown that passes for low-intensity yellow: 350 the murky brown that passes for low-intensity yellow:
329 351
… …
343 URxvt.color12: #0000FF 365 URxvt.color12: #0000FF
344 URxvt.color13: #FF00FF 366 URxvt.color13: #FF00FF
345 URxvt.color14: #00FFFF 367 URxvt.color14: #00FFFF
346 URxvt.color15: #FFFFFF 368 URxvt.color15: #FFFFFF
347 369
348 And here is a more complete set of non-standard colors. 370 And here is a more complete set of non-standard colours.
349 371
350 URxvt.cursorColor: #dc74d1 372 URxvt.cursorColor: #dc74d1
351 URxvt.pointerColor: #dc74d1 373 URxvt.pointerColor: #dc74d1
352 URxvt.background: #0e0e0e 374 URxvt.background: #0e0e0e
353 URxvt.foreground: #4ad5e1 375 URxvt.foreground: #4ad5e1
… …
426 We are working on it, in the meantime, as a workaround, use something 448 We are working on it, in the meantime, as a workaround, use something
427 like: 449 like:
428 450
429 urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...' 451 urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
430 452
453 Why is the cursor now blinking in emacs/vi/...?
454 This is likely caused by your editor/program's use of the "cvvis"
455 terminfo capability. Emacs uses it by default, as well as some versions
456 of vi and possibly other programs.
457
458 In emacs, you can switch that off by adding this to your ".emacs" file:
459
460 (setq visible-cursor nil)
461
462 For other programs, if they do not have an option, your have to remove
463 the "cvvis" capability from the terminfo description.
464
465 When urxvt first added the blinking cursor option, it didn't add a
466 "cvvis" capability, which served no purpose before. Version 9.21
467 introduced "cvvis" (and the ability to control blinking independent of
468 cursor shape) for compatibility with other terminals, which
469 traditionally use a blinking cursor for "cvvis". This also reflects the
470 intent of programs such as emacs, who expect "cvvis" to enable a
471 blinking cursor.
472
431 Keyboard, Mouse & User Interaction 473 Keyboard, Mouse & User Interaction
432 The new selection selects pieces that are too big, how can I select single words? 474 The new selection selects pieces that are too big, how can I select single words?
433 If you want to select e.g. alphanumeric words, you can use the following 475 If you want to select e.g. alphanumeric words, you can use the following
434 setting: 476 setting:
435 477
… …
460 URxvt.perl-ext-common: default,-selection-popup,-option-popup 502 URxvt.perl-ext-common: default,-selection-popup,-option-popup
461 503
462 This will keep the default extensions, but disable the two popup 504 This will keep the default extensions, but disable the two popup
463 extensions. Some extensions can also be configured, for example, 505 extensions. Some extensions can also be configured, for example,
464 scrollback search mode is triggered by M-s. You can move it to any other 506 scrollback search mode is triggered by M-s. You can move it to any other
465 combination either by setting the searchable-scrollback resource: 507 combination by adding a keysym resource that binds the desired
508 combination to the "start" action of "searchable-scrollback" and another
509 one that binds M-s to the "builtin:" action:
466 510
467 URxvt.searchable-scrollback: CM-s 511 URxvt.keysym.CM-s: searchable-scrollback:start
512 URxvt.keysym.M-s: builtin:
468 513
469 The cursor moves when selecting text in the current input line, how do I switch this off? 514 The cursor moves when selecting text in the current input line, how do I switch this off?
470 See next entry. 515 See next entry.
471 516
472 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? 517 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
… …
479 You can permanently switch this feature off by disabling the "readline" 524 You can permanently switch this feature off by disabling the "readline"
480 extension: 525 extension:
481 526
482 URxvt.perl-ext-common: default,-readline 527 URxvt.perl-ext-common: default,-readline
483 528
484 My numerical keypad acts weird and generates differing output? 529 My numeric keypad acts weird and generates differing output?
485 Some Debian GNUL/Linux users seem to have this problem, although no 530 Some Debian GNU/Linux users seem to have this problem, although no
486 specific details were reported so far. It is possible that this is 531 specific details were reported so far. It is possible that this is
487 caused by the wrong "TERM" setting, although the details of whether and 532 caused by the wrong "TERM" setting, although the details of whether and
488 how this can happen are unknown, as "TERM=rxvt" should offer a 533 how this can happen are unknown, as "TERM=rxvt" should offer a
489 compatible keymap. See the answer to the previous question, and please 534 compatible keymap. See the answer to the previous question, and please
490 report if that helped. 535 report if that helped.
491 536
492 My Compose (Multi_key) key is no longer working. 537 My Compose (Multi_key) key is no longer working.
493 The most common causes for this are that either your locale is not set 538 The most common causes for this are that either your locale is not set
494 correctly, or you specified a preeditStyle that is not supported by your 539 correctly, or you specified a preeditType that is not supported by your
495 input method. For example, if you specified OverTheSpot and your input 540 input method. For example, if you specified OverTheSpot and your input
496 method (e.g. the default input method handling Compose keys) does not 541 method (e.g. the default input method handling Compose keys) does not
497 support this (for instance because it is not visual), then rxvt-unicode 542 support this (for instance because it is not visual), then rxvt-unicode
498 will continue without an input method. 543 will continue without an input method.
499 544
500 In this case either do not specify a preeditStyle or specify more than 545 In this case either do not specify a preeditType or specify more than
501 one pre-edit style, such as OverTheSpot,Root,None. 546 one pre-edit style, such as OverTheSpot,Root,None.
547
548 If it still doesn't work, then maybe your input method doesn't support
549 compose sequences - to fall back to the built-in one, make sure you
550 don't specify an input method via "-im" or "XMODIFIERS".
502 551
503 I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 552 I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755
504 Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on 553 Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on
505 international keyboards) or simply use ISO 14755 support to your 554 international keyboards) or simply use ISO 14755 support to your
506 advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for 555 advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for
507 other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet 556 other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet
508 escape character and so on. 557 escape character and so on.
509 558
510 Mouse cut/paste suddenly no longer works. 559 Mouse cut/paste suddenly no longer works.
511 Make sure that mouse reporting is actually turned off since killing some 560 Make sure that mouse reporting is actually turned off since killing some
512 editors prematurely may leave the mouse in mouse report mode. I've heard 561 editors prematurely may leave it active. I've heard that tcsh may use
513 that tcsh may use mouse reporting unless it otherwise specified. A quick 562 mouse reporting unless it is otherwise specified. A quick check is to
514 check is to see if cut/paste works when the Alt or Shift keys are 563 see if cut/paste works when the Alt or Shift keys are pressed.
515 depressed.
516 564
517 What's with the strange Backspace/Delete key behaviour? 565 What's with the strange Backspace/Delete key behaviour?
518 Assuming that the physical Backspace key corresponds to the Backspace 566 Assuming that the physical Backspace key corresponds to the Backspace
519 keysym (not likely for Linux ... see the following question) there are 567 keysym (not likely for Linux ... see the following question) there are
520 two standard values that can be used for Backspace: "^H" and "^?". 568 two standard values that can be used for Backspace: "^H" and "^?".
521 569
522 Historically, either value is correct, but rxvt-unicode adopts the 570 Historically, either value is correct, but rxvt-unicode adopts the
523 debian policy of using "^?" when unsure, because it's the one and only 571 debian policy of using "^?" when unsure, because it's the one and only
524 correct choice :). 572 correct choice :).
525 573
526 Rxvt-unicode tries to inherit the current stty settings and uses the 574 It is possible to toggle between "^H" and "^?" with the DECBKM private
527 value of `erase' to guess the value for backspace. If rxvt-unicode 575 mode:
528 wasn't started from a terminal (say, from a menu or by remote shell),
529 then the system value of `erase', which corresponds to CERASE in
530 <termios.h>, will be used (which may not be the same as your stty
531 setting).
532
533 For starting a new rxvt-unicode:
534 576
535 # use Backspace = ^H 577 # use Backspace = ^H
536 $ stty erase ^H 578 $ stty erase ^H
537 $ urxvt 579 $ printf "\e[?67h"
538 580
539 # use Backspace = ^? 581 # use Backspace = ^?
540 $ stty erase ^? 582 $ stty erase ^?
541 $ urxvt 583 $ printf "\e[?67l"
542
543 Toggle with "ESC [ 36 h" / "ESC [ 36 l".
544
545 For an existing rxvt-unicode:
546
547 # use Backspace = ^H
548 $ stty erase ^H
549 $ echo -n "^[[36h"
550
551 # use Backspace = ^?
552 $ stty erase ^?
553 $ echo -n "^[[36l"
554 584
555 This helps satisfy some of the Backspace discrepancies that occur, but 585 This helps satisfy some of the Backspace discrepancies that occur, but
556 if you use Backspace = "^H", make sure that the termcap/terminfo value 586 if you use Backspace = "^H", make sure that the termcap/terminfo value
557 properly reflects that. 587 properly reflects that.
558 588
… …
574 use the `keysym' resource to alter the keystrings associated with 604 use the `keysym' resource to alter the keystrings associated with
575 keysyms. 605 keysyms.
576 606
577 Here's an example for a URxvt session started using "urxvt -name URxvt" 607 Here's an example for a URxvt session started using "urxvt -name URxvt"
578 608
609 URxvt.keysym.Prior: \033[5~
610 URxvt.keysym.Next: \033[6~
579 URxvt.keysym.Home: \033[1~ 611 URxvt.keysym.Home: \033[7~
580 URxvt.keysym.End: \033[4~ 612 URxvt.keysym.End: \033[8~
581 URxvt.keysym.C-apostrophe: \033<C-'>
582 URxvt.keysym.C-slash: \033<C-/>
583 URxvt.keysym.C-semicolon: \033<C-;>
584 URxvt.keysym.C-grave: \033<C-`>
585 URxvt.keysym.C-comma: \033<C-,>
586 URxvt.keysym.C-period: \033<C-.>
587 URxvt.keysym.C-0x60: \033<C-`>
588 URxvt.keysym.C-Tab: \033<C-Tab>
589 URxvt.keysym.C-Return: \033<C-Return>
590 URxvt.keysym.S-Return: \033<S-Return>
591 URxvt.keysym.S-space: \033<S-Space>
592 URxvt.keysym.M-Up: \033<M-Up> 613 URxvt.keysym.Up: \033[A
593 URxvt.keysym.M-Down: \033<M-Down> 614 URxvt.keysym.Down: \033[B
615 URxvt.keysym.Right: \033[C
594 URxvt.keysym.M-Left: \033<M-Left> 616 URxvt.keysym.Left: \033[D
595 URxvt.keysym.M-Right: \033<M-Right>
596 URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
597 URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
598 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
599 617
600 See some more examples in the documentation for the keysym resource. 618 See some more examples in the documentation for the keysym resource.
601 619
602 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map 620 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map
603 KP_Insert == Insert 621 KP_Insert == Insert
… …
620 time into customising your terminal. To get you started, here is the 638 time into customising your terminal. To get you started, here is the
621 author's .Xdefaults entries, with comments on what they do. It's 639 author's .Xdefaults entries, with comments on what they do. It's
622 certainly not *typical*, but what's typical... 640 certainly not *typical*, but what's typical...
623 641
624 URxvt.cutchars: "()*,<>[]{}|' 642 URxvt.cutchars: "()*,<>[]{}|'
625 URxvt.print-pipe: cat >/tmp/xxx 643 URxvt.print-pipe: cat >/some/path
626 644
627 These are just for testing stuff. 645 These are just for testing stuff.
628 646
629 URxvt.imLocale: ja_JP.UTF-8 647 URxvt.imLocale: ja_JP.UTF-8
630 URxvt.preeditType: OnTheSpot,None 648 URxvt.preeditType: OnTheSpot,None
… …
646 develop for myself mostly, so I actually use most of the extensions I 664 develop for myself mostly, so I actually use most of the extensions I
647 write. 665 write.
648 666
649 The selection stuff mainly makes the selection perl-error-message aware 667 The selection stuff mainly makes the selection perl-error-message aware
650 and tells it to convert perl error messages into vi-commands to load the 668 and tells it to convert perl error messages into vi-commands to load the
651 relevant file and go tot he error line number. 669 relevant file and go to the error line number.
652 670
653 URxvt.scrollstyle: plain 671 URxvt.scrollstyle: plain
654 URxvt.secondaryScroll: true 672 URxvt.secondaryScroll: true
655 673
656 As the documentation says: plain is the preferred scrollbar for the 674 As the documentation says: plain is the preferred scrollbar for the
… …
729 my purposes, it works, and gives a different look, as my normal 747 my purposes, it works, and gives a different look, as my normal
730 (Non-bold) font is already bold, and I want to see a difference between 748 (Non-bold) font is already bold, and I want to see a difference between
731 bold and normal fonts. 749 bold and normal fonts.
732 750
733 Please note that I used the "urxvt" instance name and not the "URxvt" 751 Please note that I used the "urxvt" instance name and not the "URxvt"
734 class name. Thats because I use different configs for different 752 class name. That is because I use different configs for different
735 purposes, for example, my IRC window is started with "-name IRC", and 753 purposes, for example, my IRC window is started with "-name IRC", and
736 uses these defaults: 754 uses these defaults:
737 755
738 IRC*title: IRC 756 IRC*title: IRC
739 IRC*geometry: 87x12+535+542 757 IRC*geometry: 87x12+535+542
… …
743 IRC*boldFont: suxuseuro 761 IRC*boldFont: suxuseuro
744 IRC*colorBD: white 762 IRC*colorBD: white
745 IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 763 IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
746 IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 764 IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
747 765
748 "Alt-Shift-1" and "Alt-Shift-2" switch between two different font sizes. 766 "Alt-Ctrl-1" and "Alt-Ctrl-2" switch between two different font sizes.
749 "suxuseuro" allows me to keep an eye (and actually read) stuff while 767 "suxuseuro" allows me to keep an eye (and actually read) stuff while
750 keeping a very small window. If somebody pastes something complicated 768 keeping a very small window. If somebody pastes something complicated
751 (e.g. japanese), I temporarily switch to a larger font. 769 (e.g. japanese), I temporarily switch to a larger font.
752 770
753 The above is all in my ".Xdefaults" (I don't use ".Xresources" nor 771 The above is all in my ".Xdefaults" (I don't use ".Xresources" nor
754 "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" 772 "xrdb"). I also have some resources in a separate ".Xdefaults-hostname"
755 file for different hosts, for example, on ym main desktop, I use: 773 file for different hosts, for example, on my main desktop, I use:
756 774
757 URxvt.keysym.C-M-q: command:\033[3;5;5t 775 URxvt.keysym.C-M-q: command:\033[3;5;5t
758 URxvt.keysym.C-M-y: command:\033[3;5;606t 776 URxvt.keysym.C-M-y: command:\033[3;5;606t
759 URxvt.keysym.C-M-e: command:\033[3;1605;5t 777 URxvt.keysym.C-M-e: command:\033[3;1605;5t
760 URxvt.keysym.C-M-c: command:\033[3;1605;606t 778 URxvt.keysym.C-M-c: command:\033[3;1605;606t
… …
789 The terminal description used by rxvt-unicode is not as widely available 807 The terminal description used by rxvt-unicode is not as widely available
790 as that for xterm, or even rxvt (for which the same problem often 808 as that for xterm, or even rxvt (for which the same problem often
791 arises). 809 arises).
792 810
793 The correct solution for this problem is to install the terminfo, this 811 The correct solution for this problem is to install the terminfo, this
794 can be done like this (with ncurses' infocmp and works as user and 812 can be done by simply installing rxvt-unicode on the remote system as
795 admin): 813 well (in case you have a nice package manager ready), or you can install
814 the terminfo database manually like this (with ncurses infocmp. works as
815 user and root):
796 816
797 REMOTE=remotesystem.domain 817 REMOTE=remotesystem.domain
798 infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" 818 infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
799
800 ... or by installing rxvt-unicode normally on the remote system,
801 819
802 One some systems you might need to set $TERMINFO to the full path of 820 One some systems you might need to set $TERMINFO to the full path of
803 $HOME/.terminfo for this to work. 821 $HOME/.terminfo for this to work.
804 822
805 If you cannot or do not want to do this, then you can simply set 823 If you cannot or do not want to do this, then you can simply set
… …
815 URxvt.termName: rxvt 833 URxvt.termName: rxvt
816 834
817 If you don't plan to use rxvt (quite common...) you could also replace 835 If you don't plan to use rxvt (quite common...) you could also replace
818 the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". 836 the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt".
819 837
838 nano fails with "Error opening terminal: rxvt-unicode"
839 This exceptionally confusing and useless error message is printed by
840 nano when it can't find the terminfo database. Nothing is wrong with
841 your terminal, read the previous answer for a solution.
842
820 "tic" outputs some error when compiling the terminfo entry. 843 "tic" outputs some error when compiling the terminfo entry.
821 Most likely it's the empty definition for "enacs=". Just replace it by 844 Most likely it's the empty definition for "enacs=". Just replace it by
822 "enacs=\E[0@" and try again. 845 "enacs=\E[0@" and try again.
823 846
824 "bash"'s readline does not work correctly under urxvt. 847 "bash"'s readline does not work correctly under urxvt.
825 See next entry. 848 See next entry.
826 849
827 I need a termcap file entry. 850 I need a termcap file entry.
828 One reason you might want this is that some distributions or operating 851 One reason you might want this is that some distributions or operating
829 systems still compile some programs using the long-obsoleted termcap 852 systems still compile some programs using the long-obsoleted termcap
830 library (Fedora Core's bash is one example) and rely on a termcap entry 853 library (Fedora's bash is one example) and rely on a termcap entry for
831 for "rxvt-unicode". 854 "rxvt-unicode".
832 855
833 You could use rxvt's termcap entry with reasonable results in many 856 You could use rxvt's termcap entry with reasonable results in many
834 cases. You can also create a termcap entry by using terminfo's infocmp 857 cases. You can also create a termcap entry by using terminfo's infocmp
835 program like this: 858 program like this:
836 859
… …
859 Why doesn't vim/emacs etc. make use of italic? 882 Why doesn't vim/emacs etc. make use of italic?
860 See next entry. 883 See next entry.
861 884
862 Why are the secondary screen-related options not working properly? 885 Why are the secondary screen-related options not working properly?
863 Make sure you are using "TERM=rxvt-unicode". Some pre-packaged 886 Make sure you are using "TERM=rxvt-unicode". Some pre-packaged
864 distributions (most notably Debian GNU/Linux) break rxvt-unicode by 887 distributions break rxvt-unicode by setting "TERM" to "rxvt", which
865 setting "TERM" to "rxvt", which doesn't have these extra features. 888 doesn't have these extra features. Unfortunately, some of these
866 Unfortunately, some of these (most notably, again, Debian GNU/Linux)
867 furthermore fail to even install the "rxvt-unicode" terminfo file, so 889 furthermore fail to even install the "rxvt-unicode" terminfo file, so
868 you will need to install it on your own (See the question When I log-in 890 you will need to install it on your own (See the question When I log-in
869 to another system it tells me about missing terminfo data? on how to do 891 to another system it tells me about missing terminfo data? on how to do
870 this). 892 this).
871 893
… …
982 For scim, use "@im=SCIM". You can see what input method servers are 1004 For scim, use "@im=SCIM". You can see what input method servers are
983 running with this command: 1005 running with this command:
984 1006
985 xprop -root XIM_SERVERS 1007 xprop -root XIM_SERVERS
986 1008
987
988
989 My input method wants <some encoding> but I want UTF-8, what can I do? 1009 My input method wants <some encoding> but I want UTF-8, what can I do?
990 You can specify separate locales for the input method and the rest of 1010 You can specify separate locales for the input method and the rest of
991 the terminal, using the resource "imlocale": 1011 the terminal, using the resource "imlocale":
992 1012
993 URxvt.imlocale: ja_JP.EUC-JP 1013 URxvt.imlocale: ja_JP.EUC-JP
… …
1006 cannot be completely avoided even if both sides cooperate. 1026 cannot be completely avoided even if both sides cooperate.
1007 1027
1008 So the only workaround is not to kill your Input Method Servers. 1028 So the only workaround is not to kill your Input Method Servers.
1009 1029
1010 Operating Systems / Package Maintaining 1030 Operating Systems / Package Maintaining
1011 I am using Debian GNU/Linux and have a problem...
1012 The Debian GNU/Linux package of rxvt-unicode in sarge contains large
1013 patches that considerably change the behaviour of rxvt-unicode (but
1014 unfortunately this notice has been removed). Before reporting a bug to
1015 the original rxvt-unicode author please download and install the genuine
1016 version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
1017 the problem. If you cannot, chances are that the problems are specific
1018 to Debian GNU/Linux, in which case it should be reported via the Debian
1019 Bug Tracking System (use "reportbug" to report the bug).
1020
1021 For other problems that also affect the Debian package, you can and
1022 probably should use the Debian BTS, too, because, after all, it's also a
1023 bug in the Debian version and it serves as a reminder for other users
1024 that might encounter the same issue.
1025
1026 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? 1031 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
1027 You should build one binary with the default options. configure now 1032 You should build one binary with the default options. configure now
1028 enables most useful options, and the trend goes to making them 1033 enables most useful options, and the trend goes to making them
1029 runtime-switchable, too, so there is usually no drawback to enabling 1034 runtime-switchable, too, so there is usually no drawback to enabling
1030 them, except higher disk and possibly memory usage. The perl interpreter 1035 them, except higher disk and possibly memory usage. The perl interpreter
1031 should be enabled, as important functionality (menus, selection, likely 1036 should be enabled, as important functionality (menus, selection, likely
1032 more in the future) depends on it. 1037 more in the future) depends on it.
1033 1038
1034 You should not overwrite the "perl-ext-common" snd "perl-ext" resources 1039 You should not overwrite the "perl-ext-common" and "perl-ext" resources
1035 system-wide (except maybe with "defaults"). This will result in useful 1040 system-wide (except maybe with "defaults"). This will result in useful
1036 behaviour. If your distribution aims at low memory, add an empty 1041 behaviour. If your distribution aims at low memory, add an empty
1037 "perl-ext-common" resource to the app-defaults file. This will keep the 1042 "perl-ext-common" resource to the app-defaults file. This will keep the
1038 perl interpreter disabled until the user enables it. 1043 perl interpreter disabled until the user enables it.
1039 1044

Diff Legend

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