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.72 by root, Sat May 14 08:28:25 2016 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 How do I distinguish whether I'm running rxvt-unicode or a regular
74xterm? I need this to decide about setting colours etc.
75 The original rxvt and rxvt-unicode always export the variable 75 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 76 "COLORTERM", so you can check and see if that is set. Note that several
77 programs, JED, slrn, Midnight Commander automatically check this 77 programs, JED, slrn, Midnight Commander automatically check this
78 variable to decide whether or not to use color. 78 variable to decide whether or not to use colour.
79 79
80 How do I set the correct, full IP address for the DISPLAY variable? 80 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 81 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 82 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 83 snippets to correctly set the display. If your version of rxvt-unicode
… …
90 90
91 # Bourne/Korn/POSIX family of shells: 91 # Bourne/Korn/POSIX family of shells:
92 [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know 92 [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
93 if [ ${TERM:-foo} = xterm ]; then 93 if [ ${TERM:-foo} = xterm ]; then
94 stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not 94 stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
95 echo -n '^[Z' 95 printf "\eZ"
96 read term_id 96 read term_id
97 stty icanon echo 97 stty icanon echo
98 if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then 98 if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
99 echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string 99 printf '\e[7n' # query the rxvt we are in for the DISPLAY string
100 read DISPLAY # set it in our local shell 100 read DISPLAY # set it in our local shell
101 fi 101 fi
102 fi 102 fi
103 103
104 How do I compile the manual pages on my own? 104 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, 105 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 157 the case of rxvt-unicode this hardly matters, as its portability limits
158 are defined by things like X11, pseudo terminals, locale support and 158 are defined by things like X11, pseudo terminals, locale support and
159 unix domain sockets, which are all less portable than C++ itself. 159 unix domain sockets, which are all less portable than C++ itself.
160 160
161 Regarding the bloat, see the above question: It's easy to write programs 161 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 162 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 163 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 164 is not necessarily the case with GCC. Here is what rxvt links against on
165 system with a minimal config: 165 my system with a minimal config:
166 166
167 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 167 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
168 libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) 168 libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
169 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) 169 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
170 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) 170 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
… …
180 No large bloated libraries (of course, none were linked in statically), 180 No large bloated libraries (of course, none were linked in statically),
181 except maybe libX11 :) 181 except maybe libX11 :)
182 182
183 Rendering, Font & Look and Feel Issues 183 Rendering, Font & Look and Feel Issues
184 I can't get transparency working, what am I doing wrong? 184 I can't get transparency working, what am I doing wrong?
185 First of all, please address all transparency related issues to Sasha 185 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, 186 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 187 may bug everybody else). Also, if you can't get it working consider it a
188 failed. 188 rite of passage: ... and you failed.
189 189
190 Here are four ways to get transparency. Do read the manpage and option 190 Here are four ways to get transparency. Do read the manpage and option
191 descriptions for the programs mentioned and rxvt-unicode. Really, do it! 191 descriptions for the programs mentioned and rxvt-unicode. Really, do it!
192 192
193 1. Use transparent mode: 193 1. Use transparent mode:
194 194
195 Esetroot wallpaper.jpg 195 Esetroot wallpaper.jpg
196 urxvt -tr -tint red -sh 40 196 urxvt -tr -tint red -sh 40
197 197
198 That works. If you think it doesn't, you lack transparency and tinting 198 That works. If you think it doesn't, you lack transparency and tinting
199 support, or you are unable to read. 199 support, or you are unable to read. This method requires that the
200 background-setting program sets the _XROOTPMAP_ID or ESETROOT_PMAP_ID
201 property. Compatible programs are Esetroot, hsetroot and feh.
200 202
201 2. Use a simple pixmap and emulate pseudo-transparency. This enables you 203 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 204 to use effects other than tinting and shading: Just shade/tint/whatever
203 your picture with gimp or any other tool: 205 your picture with gimp or any other tool:
204 206
205 convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg 207 convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
206 urxvt -pixmap "background.jpg;:root" 208 urxvt -pixmap "background.jpg;:root"
207 209
208 That works. If you think it doesn't, you lack AfterImage support, or you 210 That works. If you think it doesn't, you lack GDK-PixBuf support, or you
209 are unable to read. 211 are unable to read.
210 212
211 3. Use an ARGB visual: 213 3. Use an ARGB visual:
212 214
213 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc 215 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
… …
312 For the standard background colour, blinking will actually make the text 314 For the standard background colour, blinking will actually make the text
313 blink when compiled with "--enable-text-blink". Without 315 blink when compiled with "--enable-text-blink". Without
314 "--enable-text-blink", the blink attribute will be ignored. 316 "--enable-text-blink", the blink attribute will be ignored.
315 317
316 On ANSI colours, bold/blink attributes are used to set high-intensity 318 On ANSI colours, bold/blink attributes are used to set high-intensity
317 foreground/background colors. 319 foreground/background colours.
318 320
319 color0-7 are the low-intensity colors. 321 color0-7 are the low-intensity colours.
320 322
321 color8-15 are the corresponding high-intensity colors. 323 color8-15 are the corresponding high-intensity colours.
322 324
323 I don't like the screen colors. How do I change them? 325 I don't like the screen colours. How do I change them?
324 You can change the screen colors at run-time using ~/.Xdefaults 326 You can change the screen colours at run-time using ~/.Xdefaults
325 resources (or as long-options). 327 resources (or as long-options).
326 328
327 Here are values that are supposed to resemble a VGA screen, including 329 Here are values that are supposed to resemble a VGA screen, including
328 the murky brown that passes for low-intensity yellow: 330 the murky brown that passes for low-intensity yellow:
329 331
… …
343 URxvt.color12: #0000FF 345 URxvt.color12: #0000FF
344 URxvt.color13: #FF00FF 346 URxvt.color13: #FF00FF
345 URxvt.color14: #00FFFF 347 URxvt.color14: #00FFFF
346 URxvt.color15: #FFFFFF 348 URxvt.color15: #FFFFFF
347 349
348 And here is a more complete set of non-standard colors. 350 And here is a more complete set of non-standard colours.
349 351
350 URxvt.cursorColor: #dc74d1 352 URxvt.cursorColor: #dc74d1
351 URxvt.pointerColor: #dc74d1 353 URxvt.pointerColor: #dc74d1
352 URxvt.background: #0e0e0e 354 URxvt.background: #0e0e0e
353 URxvt.foreground: #4ad5e1 355 URxvt.foreground: #4ad5e1
… …
426 We are working on it, in the meantime, as a workaround, use something 428 We are working on it, in the meantime, as a workaround, use something
427 like: 429 like:
428 430
429 urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...' 431 urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
430 432
433 Why is the cursor now blinking in emacs/vi/...?
434 This is likely caused by your editor/program's use of the "cvvis"
435 terminfo capability. Emacs uses it by default, as well as some versions
436 of vi and possibly other programs.
437
438 In emacs, you can switch that off by adding this to your ".emacs" file:
439
440 (setq visible-cursor nil)
441
442 For other programs, if they do not have an option, your have to remove
443 the "cvvis" capability from the terminfo description.
444
445 When urxvt first added the blinking cursor option, it didn't add a
446 "cvvis" capability, which served no purpose before. Version 9.21
447 introduced "cvvis" (and the ability to control blinking independent of
448 cursor shape) for compatibility with other terminals, which
449 traditionally use a blinking cursor for "cvvis". This also reflects the
450 intent of programs such as emacs, who expect "cvvis" to enable a
451 blinking cursor.
452
431 Keyboard, Mouse & User Interaction 453 Keyboard, Mouse & User Interaction
432 The new selection selects pieces that are too big, how can I select single words? 454 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 455 If you want to select e.g. alphanumeric words, you can use the following
434 setting: 456 setting:
435 457
… …
460 URxvt.perl-ext-common: default,-selection-popup,-option-popup 482 URxvt.perl-ext-common: default,-selection-popup,-option-popup
461 483
462 This will keep the default extensions, but disable the two popup 484 This will keep the default extensions, but disable the two popup
463 extensions. Some extensions can also be configured, for example, 485 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 486 scrollback search mode is triggered by M-s. You can move it to any other
465 combination either by setting the searchable-scrollback resource: 487 combination by adding a keysym resource that binds the desired
488 combination to the "start" action of "searchable-scrollback" and another
489 one that binds M-s to the "builtin:" action:
466 490
467 URxvt.searchable-scrollback: CM-s 491 URxvt.keysym.CM-s: searchable-scrollback:start
492 URxvt.keysym.M-s: builtin:
468 493
469 The cursor moves when selecting text in the current input line, how do I switch this off? 494 The cursor moves when selecting text in the current input line, how do I switch this off?
470 See next entry. 495 See next entry.
471 496
472 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? 497 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" 504 You can permanently switch this feature off by disabling the "readline"
480 extension: 505 extension:
481 506
482 URxvt.perl-ext-common: default,-readline 507 URxvt.perl-ext-common: default,-readline
483 508
484 My numerical keypad acts weird and generates differing output? 509 My numeric keypad acts weird and generates differing output?
485 Some Debian GNUL/Linux users seem to have this problem, although no 510 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 511 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 512 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 513 how this can happen are unknown, as "TERM=rxvt" should offer a
489 compatible keymap. See the answer to the previous question, and please 514 compatible keymap. See the answer to the previous question, and please
490 report if that helped. 515 report if that helped.
491 516
492 My Compose (Multi_key) key is no longer working. 517 My Compose (Multi_key) key is no longer working.
493 The most common causes for this are that either your locale is not set 518 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 519 correctly, or you specified a preeditType that is not supported by your
495 input method. For example, if you specified OverTheSpot and your input 520 input method. For example, if you specified OverTheSpot and your input
496 method (e.g. the default input method handling Compose keys) does not 521 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 522 support this (for instance because it is not visual), then rxvt-unicode
498 will continue without an input method. 523 will continue without an input method.
499 524
500 In this case either do not specify a preeditStyle or specify more than 525 In this case either do not specify a preeditType or specify more than
501 one pre-edit style, such as OverTheSpot,Root,None. 526 one pre-edit style, such as OverTheSpot,Root,None.
527
528 If it still doesn't work, then maybe your input method doesn't support
529 compose sequences - to fall back to the built-in one, make sure you
530 don't specify an input method via "-im" or "XMODIFIERS".
502 531
503 I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 532 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 533 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 534 international keyboards) or simply use ISO 14755 support to your
506 advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for 535 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 536 other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet
508 escape character and so on. 537 escape character and so on.
509 538
510 Mouse cut/paste suddenly no longer works. 539 Mouse cut/paste suddenly no longer works.
511 Make sure that mouse reporting is actually turned off since killing some 540 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 541 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 542 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 543 see if cut/paste works when the Alt or Shift keys are pressed.
515 depressed.
516 544
517 What's with the strange Backspace/Delete key behaviour? 545 What's with the strange Backspace/Delete key behaviour?
518 Assuming that the physical Backspace key corresponds to the Backspace 546 Assuming that the physical Backspace key corresponds to the Backspace
519 keysym (not likely for Linux ... see the following question) there are 547 keysym (not likely for Linux ... see the following question) there are
520 two standard values that can be used for Backspace: "^H" and "^?". 548 two standard values that can be used for Backspace: "^H" and "^?".
521 549
522 Historically, either value is correct, but rxvt-unicode adopts the 550 Historically, either value is correct, but rxvt-unicode adopts the
523 debian policy of using "^?" when unsure, because it's the one and only 551 debian policy of using "^?" when unsure, because it's the one and only
524 correct choice :). 552 correct choice :).
525 553
526 Rxvt-unicode tries to inherit the current stty settings and uses the 554 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 555 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 556
535 # use Backspace = ^H 557 # use Backspace = ^H
536 $ stty erase ^H 558 $ stty erase ^H
537 $ urxvt 559 $ printf "\e[?67h"
538 560
539 # use Backspace = ^? 561 # use Backspace = ^?
540 $ stty erase ^? 562 $ stty erase ^?
541 $ urxvt 563 $ 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 564
555 This helps satisfy some of the Backspace discrepancies that occur, but 565 This helps satisfy some of the Backspace discrepancies that occur, but
556 if you use Backspace = "^H", make sure that the termcap/terminfo value 566 if you use Backspace = "^H", make sure that the termcap/terminfo value
557 properly reflects that. 567 properly reflects that.
558 568
… …
574 use the `keysym' resource to alter the keystrings associated with 584 use the `keysym' resource to alter the keystrings associated with
575 keysyms. 585 keysyms.
576 586
577 Here's an example for a URxvt session started using "urxvt -name URxvt" 587 Here's an example for a URxvt session started using "urxvt -name URxvt"
578 588
589 URxvt.keysym.Prior: \033[5~
590 URxvt.keysym.Next: \033[6~
579 URxvt.keysym.Home: \033[1~ 591 URxvt.keysym.Home: \033[7~
580 URxvt.keysym.End: \033[4~ 592 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> 593 URxvt.keysym.Up: \033[A
593 URxvt.keysym.M-Down: \033<M-Down> 594 URxvt.keysym.Down: \033[B
595 URxvt.keysym.Right: \033[C
594 URxvt.keysym.M-Left: \033<M-Left> 596 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 597
600 See some more examples in the documentation for the keysym resource. 598 See some more examples in the documentation for the keysym resource.
601 599
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 600 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 601 KP_Insert == Insert
… …
646 develop for myself mostly, so I actually use most of the extensions I 644 develop for myself mostly, so I actually use most of the extensions I
647 write. 645 write.
648 646
649 The selection stuff mainly makes the selection perl-error-message aware 647 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 648 and tells it to convert perl error messages into vi-commands to load the
651 relevant file and go tot he error line number. 649 relevant file and go to the error line number.
652 650
653 URxvt.scrollstyle: plain 651 URxvt.scrollstyle: plain
654 URxvt.secondaryScroll: true 652 URxvt.secondaryScroll: true
655 653
656 As the documentation says: plain is the preferred scrollbar for the 654 As the documentation says: plain is the preferred scrollbar for the
… …
729 my purposes, it works, and gives a different look, as my normal 727 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 728 (Non-bold) font is already bold, and I want to see a difference between
731 bold and normal fonts. 729 bold and normal fonts.
732 730
733 Please note that I used the "urxvt" instance name and not the "URxvt" 731 Please note that I used the "urxvt" instance name and not the "URxvt"
734 class name. Thats because I use different configs for different 732 class name. That is because I use different configs for different
735 purposes, for example, my IRC window is started with "-name IRC", and 733 purposes, for example, my IRC window is started with "-name IRC", and
736 uses these defaults: 734 uses these defaults:
737 735
738 IRC*title: IRC 736 IRC*title: IRC
739 IRC*geometry: 87x12+535+542 737 IRC*geometry: 87x12+535+542
… …
743 IRC*boldFont: suxuseuro 741 IRC*boldFont: suxuseuro
744 IRC*colorBD: white 742 IRC*colorBD: white
745 IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 743 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 744 IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
747 745
748 "Alt-Shift-1" and "Alt-Shift-2" switch between two different font sizes. 746 "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 747 "suxuseuro" allows me to keep an eye (and actually read) stuff while
750 keeping a very small window. If somebody pastes something complicated 748 keeping a very small window. If somebody pastes something complicated
751 (e.g. japanese), I temporarily switch to a larger font. 749 (e.g. japanese), I temporarily switch to a larger font.
752 750
753 The above is all in my ".Xdefaults" (I don't use ".Xresources" nor 751 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" 752 "xrdb"). I also have some resources in a separate ".Xdefaults-hostname"
755 file for different hosts, for example, on ym main desktop, I use: 753 file for different hosts, for example, on my main desktop, I use:
756 754
757 URxvt.keysym.C-M-q: command:\033[3;5;5t 755 URxvt.keysym.C-M-q: command:\033[3;5;5t
758 URxvt.keysym.C-M-y: command:\033[3;5;606t 756 URxvt.keysym.C-M-y: command:\033[3;5;606t
759 URxvt.keysym.C-M-e: command:\033[3;1605;5t 757 URxvt.keysym.C-M-e: command:\033[3;1605;5t
760 URxvt.keysym.C-M-c: command:\033[3;1605;606t 758 URxvt.keysym.C-M-c: command:\033[3;1605;606t
… …
789 The terminal description used by rxvt-unicode is not as widely available 787 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 788 as that for xterm, or even rxvt (for which the same problem often
791 arises). 789 arises).
792 790
793 The correct solution for this problem is to install the terminfo, this 791 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 792 can be done by simply installing rxvt-unicode on the remote system as
795 admin): 793 well (in case you have a nice package manager ready), or you can install
794 the terminfo database manually like this (with ncurses infocmp. works as
795 user and root):
796 796
797 REMOTE=remotesystem.domain 797 REMOTE=remotesystem.domain
798 infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" 798 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 799
802 One some systems you might need to set $TERMINFO to the full path of 800 One some systems you might need to set $TERMINFO to the full path of
803 $HOME/.terminfo for this to work. 801 $HOME/.terminfo for this to work.
804 802
805 If you cannot or do not want to do this, then you can simply set 803 If you cannot or do not want to do this, then you can simply set
… …
815 URxvt.termName: rxvt 813 URxvt.termName: rxvt
816 814
817 If you don't plan to use rxvt (quite common...) you could also replace 815 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". 816 the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt".
819 817
818 nano fails with "Error opening terminal: rxvt-unicode"
819 This exceptionally confusing and useless error message is printed by
820 nano when it can't find the terminfo database. Nothing is wrong with
821 your terminal, read the previous answer for a solution.
822
820 "tic" outputs some error when compiling the terminfo entry. 823 "tic" outputs some error when compiling the terminfo entry.
821 Most likely it's the empty definition for "enacs=". Just replace it by 824 Most likely it's the empty definition for "enacs=". Just replace it by
822 "enacs=\E[0@" and try again. 825 "enacs=\E[0@" and try again.
823 826
824 "bash"'s readline does not work correctly under urxvt. 827 "bash"'s readline does not work correctly under urxvt.
825 See next entry. 828 See next entry.
826 829
827 I need a termcap file entry. 830 I need a termcap file entry.
828 One reason you might want this is that some distributions or operating 831 One reason you might want this is that some distributions or operating
829 systems still compile some programs using the long-obsoleted termcap 832 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 833 library (Fedora's bash is one example) and rely on a termcap entry for
831 for "rxvt-unicode". 834 "rxvt-unicode".
832 835
833 You could use rxvt's termcap entry with reasonable results in many 836 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 837 cases. You can also create a termcap entry by using terminfo's infocmp
835 program like this: 838 program like this:
836 839
… …
859 Why doesn't vim/emacs etc. make use of italic? 862 Why doesn't vim/emacs etc. make use of italic?
860 See next entry. 863 See next entry.
861 864
862 Why are the secondary screen-related options not working properly? 865 Why are the secondary screen-related options not working properly?
863 Make sure you are using "TERM=rxvt-unicode". Some pre-packaged 866 Make sure you are using "TERM=rxvt-unicode". Some pre-packaged
864 distributions (most notably Debian GNU/Linux) break rxvt-unicode by 867 distributions break rxvt-unicode by setting "TERM" to "rxvt", which
865 setting "TERM" to "rxvt", which doesn't have these extra features. 868 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 869 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 870 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 871 to another system it tells me about missing terminfo data? on how to do
870 this). 872 this).
871 873
… …
982 For scim, use "@im=SCIM". You can see what input method servers are 984 For scim, use "@im=SCIM". You can see what input method servers are
983 running with this command: 985 running with this command:
984 986
985 xprop -root XIM_SERVERS 987 xprop -root XIM_SERVERS
986 988
987
988
989 My input method wants <some encoding> but I want UTF-8, what can I do? 989 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 990 You can specify separate locales for the input method and the rest of
991 the terminal, using the resource "imlocale": 991 the terminal, using the resource "imlocale":
992 992
993 URxvt.imlocale: ja_JP.EUC-JP 993 URxvt.imlocale: ja_JP.EUC-JP
… …
1006 cannot be completely avoided even if both sides cooperate. 1006 cannot be completely avoided even if both sides cooperate.
1007 1007
1008 So the only workaround is not to kill your Input Method Servers. 1008 So the only workaround is not to kill your Input Method Servers.
1009 1009
1010 Operating Systems / Package Maintaining 1010 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? 1011 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
1027 You should build one binary with the default options. configure now 1012 You should build one binary with the default options. configure now
1028 enables most useful options, and the trend goes to making them 1013 enables most useful options, and the trend goes to making them
1029 runtime-switchable, too, so there is usually no drawback to enabling 1014 runtime-switchable, too, so there is usually no drawback to enabling
1030 them, except higher disk and possibly memory usage. The perl interpreter 1015 them, except higher disk and possibly memory usage. The perl interpreter
1031 should be enabled, as important functionality (menus, selection, likely 1016 should be enabled, as important functionality (menus, selection, likely
1032 more in the future) depends on it. 1017 more in the future) depends on it.
1033 1018
1034 You should not overwrite the "perl-ext-common" snd "perl-ext" resources 1019 You should not overwrite the "perl-ext-common" and "perl-ext" resources
1035 system-wide (except maybe with "defaults"). This will result in useful 1020 system-wide (except maybe with "defaults"). This will result in useful
1036 behaviour. If your distribution aims at low memory, add an empty 1021 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 1022 "perl-ext-common" resource to the app-defaults file. This will keep the
1038 perl interpreter disabled until the user enables it. 1023 perl interpreter disabled until the user enables it.
1039 1024

Diff Legend

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