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.58 by root, Tue Mar 16 00:54:46 2010 UTC vs.
Revision 1.69 by root, Sat Apr 26 14:31:44 2014 UTC

… …
69 This tries to create a new terminal, and if fails with exit status 2, 69 This tries to create a new terminal, and if fails with exit status 2,
70 meaning it couldn't connect to the daemon, it will start the daemon and 70 meaning it couldn't connect to the daemon, it will start the daemon and
71 re-run the command. Subsequent invocations of the script will re-use the 71 re-run the command. Subsequent invocations of the script will re-use the
72 existing daemon. 72 existing daemon.
73 73
74 How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. 74 How do I distinguish whether I'm running rxvt-unicode or a regular
75xterm? I need this to decide about setting colours etc.
75 The original rxvt and rxvt-unicode always export the variable 76 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 77 "COLORTERM", so you can check and see if that is set. Note that several
77 programs, JED, slrn, Midnight Commander automatically check this 78 programs, JED, slrn, Midnight Commander automatically check this
78 variable to decide whether or not to use color. 79 variable to decide whether or not to use colour.
79 80
80 How do I set the correct, full IP address for the DISPLAY variable? 81 How do I set the correct, full IP address for the DISPLAY variable?
81 If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled 82 If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled
82 insecure mode then it is possible to use the following shell script 83 insecure mode then it is possible to use the following shell script
83 snippets to correctly set the display. If your version of rxvt-unicode 84 snippets to correctly set the display. If your version of rxvt-unicode
… …
90 91
91 # Bourne/Korn/POSIX family of shells: 92 # Bourne/Korn/POSIX family of shells:
92 [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know 93 [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
93 if [ ${TERM:-foo} = xterm ]; then 94 if [ ${TERM:-foo} = xterm ]; then
94 stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not 95 stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
95 echo -n '^[Z' 96 printf "\eZ"
96 read term_id 97 read term_id
97 stty icanon echo 98 stty icanon echo
98 if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then 99 if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
99 echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string 100 printf '\e[7n' # query the rxvt we are in for the DISPLAY string
100 read DISPLAY # set it in our local shell 101 read DISPLAY # set it in our local shell
101 fi 102 fi
102 fi 103 fi
103 104
104 How do I compile the manual pages on my own? 105 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, 106 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 158 the case of rxvt-unicode this hardly matters, as its portability limits
158 are defined by things like X11, pseudo terminals, locale support and 159 are defined by things like X11, pseudo terminals, locale support and
159 unix domain sockets, which are all less portable than C++ itself. 160 unix domain sockets, which are all less portable than C++ itself.
160 161
161 Regarding the bloat, see the above question: It's easy to write programs 162 Regarding the bloat, see the above question: It's easy to write programs
162 in C that use gobs of memory, an certainly possible to write programs in 163 in C that use gobs of memory, and certainly possible to write programs
163 C++ that don't. C++ also often comes with large libraries, but this is 164 in C++ that don't. C++ also often comes with large libraries, but this
164 not necessarily the case with GCC. Here is what rxvt links against on my 165 is not necessarily the case with GCC. Here is what rxvt links against on
165 system with a minimal config: 166 my system with a minimal config:
166 167
167 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 168 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
168 libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) 169 libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
169 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) 170 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
170 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) 171 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
… …
180 No large bloated libraries (of course, none were linked in statically), 181 No large bloated libraries (of course, none were linked in statically),
181 except maybe libX11 :) 182 except maybe libX11 :)
182 183
183 Rendering, Font & Look and Feel Issues 184 Rendering, Font & Look and Feel Issues
184 I can't get transparency working, what am I doing wrong? 185 I can't get transparency working, what am I doing wrong?
185 First of all, please address all transparency related issues to Sasha 186 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, 187 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 188 may bug everybody else). Also, if you can't get it working consider it a
188 failed. 189 rite of passage: ... and you failed.
189 190
190 Here are four ways to get transparency. Do read the manpage and option 191 Here are four ways to get transparency. Do read the manpage and option
191 descriptions for the programs mentioned and rxvt-unicode. Really, do it! 192 descriptions for the programs mentioned and rxvt-unicode. Really, do it!
192 193
193 1. Use transparent mode: 194 1. Use transparent mode:
194 195
195 Esetroot wallpaper.jpg 196 Esetroot wallpaper.jpg
196 urxvt -tr -tint red -sh 40 197 urxvt -tr -tint red -sh 40
197 198
198 That works. If you think it doesn't, you lack transparency and tinting 199 That works. If you think it doesn't, you lack transparency and tinting
199 support, or you are unable to read. 200 support, or you are unable to read. This method requires that the
201 background-setting program sets the _XROOTPMAP_ID or ESETROOT_PMAP_ID
202 property. Compatible programs are Esetroot, hsetroot and feh.
200 203
201 2. Use a simple pixmap and emulate pseudo-transparency. This enables you 204 2. Use a simple pixmap and emulate pseudo-transparency. This enables you
202 to use effects other than tinting and shading: Just shade/tint/whatever 205 to use effects other than tinting and shading: Just shade/tint/whatever
203 your picture with gimp or any other tool: 206 your picture with gimp or any other tool:
204 207
205 convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg 208 convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
206 urxvt -pixmap "background.jpg;:root" 209 urxvt -pixmap "background.jpg;:root"
207 210
208 That works. If you think it doesn't, you lack AfterImage support, or you 211 That works. If you think it doesn't, you lack GDK-PixBuf support, or you
209 are unable to read. 212 are unable to read.
210 213
211 3. Use an ARGB visual: 214 3. Use an ARGB visual:
212 215
213 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc 216 urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
… …
312 For the standard background colour, blinking will actually make the text 315 For the standard background colour, blinking will actually make the text
313 blink when compiled with "--enable-text-blink". Without 316 blink when compiled with "--enable-text-blink". Without
314 "--enable-text-blink", the blink attribute will be ignored. 317 "--enable-text-blink", the blink attribute will be ignored.
315 318
316 On ANSI colours, bold/blink attributes are used to set high-intensity 319 On ANSI colours, bold/blink attributes are used to set high-intensity
317 foreground/background colors. 320 foreground/background colours.
318 321
319 color0-7 are the low-intensity colors. 322 color0-7 are the low-intensity colours.
320 323
321 color8-15 are the corresponding high-intensity colors. 324 color8-15 are the corresponding high-intensity colours.
322 325
323 I don't like the screen colors. How do I change them? 326 I don't like the screen colours. How do I change them?
324 You can change the screen colors at run-time using ~/.Xdefaults 327 You can change the screen colours at run-time using ~/.Xdefaults
325 resources (or as long-options). 328 resources (or as long-options).
326 329
327 Here are values that are supposed to resemble a VGA screen, including 330 Here are values that are supposed to resemble a VGA screen, including
328 the murky brown that passes for low-intensity yellow: 331 the murky brown that passes for low-intensity yellow:
329 332
… …
343 URxvt.color12: #0000FF 346 URxvt.color12: #0000FF
344 URxvt.color13: #FF00FF 347 URxvt.color13: #FF00FF
345 URxvt.color14: #00FFFF 348 URxvt.color14: #00FFFF
346 URxvt.color15: #FFFFFF 349 URxvt.color15: #FFFFFF
347 350
348 And here is a more complete set of non-standard colors. 351 And here is a more complete set of non-standard colours.
349 352
350 URxvt.cursorColor: #dc74d1 353 URxvt.cursorColor: #dc74d1
351 URxvt.pointerColor: #dc74d1 354 URxvt.pointerColor: #dc74d1
352 URxvt.background: #0e0e0e 355 URxvt.background: #0e0e0e
353 URxvt.foreground: #4ad5e1 356 URxvt.foreground: #4ad5e1
… …
489 compatible keymap. See the answer to the previous question, and please 492 compatible keymap. See the answer to the previous question, and please
490 report if that helped. 493 report if that helped.
491 494
492 My Compose (Multi_key) key is no longer working. 495 My Compose (Multi_key) key is no longer working.
493 The most common causes for this are that either your locale is not set 496 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 497 correctly, or you specified a preeditType that is not supported by your
495 input method. For example, if you specified OverTheSpot and your input 498 input method. For example, if you specified OverTheSpot and your input
496 method (e.g. the default input method handling Compose keys) does not 499 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 500 support this (for instance because it is not visual), then rxvt-unicode
498 will continue without an input method. 501 will continue without an input method.
499 502
500 In this case either do not specify a preeditStyle or specify more than 503 In this case either do not specify a preeditType or specify more than
501 one pre-edit style, such as OverTheSpot,Root,None. 504 one pre-edit style, such as OverTheSpot,Root,None.
502 505
503 If it still doesn't work, then maybe your input method doesn't support 506 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 507 compose sequences - to fall back to the built-in one, make sure you
505 don't specify an input method via "-im" or "XMODIFIERS". 508 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 514 other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet
512 escape character and so on. 515 escape character and so on.
513 516
514 Mouse cut/paste suddenly no longer works. 517 Mouse cut/paste suddenly no longer works.
515 Make sure that mouse reporting is actually turned off since killing some 518 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 519 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 520 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 521 see if cut/paste works when the Alt or Shift keys are pressed.
519 depressed.
520 522
521 What's with the strange Backspace/Delete key behaviour? 523 What's with the strange Backspace/Delete key behaviour?
522 Assuming that the physical Backspace key corresponds to the Backspace 524 Assuming that the physical Backspace key corresponds to the Backspace
523 keysym (not likely for Linux ... see the following question) there are 525 keysym (not likely for Linux ... see the following question) there are
524 two standard values that can be used for Backspace: "^H" and "^?". 526 two standard values that can be used for Backspace: "^H" and "^?".
525 527
526 Historically, either value is correct, but rxvt-unicode adopts the 528 Historically, either value is correct, but rxvt-unicode adopts the
527 debian policy of using "^?" when unsure, because it's the one and only 529 debian policy of using "^?" when unsure, because it's the one and only
528 correct choice :). 530 correct choice :).
529 531
530 Rxvt-unicode tries to inherit the current stty settings and uses the 532 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 533 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 534
539 # use Backspace = ^H 535 # use Backspace = ^H
540 $ stty erase ^H 536 $ stty erase ^H
541 $ urxvt 537 $ printf "\e[?67h"
542 538
543 # use Backspace = ^? 539 # use Backspace = ^?
544 $ stty erase ^? 540 $ stty erase ^?
545 $ urxvt 541 $ 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 542
559 This helps satisfy some of the Backspace discrepancies that occur, but 543 This helps satisfy some of the Backspace discrepancies that occur, but
560 if you use Backspace = "^H", make sure that the termcap/terminfo value 544 if you use Backspace = "^H", make sure that the termcap/terminfo value
561 properly reflects that. 545 properly reflects that.
562 546
… …
578 use the `keysym' resource to alter the keystrings associated with 562 use the `keysym' resource to alter the keystrings associated with
579 keysyms. 563 keysyms.
580 564
581 Here's an example for a URxvt session started using "urxvt -name URxvt" 565 Here's an example for a URxvt session started using "urxvt -name URxvt"
582 566
567 URxvt.keysym.Prior: \033[5~
568 URxvt.keysym.Next: \033[6~
583 URxvt.keysym.Home: \033[1~ 569 URxvt.keysym.Home: \033[7~
584 URxvt.keysym.End: \033[4~ 570 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> 571 URxvt.keysym.Up: \033[A
597 URxvt.keysym.M-Down: \033<M-Down> 572 URxvt.keysym.Down: \033[B
573 URxvt.keysym.Right: \033[C
598 URxvt.keysym.M-Left: \033<M-Left> 574 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 575
604 See some more examples in the documentation for the keysym resource. 576 See some more examples in the documentation for the keysym resource.
605 577
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 578 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 579 KP_Insert == Insert
… …
754 keeping a very small window. If somebody pastes something complicated 726 keeping a very small window. If somebody pastes something complicated
755 (e.g. japanese), I temporarily switch to a larger font. 727 (e.g. japanese), I temporarily switch to a larger font.
756 728
757 The above is all in my ".Xdefaults" (I don't use ".Xresources" nor 729 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" 730 "xrdb"). I also have some resources in a separate ".Xdefaults-hostname"
759 file for different hosts, for example, on ym main desktop, I use: 731 file for different hosts, for example, on my main desktop, I use:
760 732
761 URxvt.keysym.C-M-q: command:\033[3;5;5t 733 URxvt.keysym.C-M-q: command:\033[3;5;5t
762 URxvt.keysym.C-M-y: command:\033[3;5;606t 734 URxvt.keysym.C-M-y: command:\033[3;5;606t
763 URxvt.keysym.C-M-e: command:\033[3;1605;5t 735 URxvt.keysym.C-M-e: command:\033[3;1605;5t
764 URxvt.keysym.C-M-c: command:\033[3;1605;606t 736 URxvt.keysym.C-M-c: command:\033[3;1605;606t
… …
802 774
803 REMOTE=remotesystem.domain 775 REMOTE=remotesystem.domain
804 infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" 776 infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
805 777
806 One some systems you might need to set $TERMINFO to the full path of 778 One some systems you might need to set $TERMINFO to the full path of
807 $HOME/.terminfo for this to work. 779 $HOME/.terminfo for this to work. Debian systems have a broken tic which
780 will not be able to overwrite the existing rxvt-unicode terminfo entry -
781 you might have to manually delete all traces of rxvt-unicode* from
782 /etc/terminfo.
808 783
809 If you cannot or do not want to do this, then you can simply set 784 If you cannot or do not want to do this, then you can simply set
810 "TERM=rxvt" or even "TERM=xterm", and live with the small number of 785 "TERM=rxvt" or even "TERM=xterm", and live with the small number of
811 problems arising, which includes wrong keymapping, less and different 786 problems arising, which includes wrong keymapping, less and different
812 colours and some refresh errors in fullscreen applications. It's a nice 787 colours and some refresh errors in fullscreen applications. It's a nice
… …
991 For scim, use "@im=SCIM". You can see what input method servers are 966 For scim, use "@im=SCIM". You can see what input method servers are
992 running with this command: 967 running with this command:
993 968
994 xprop -root XIM_SERVERS 969 xprop -root XIM_SERVERS
995 970
996
997
998 My input method wants <some encoding> but I want UTF-8, what can I do? 971 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 972 You can specify separate locales for the input method and the rest of
1000 the terminal, using the resource "imlocale": 973 the terminal, using the resource "imlocale":
1001 974
1002 URxvt.imlocale: ja_JP.EUC-JP 975 URxvt.imlocale: ja_JP.EUC-JP
… …
1020 I am using Debian GNU/Linux and have a problem... 993 I am using Debian GNU/Linux and have a problem...
1021 The Debian GNU/Linux package of rxvt-unicode in sarge contains large 994 The Debian GNU/Linux package of rxvt-unicode in sarge contains large
1022 patches that considerably change the behaviour of rxvt-unicode (but 995 patches that considerably change the behaviour of rxvt-unicode (but
1023 unfortunately this notice has been removed). Before reporting a bug to 996 unfortunately this notice has been removed). Before reporting a bug to
1024 the original rxvt-unicode author please download and install the genuine 997 the original rxvt-unicode author please download and install the genuine
1025 version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce 998 version (<http://software.schmorp.de/pkg/rxvt-unicode.html>) and try to
1026 the problem. If you cannot, chances are that the problems are specific 999 reproduce the problem. If you cannot, chances are that the problems are
1027 to Debian GNU/Linux, in which case it should be reported via the Debian 1000 specific to Debian GNU/Linux, in which case it should be reported via
1028 Bug Tracking System (use "reportbug" to report the bug). 1001 the Debian Bug Tracking System (use "reportbug" to report the bug).
1029 1002
1030 For other problems that also affect the Debian package, you can and 1003 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 1004 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 1005 bug in the Debian version and it serves as a reminder for other users
1033 that might encounter the same issue. 1006 that might encounter the same issue.
… …
1120 The solution is to upgrade your system or switch to a better one. A 1093 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 1094 possibly working workaround is to use a wcwidth implementation like
1122 1095
1123 http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c 1096 http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
1124 1097
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