… | |
… | |
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 |
|
|
74 | xterm? 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 | |
… | |
… | |
479 | You can permanently switch this feature off by disabling the "readline" |
501 | You can permanently switch this feature off by disabling the "readline" |
480 | extension: |
502 | extension: |
481 | |
503 | |
482 | URxvt.perl-ext-common: default,-readline |
504 | URxvt.perl-ext-common: default,-readline |
483 | |
505 | |
484 | My numerical keypad acts weird and generates differing output? |
506 | My numeric keypad acts weird and generates differing output? |
485 | Some Debian GNUL/Linux users seem to have this problem, although no |
507 | 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 |
508 | 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 |
509 | 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 |
510 | how this can happen are unknown, as "TERM=rxvt" should offer a |
489 | compatible keymap. See the answer to the previous question, and please |
511 | compatible keymap. See the answer to the previous question, and please |
490 | report if that helped. |
512 | report if that helped. |
491 | |
513 | |
492 | My Compose (Multi_key) key is no longer working. |
514 | My Compose (Multi_key) key is no longer working. |
493 | The most common causes for this are that either your locale is not set |
515 | 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 |
516 | correctly, or you specified a preeditType that is not supported by your |
495 | input method. For example, if you specified OverTheSpot and your input |
517 | input method. For example, if you specified OverTheSpot and your input |
496 | method (e.g. the default input method handling Compose keys) does not |
518 | 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 |
519 | support this (for instance because it is not visual), then rxvt-unicode |
498 | will continue without an input method. |
520 | will continue without an input method. |
499 | |
521 | |
500 | In this case either do not specify a preeditStyle or specify more than |
522 | In this case either do not specify a preeditType or specify more than |
501 | one pre-edit style, such as OverTheSpot,Root,None. |
523 | one pre-edit style, such as OverTheSpot,Root,None. |
502 | |
524 | |
503 | If it still doesn't work, then maybe your input method doesn't support |
525 | 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 |
526 | compose sequences - to fall back to the built-in one, make sure you |
505 | don't specify an input method via "-im" or "XMODIFIERS". |
527 | 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 |
533 | other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet |
512 | escape character and so on. |
534 | escape character and so on. |
513 | |
535 | |
514 | Mouse cut/paste suddenly no longer works. |
536 | Mouse cut/paste suddenly no longer works. |
515 | Make sure that mouse reporting is actually turned off since killing some |
537 | 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 |
538 | 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 |
539 | 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 |
540 | see if cut/paste works when the Alt or Shift keys are pressed. |
519 | depressed. |
|
|
520 | |
541 | |
521 | What's with the strange Backspace/Delete key behaviour? |
542 | What's with the strange Backspace/Delete key behaviour? |
522 | Assuming that the physical Backspace key corresponds to the Backspace |
543 | Assuming that the physical Backspace key corresponds to the Backspace |
523 | keysym (not likely for Linux ... see the following question) there are |
544 | keysym (not likely for Linux ... see the following question) there are |
524 | two standard values that can be used for Backspace: "^H" and "^?". |
545 | two standard values that can be used for Backspace: "^H" and "^?". |
525 | |
546 | |
526 | Historically, either value is correct, but rxvt-unicode adopts the |
547 | Historically, either value is correct, but rxvt-unicode adopts the |
527 | debian policy of using "^?" when unsure, because it's the one and only |
548 | debian policy of using "^?" when unsure, because it's the one and only |
528 | correct choice :). |
549 | correct choice :). |
529 | |
550 | |
530 | Rxvt-unicode tries to inherit the current stty settings and uses the |
551 | 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 |
552 | 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 | |
553 | |
539 | # use Backspace = ^H |
554 | # use Backspace = ^H |
540 | $ stty erase ^H |
555 | $ stty erase ^H |
541 | $ urxvt |
556 | $ printf "\e[?67h" |
542 | |
557 | |
543 | # use Backspace = ^? |
558 | # use Backspace = ^? |
544 | $ stty erase ^? |
559 | $ stty erase ^? |
545 | $ urxvt |
560 | $ 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 | |
561 | |
559 | This helps satisfy some of the Backspace discrepancies that occur, but |
562 | This helps satisfy some of the Backspace discrepancies that occur, but |
560 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
563 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
561 | properly reflects that. |
564 | properly reflects that. |
562 | |
565 | |
… | |
… | |
578 | use the `keysym' resource to alter the keystrings associated with |
581 | use the `keysym' resource to alter the keystrings associated with |
579 | keysyms. |
582 | keysyms. |
580 | |
583 | |
581 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
584 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
582 | |
585 | |
|
|
586 | URxvt.keysym.Prior: \033[5~ |
|
|
587 | URxvt.keysym.Next: \033[6~ |
583 | URxvt.keysym.Home: \033[1~ |
588 | URxvt.keysym.Home: \033[7~ |
584 | URxvt.keysym.End: \033[4~ |
589 | 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> |
590 | URxvt.keysym.Up: \033[A |
597 | URxvt.keysym.M-Down: \033<M-Down> |
591 | URxvt.keysym.Down: \033[B |
|
|
592 | URxvt.keysym.Right: \033[C |
598 | URxvt.keysym.M-Left: \033<M-Left> |
593 | 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 | |
594 | |
604 | See some more examples in the documentation for the keysym resource. |
595 | See some more examples in the documentation for the keysym resource. |
605 | |
596 | |
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 |
597 | 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 |
598 | KP_Insert == Insert |
… | |
… | |
754 | keeping a very small window. If somebody pastes something complicated |
745 | keeping a very small window. If somebody pastes something complicated |
755 | (e.g. japanese), I temporarily switch to a larger font. |
746 | (e.g. japanese), I temporarily switch to a larger font. |
756 | |
747 | |
757 | The above is all in my ".Xdefaults" (I don't use ".Xresources" nor |
748 | 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" |
749 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
759 | file for different hosts, for example, on ym main desktop, I use: |
750 | file for different hosts, for example, on my main desktop, I use: |
760 | |
751 | |
761 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
752 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
762 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
753 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
763 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
754 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
764 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
755 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
… | |
… | |
868 | Why doesn't vim/emacs etc. make use of italic? |
859 | Why doesn't vim/emacs etc. make use of italic? |
869 | See next entry. |
860 | See next entry. |
870 | |
861 | |
871 | Why are the secondary screen-related options not working properly? |
862 | Why are the secondary screen-related options not working properly? |
872 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
863 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
873 | distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
864 | distributions break rxvt-unicode by setting "TERM" to "rxvt", which |
874 | setting "TERM" to "rxvt", which doesn't have these extra features. |
865 | 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 |
866 | 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 |
867 | 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 |
868 | to another system it tells me about missing terminfo data? on how to do |
879 | this). |
869 | this). |
880 | |
870 | |
… | |
… | |
991 | For scim, use "@im=SCIM". You can see what input method servers are |
981 | For scim, use "@im=SCIM". You can see what input method servers are |
992 | running with this command: |
982 | running with this command: |
993 | |
983 | |
994 | xprop -root XIM_SERVERS |
984 | xprop -root XIM_SERVERS |
995 | |
985 | |
996 | |
|
|
997 | |
|
|
998 | My input method wants <some encoding> but I want UTF-8, what can I do? |
986 | 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 |
987 | You can specify separate locales for the input method and the rest of |
1000 | the terminal, using the resource "imlocale": |
988 | the terminal, using the resource "imlocale": |
1001 | |
989 | |
1002 | URxvt.imlocale: ja_JP.EUC-JP |
990 | URxvt.imlocale: ja_JP.EUC-JP |
… | |
… | |
1015 | cannot be completely avoided even if both sides cooperate. |
1003 | cannot be completely avoided even if both sides cooperate. |
1016 | |
1004 | |
1017 | So the only workaround is not to kill your Input Method Servers. |
1005 | So the only workaround is not to kill your Input Method Servers. |
1018 | |
1006 | |
1019 | Operating Systems / Package Maintaining |
1007 | 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? |
1008 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1036 | You should build one binary with the default options. configure now |
1009 | You should build one binary with the default options. configure now |
1037 | enables most useful options, and the trend goes to making them |
1010 | enables most useful options, and the trend goes to making them |
1038 | runtime-switchable, too, so there is usually no drawback to enabling |
1011 | runtime-switchable, too, so there is usually no drawback to enabling |
1039 | them, except higher disk and possibly memory usage. The perl interpreter |
1012 | them, except higher disk and possibly memory usage. The perl interpreter |
… | |
… | |
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 | |
|
|