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.57 by root, Wed Dec 30 06:14:03 2009 UTC vs.
Revision 1.73 by root, Fri May 14 13:47:43 2021 UTC

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 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 transparent mode:
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
312 For the standard background colour, blinking will actually make the text 336 For the standard background colour, blinking will actually make the text
313 blink when compiled with "--enable-text-blink". Without 337 blink when compiled with "--enable-text-blink". Without
314 "--enable-text-blink", the blink attribute will be ignored. 338 "--enable-text-blink", the blink attribute will be ignored.
315 339
316 On ANSI colours, bold/blink attributes are used to set high-intensity 340 On ANSI colours, bold/blink attributes are used to set high-intensity
317 foreground/background colors. 341 foreground/background colours.
318 342
319 color0-7 are the low-intensity colors. 343 color0-7 are the low-intensity colours.
320 344
321 color8-15 are the corresponding high-intensity colors. 345 color8-15 are the corresponding high-intensity colours.
322 346
323 I don't like the screen colors. How do I change them? 347 I don't like the screen colours. How do I change them?
324 You can change the screen colors at run-time using ~/.Xdefaults 348 You can change the screen colours at run-time using ~/.Xdefaults
325 resources (or as long-options). 349 resources (or as long-options).
326 350
327 Here are values that are supposed to resemble a VGA screen, including 351 Here are values that are supposed to resemble a VGA screen, including
328 the murky brown that passes for low-intensity yellow: 352 the murky brown that passes for low-intensity yellow:
329 353
343 URxvt.color12: #0000FF 367 URxvt.color12: #0000FF
344 URxvt.color13: #FF00FF 368 URxvt.color13: #FF00FF
345 URxvt.color14: #00FFFF 369 URxvt.color14: #00FFFF
346 URxvt.color15: #FFFFFF 370 URxvt.color15: #FFFFFF
347 371
348 And here is a more complete set of non-standard colors. 372 And here is a more complete set of non-standard colours.
349 373
350 URxvt.cursorColor: #dc74d1 374 URxvt.cursorColor: #dc74d1
351 URxvt.pointerColor: #dc74d1 375 URxvt.pointerColor: #dc74d1
352 URxvt.background: #0e0e0e 376 URxvt.background: #0e0e0e
353 URxvt.foreground: #4ad5e1 377 URxvt.foreground: #4ad5e1
426 We are working on it, in the meantime, as a workaround, use something 450 We are working on it, in the meantime, as a workaround, use something
427 like: 451 like:
428 452
429 urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...' 453 urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
430 454
455 Why is the cursor now blinking in emacs/vi/...?
456 This is likely caused by your editor/program's use of the "cvvis"
457 terminfo capability. Emacs uses it by default, as well as some versions
458 of vi and possibly other programs.
459
460 In emacs, you can switch that off by adding this to your ".emacs" file:
461
462 (setq visible-cursor nil)
463
464 For other programs, if they do not have an option, your have to remove
465 the "cvvis" capability from the terminfo description.
466
467 When urxvt first added the blinking cursor option, it didn't add a
468 "cvvis" capability, which served no purpose before. Version 9.21
469 introduced "cvvis" (and the ability to control blinking independent of
470 cursor shape) for compatibility with other terminals, which
471 traditionally use a blinking cursor for "cvvis". This also reflects the
472 intent of programs such as emacs, who expect "cvvis" to enable a
473 blinking cursor.
474
431 Keyboard, Mouse & User Interaction 475 Keyboard, Mouse & User Interaction
432 The new selection selects pieces that are too big, how can I select single words? 476 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 477 If you want to select e.g. alphanumeric words, you can use the following
434 setting: 478 setting:
435 479
460 URxvt.perl-ext-common: default,-selection-popup,-option-popup 504 URxvt.perl-ext-common: default,-selection-popup,-option-popup
461 505
462 This will keep the default extensions, but disable the two popup 506 This will keep the default extensions, but disable the two popup
463 extensions. Some extensions can also be configured, for example, 507 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 508 scrollback search mode is triggered by M-s. You can move it to any other
465 combination either by setting the searchable-scrollback resource: 509 combination by adding a keysym resource that binds the desired
510 combination to the "start" action of "searchable-scrollback" and another
511 one that binds M-s to the "builtin:" action:
466 512
467 URxvt.searchable-scrollback: CM-s 513 URxvt.keysym.CM-s: searchable-scrollback:start
514 URxvt.keysym.M-s: builtin:
468 515
469 The cursor moves when selecting text in the current input line, how do I switch this off? 516 The cursor moves when selecting text in the current input line, how do I switch this off?
470 See next entry. 517 See next entry.
471 518
472 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? 519 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" 526 You can permanently switch this feature off by disabling the "readline"
480 extension: 527 extension:
481 528
482 URxvt.perl-ext-common: default,-readline 529 URxvt.perl-ext-common: default,-readline
483 530
484 My numerical keypad acts weird and generates differing output? 531 My numeric keypad acts weird and generates differing output?
485 Some Debian GNUL/Linux users seem to have this problem, although no 532 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 533 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 534 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 535 how this can happen are unknown, as "TERM=rxvt" should offer a
489 compatible keymap. See the answer to the previous question, and please 536 compatible keymap. See the answer to the previous question, and please
490 report if that helped. 537 report if that helped.
491 538
492 My Compose (Multi_key) key is no longer working. 539 My Compose (Multi_key) key is no longer working.
493 The most common causes for this are that either your locale is not set 540 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 541 correctly, or you specified a preeditType that is not supported by your
495 input method. For example, if you specified OverTheSpot and your input 542 input method. For example, if you specified OverTheSpot and your input
496 method (e.g. the default input method handling Compose keys) does not 543 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 544 support this (for instance because it is not visual), then rxvt-unicode
498 will continue without an input method. 545 will continue without an input method.
499 546
500 In this case either do not specify a preeditStyle or specify more than 547 In this case either do not specify a preeditType or specify more than
501 one pre-edit style, such as OverTheSpot,Root,None. 548 one pre-edit style, such as OverTheSpot,Root,None.
502 549
503 If it still doesn't work, then maybe your input method doesn't support 550 If it still doesn't work, then maybe your input method doesn't support
504 compose sequences - to fall back to the built-in one, make sure you 551 compose sequences - to fall back to the built-in one, make sure you
505 don't specify an input method via "-im" or "XMODIFIERS". 552 don't specify an input method via "-im" or "XMODIFIERS".
511 other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet 558 other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet
512 escape character and so on. 559 escape character and so on.
513 560
514 Mouse cut/paste suddenly no longer works. 561 Mouse cut/paste suddenly no longer works.
515 Make sure that mouse reporting is actually turned off since killing some 562 Make sure that mouse reporting is actually turned off since killing some
516 editors prematurely may leave the mouse in mouse report mode. I've heard 563 editors prematurely may leave it active. I've heard that tcsh may use
517 that tcsh may use mouse reporting unless it otherwise specified. A quick 564 mouse reporting unless it is otherwise specified. A quick check is to
518 check is to see if cut/paste works when the Alt or Shift keys are 565 see if cut/paste works when the Alt or Shift keys are pressed.
519 depressed.
520 566
521 What's with the strange Backspace/Delete key behaviour? 567 What's with the strange Backspace/Delete key behaviour?
522 Assuming that the physical Backspace key corresponds to the Backspace 568 Assuming that the physical Backspace key corresponds to the Backspace
523 keysym (not likely for Linux ... see the following question) there are 569 keysym (not likely for Linux ... see the following question) there are
524 two standard values that can be used for Backspace: "^H" and "^?". 570 two standard values that can be used for Backspace: "^H" and "^?".
525 571
526 Historically, either value is correct, but rxvt-unicode adopts the 572 Historically, either value is correct, but rxvt-unicode adopts the
527 debian policy of using "^?" when unsure, because it's the one and only 573 debian policy of using "^?" when unsure, because it's the one and only
528 correct choice :). 574 correct choice :).
529 575
530 Rxvt-unicode tries to inherit the current stty settings and uses the 576 It is possible to toggle between "^H" and "^?" with the DECBKM private
531 value of `erase' to guess the value for backspace. If rxvt-unicode 577 mode:
532 wasn't started from a terminal (say, from a menu or by remote shell),
533 then the system value of `erase', which corresponds to CERASE in
534 <termios.h>, will be used (which may not be the same as your stty
535 setting).
536
537 For starting a new rxvt-unicode:
538 578
539 # use Backspace = ^H 579 # use Backspace = ^H
540 $ stty erase ^H 580 $ stty erase ^H
541 $ urxvt 581 $ printf "\e[?67h"
542 582
543 # use Backspace = ^? 583 # use Backspace = ^?
544 $ stty erase ^? 584 $ stty erase ^?
545 $ urxvt 585 $ printf "\e[?67l"
546
547 Toggle with "ESC [ 36 h" / "ESC [ 36 l".
548
549 For an existing rxvt-unicode:
550
551 # use Backspace = ^H
552 $ stty erase ^H
553 $ echo -n "^[[36h"
554
555 # use Backspace = ^?
556 $ stty erase ^?
557 $ echo -n "^[[36l"
558 586
559 This helps satisfy some of the Backspace discrepancies that occur, but 587 This helps satisfy some of the Backspace discrepancies that occur, but
560 if you use Backspace = "^H", make sure that the termcap/terminfo value 588 if you use Backspace = "^H", make sure that the termcap/terminfo value
561 properly reflects that. 589 properly reflects that.
562 590
578 use the `keysym' resource to alter the keystrings associated with 606 use the `keysym' resource to alter the keystrings associated with
579 keysyms. 607 keysyms.
580 608
581 Here's an example for a URxvt session started using "urxvt -name URxvt" 609 Here's an example for a URxvt session started using "urxvt -name URxvt"
582 610
611 URxvt.keysym.Prior: \033[5~
612 URxvt.keysym.Next: \033[6~
583 URxvt.keysym.Home: \033[1~ 613 URxvt.keysym.Home: \033[7~
584 URxvt.keysym.End: \033[4~ 614 URxvt.keysym.End: \033[8~
585 URxvt.keysym.C-apostrophe: \033<C-'>
586 URxvt.keysym.C-slash: \033<C-/>
587 URxvt.keysym.C-semicolon: \033<C-;>
588 URxvt.keysym.C-grave: \033<C-`>
589 URxvt.keysym.C-comma: \033<C-,>
590 URxvt.keysym.C-period: \033<C-.>
591 URxvt.keysym.C-0x60: \033<C-`>
592 URxvt.keysym.C-Tab: \033<C-Tab>
593 URxvt.keysym.C-Return: \033<C-Return>
594 URxvt.keysym.S-Return: \033<S-Return>
595 URxvt.keysym.S-space: \033<S-Space>
596 URxvt.keysym.M-Up: \033<M-Up> 615 URxvt.keysym.Up: \033[A
597 URxvt.keysym.M-Down: \033<M-Down> 616 URxvt.keysym.Down: \033[B
617 URxvt.keysym.Right: \033[C
598 URxvt.keysym.M-Left: \033<M-Left> 618 URxvt.keysym.Left: \033[D
599 URxvt.keysym.M-Right: \033<M-Right>
600 URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
601 URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
602 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
603 619
604 See some more examples in the documentation for the keysym resource. 620 See some more examples in the documentation for the keysym resource.
605 621
606 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 622 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
607 KP_Insert == Insert 623 KP_Insert == Insert
624 time into customising your terminal. To get you started, here is the 640 time into customising your terminal. To get you started, here is the
625 author's .Xdefaults entries, with comments on what they do. It's 641 author's .Xdefaults entries, with comments on what they do. It's
626 certainly not *typical*, but what's typical... 642 certainly not *typical*, but what's typical...
627 643
628 URxvt.cutchars: "()*,<>[]{}|' 644 URxvt.cutchars: "()*,<>[]{}|'
629 URxvt.print-pipe: cat >/tmp/xxx 645 URxvt.print-pipe: cat >/some/path
630 646
631 These are just for testing stuff. 647 These are just for testing stuff.
632 648
633 URxvt.imLocale: ja_JP.UTF-8 649 URxvt.imLocale: ja_JP.UTF-8
634 URxvt.preeditType: OnTheSpot,None 650 URxvt.preeditType: OnTheSpot,None
650 develop for myself mostly, so I actually use most of the extensions I 666 develop for myself mostly, so I actually use most of the extensions I
651 write. 667 write.
652 668
653 The selection stuff mainly makes the selection perl-error-message aware 669 The selection stuff mainly makes the selection perl-error-message aware
654 and tells it to convert perl error messages into vi-commands to load the 670 and tells it to convert perl error messages into vi-commands to load the
655 relevant file and go tot he error line number. 671 relevant file and go to the error line number.
656 672
657 URxvt.scrollstyle: plain 673 URxvt.scrollstyle: plain
658 URxvt.secondaryScroll: true 674 URxvt.secondaryScroll: true
659 675
660 As the documentation says: plain is the preferred scrollbar for the 676 As the documentation says: plain is the preferred scrollbar for the
733 my purposes, it works, and gives a different look, as my normal 749 my purposes, it works, and gives a different look, as my normal
734 (Non-bold) font is already bold, and I want to see a difference between 750 (Non-bold) font is already bold, and I want to see a difference between
735 bold and normal fonts. 751 bold and normal fonts.
736 752
737 Please note that I used the "urxvt" instance name and not the "URxvt" 753 Please note that I used the "urxvt" instance name and not the "URxvt"
738 class name. Thats because I use different configs for different 754 class name. That is because I use different configs for different
739 purposes, for example, my IRC window is started with "-name IRC", and 755 purposes, for example, my IRC window is started with "-name IRC", and
740 uses these defaults: 756 uses these defaults:
741 757
742 IRC*title: IRC 758 IRC*title: IRC
743 IRC*geometry: 87x12+535+542 759 IRC*geometry: 87x12+535+542
754 keeping a very small window. If somebody pastes something complicated 770 keeping a very small window. If somebody pastes something complicated
755 (e.g. japanese), I temporarily switch to a larger font. 771 (e.g. japanese), I temporarily switch to a larger font.
756 772
757 The above is all in my ".Xdefaults" (I don't use ".Xresources" nor 773 The above is all in my ".Xdefaults" (I don't use ".Xresources" nor
758 "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" 774 "xrdb"). I also have some resources in a separate ".Xdefaults-hostname"
759 file for different hosts, for example, on ym main desktop, I use: 775 file for different hosts, for example, on my main desktop, I use:
760 776
761 URxvt.keysym.C-M-q: command:\033[3;5;5t 777 URxvt.keysym.C-M-q: command:\033[3;5;5t
762 URxvt.keysym.C-M-y: command:\033[3;5;606t 778 URxvt.keysym.C-M-y: command:\033[3;5;606t
763 URxvt.keysym.C-M-e: command:\033[3;1605;5t 779 URxvt.keysym.C-M-e: command:\033[3;1605;5t
764 URxvt.keysym.C-M-c: command:\033[3;1605;606t 780 URxvt.keysym.C-M-c: command:\033[3;1605;606t
834 See next entry. 850 See next entry.
835 851
836 I need a termcap file entry. 852 I need a termcap file entry.
837 One reason you might want this is that some distributions or operating 853 One reason you might want this is that some distributions or operating
838 systems still compile some programs using the long-obsoleted termcap 854 systems still compile some programs using the long-obsoleted termcap
839 library (Fedora Core's bash is one example) and rely on a termcap entry 855 library (Fedora's bash is one example) and rely on a termcap entry for
840 for "rxvt-unicode". 856 "rxvt-unicode".
841 857
842 You could use rxvt's termcap entry with reasonable results in many 858 You could use rxvt's termcap entry with reasonable results in many
843 cases. You can also create a termcap entry by using terminfo's infocmp 859 cases. You can also create a termcap entry by using terminfo's infocmp
844 program like this: 860 program like this:
845 861
868 Why doesn't vim/emacs etc. make use of italic? 884 Why doesn't vim/emacs etc. make use of italic?
869 See next entry. 885 See next entry.
870 886
871 Why are the secondary screen-related options not working properly? 887 Why are the secondary screen-related options not working properly?
872 Make sure you are using "TERM=rxvt-unicode". Some pre-packaged 888 Make sure you are using "TERM=rxvt-unicode". Some pre-packaged
873 distributions (most notably Debian GNU/Linux) break rxvt-unicode by 889 distributions break rxvt-unicode by setting "TERM" to "rxvt", which
874 setting "TERM" to "rxvt", which doesn't have these extra features. 890 doesn't have these extra features. Unfortunately, some of these
875 Unfortunately, some of these (most notably, again, Debian GNU/Linux)
876 furthermore fail to even install the "rxvt-unicode" terminfo file, so 891 furthermore fail to even install the "rxvt-unicode" terminfo file, so
877 you will need to install it on your own (See the question When I log-in 892 you will need to install it on your own (See the question When I log-in
878 to another system it tells me about missing terminfo data? on how to do 893 to another system it tells me about missing terminfo data? on how to do
879 this). 894 this).
880 895
991 For scim, use "@im=SCIM". You can see what input method servers are 1006 For scim, use "@im=SCIM". You can see what input method servers are
992 running with this command: 1007 running with this command:
993 1008
994 xprop -root XIM_SERVERS 1009 xprop -root XIM_SERVERS
995 1010
996
997
998 My input method wants <some encoding> but I want UTF-8, what can I do? 1011 My input method wants <some encoding> but I want UTF-8, what can I do?
999 You can specify separate locales for the input method and the rest of 1012 You can specify separate locales for the input method and the rest of
1000 the terminal, using the resource "imlocale": 1013 the terminal, using the resource "imlocale":
1001 1014
1002 URxvt.imlocale: ja_JP.EUC-JP 1015 URxvt.imlocale: ja_JP.EUC-JP
1015 cannot be completely avoided even if both sides cooperate. 1028 cannot be completely avoided even if both sides cooperate.
1016 1029
1017 So the only workaround is not to kill your Input Method Servers. 1030 So the only workaround is not to kill your Input Method Servers.
1018 1031
1019 Operating Systems / Package Maintaining 1032 Operating Systems / Package Maintaining
1020 I am using Debian GNU/Linux and have a problem...
1021 The Debian GNU/Linux package of rxvt-unicode in sarge contains large
1022 patches that considerably change the behaviour of rxvt-unicode (but
1023 unfortunately this notice has been removed). Before reporting a bug to
1024 the original rxvt-unicode author please download and install the genuine
1025 version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce
1026 the problem. If you cannot, chances are that the problems are specific
1027 to Debian GNU/Linux, in which case it should be reported via the Debian
1028 Bug Tracking System (use "reportbug" to report the bug).
1029
1030 For other problems that also affect the Debian package, you can and
1031 probably should use the Debian BTS, too, because, after all, it's also a
1032 bug in the Debian version and it serves as a reminder for other users
1033 that might encounter the same issue.
1034
1035 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? 1033 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
1036 You should build one binary with the default options. configure now 1034 You should build one binary with the default options. configure now
1037 enables most useful options, and the trend goes to making them 1035 enables most useful options, and the trend goes to making them
1038 runtime-switchable, too, so there is usually no drawback to enabling 1036 runtime-switchable, too, so there is usually no drawback to enabling
1039 them, except higher disk and possibly memory usage. The perl interpreter 1037 them, except higher disk and possibly memory usage. The perl interpreter
1040 should be enabled, as important functionality (menus, selection, likely 1038 should be enabled, as important functionality (menus, selection, likely
1041 more in the future) depends on it. 1039 more in the future) depends on it.
1042 1040
1043 You should not overwrite the "perl-ext-common" snd "perl-ext" resources 1041 You should not overwrite the "perl-ext-common" and "perl-ext" resources
1044 system-wide (except maybe with "defaults"). This will result in useful 1042 system-wide (except maybe with "defaults"). This will result in useful
1045 behaviour. If your distribution aims at low memory, add an empty 1043 behaviour. If your distribution aims at low memory, add an empty
1046 "perl-ext-common" resource to the app-defaults file. This will keep the 1044 "perl-ext-common" resource to the app-defaults file. This will keep the
1047 perl interpreter disabled until the user enables it. 1045 perl interpreter disabled until the user enables it.
1048 1046
1120 The solution is to upgrade your system or switch to a better one. A 1118 The solution is to upgrade your system or switch to a better one. A
1121 possibly working workaround is to use a wcwidth implementation like 1119 possibly working workaround is to use a wcwidth implementation like
1122 1120
1123 http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c 1121 http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
1124 1122
1125 I want 256 colors
1126 Are you sure you need 256 colors? 88 colors should be enough for most
1127 purposes. If you really need more, there is an unsupported patch for it
1128 in the doc directory, but please do not ask for it to be applied.
1129

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines