… | |
… | |
2 | Meta, Features & Commandline Issues |
2 | Meta, Features & Commandline Issues |
3 | My question isn't answered here, can I ask a human? |
3 | My question isn't answered here, can I ask a human? |
4 | Before sending me mail, you could go to IRC: "irc.freenode.net", channel |
4 | Before sending me mail, you could go to IRC: "irc.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 | |
|
|
8 | I use Gentoo, and I have a problem... |
|
|
9 | There are two big problems with Gentoo Linux: first, most if not all |
|
|
10 | Gentoo systems are completely broken (missing or mismatched header |
|
|
11 | files, broken compiler etc. are just the tip of the iceberg); secondly, |
|
|
12 | it should be called Gentoo GNU/Linux. |
|
|
13 | |
|
|
14 | For these reasons, it is impossible to support rxvt-unicode on Gentoo. |
|
|
15 | Problems appearing on Gentoo systems will usually simply be ignored |
|
|
16 | unless they can be reproduced on non-Gentoo systems. |
7 | |
17 | |
8 | Does it support tabs, can I have a tabbed rxvt-unicode? |
18 | Does it support tabs, can I have a tabbed rxvt-unicode? |
9 | Beginning with version 7.3, there is a perl extension that implements a |
19 | Beginning with version 7.3, there is a perl extension that implements a |
10 | simple tabbed terminal. It is installed by default, so any of these |
20 | simple tabbed terminal. It is installed by default, so any of these |
11 | should give you tabs: |
21 | should give you tabs: |
… | |
… | |
58 | 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, |
59 | 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 |
60 | 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 |
61 | existing daemon. |
71 | existing daemon. |
62 | |
72 | |
63 | 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 |
|
|
96 | xterm? I need this to decide about setting colours etc. |
64 | The original rxvt and rxvt-unicode always export the variable |
97 | The original rxvt and rxvt-unicode always export the variable |
65 | "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 |
66 | programs, JED, slrn, Midnight Commander automatically check this |
99 | programs, JED, slrn, Midnight Commander automatically check this |
67 | variable to decide whether or not to use color. |
100 | variable to decide whether or not to use colour. |
68 | |
101 | |
69 | 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? |
70 | 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 |
71 | 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 |
72 | 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 |
… | |
… | |
79 | |
112 | |
80 | # Bourne/Korn/POSIX family of shells: |
113 | # Bourne/Korn/POSIX family of shells: |
81 | [ ${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 |
82 | if [ ${TERM:-foo} = xterm ]; then |
115 | if [ ${TERM:-foo} = xterm ]; then |
83 | 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 |
84 | echo -n '^[Z' |
117 | printf "\eZ" |
85 | read term_id |
118 | read term_id |
86 | stty icanon echo |
119 | stty icanon echo |
87 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
120 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
88 | 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 |
89 | read DISPLAY # set it in our local shell |
122 | read DISPLAY # set it in our local shell |
90 | fi |
123 | fi |
91 | fi |
124 | fi |
92 | |
125 | |
93 | How do I compile the manual pages on my own? |
126 | How do I compile the manual pages on my own? |
94 | 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, |
… | |
… | |
146 | 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 |
147 | are defined by things like X11, pseudo terminals, locale support and |
180 | are defined by things like X11, pseudo terminals, locale support and |
148 | unix domain sockets, which are all less portable than C++ itself. |
181 | unix domain sockets, which are all less portable than C++ itself. |
149 | |
182 | |
150 | 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 |
151 | 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 |
152 | 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 |
153 | 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 |
154 | system with a minimal config: |
187 | my system with a minimal config: |
155 | |
188 | |
156 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
189 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
157 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
190 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
158 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
191 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
159 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
192 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
… | |
… | |
169 | No large bloated libraries (of course, none were linked in statically), |
202 | No large bloated libraries (of course, none were linked in statically), |
170 | except maybe libX11 :) |
203 | except maybe libX11 :) |
171 | |
204 | |
172 | Rendering, Font & Look and Feel Issues |
205 | Rendering, Font & Look and Feel Issues |
173 | I can't get transparency working, what am I doing wrong? |
206 | I can't get transparency working, what am I doing wrong? |
174 | First of all, please address all transparency related issues to Sasha |
207 | First of all, transparency isn't officially supported in rxvt-unicode, |
175 | 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 |
176 | 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 |
177 | failed. |
210 | rite of passage: ... and you failed. |
178 | |
211 | |
179 | 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 |
180 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
213 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
181 | |
214 | |
182 | 1. Use transparent mode: |
215 | 1. Use transparent mode: |
183 | |
216 | |
184 | Esetroot wallpaper.jpg |
217 | Esetroot wallpaper.jpg |
185 | urxvt -tr -tint red -sh 40 |
218 | urxvt -tr -tint red -sh 40 |
186 | |
219 | |
187 | 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 |
188 | 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. |
189 | |
224 | |
190 | 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 |
191 | 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 |
192 | your picture with gimp or any other tool: |
227 | your picture with gimp or any other tool: |
193 | |
228 | |
194 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
229 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
195 | urxvt -pixmap "background.jpg;:root" |
230 | urxvt -pixmap "background.jpg;:root" |
196 | |
231 | |
197 | 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 |
198 | are unable to read. |
233 | are unable to read. |
199 | |
234 | |
200 | 3. Use an ARGB visual: |
235 | 3. Use an ARGB visual: |
201 | |
236 | |
202 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
237 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
… | |
… | |
301 | For the standard background colour, blinking will actually make the text |
336 | For the standard background colour, blinking will actually make the text |
302 | blink when compiled with "--enable-text-blink". Without |
337 | blink when compiled with "--enable-text-blink". Without |
303 | "--enable-text-blink", the blink attribute will be ignored. |
338 | "--enable-text-blink", the blink attribute will be ignored. |
304 | |
339 | |
305 | 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 |
306 | foreground/background colors. |
341 | foreground/background colours. |
307 | |
342 | |
308 | color0-7 are the low-intensity colors. |
343 | color0-7 are the low-intensity colours. |
309 | |
344 | |
310 | color8-15 are the corresponding high-intensity colors. |
345 | color8-15 are the corresponding high-intensity colours. |
311 | |
346 | |
312 | 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? |
313 | You can change the screen colors at run-time using ~/.Xdefaults |
348 | You can change the screen colours at run-time using ~/.Xdefaults |
314 | resources (or as long-options). |
349 | resources (or as long-options). |
315 | |
350 | |
316 | 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 |
317 | the murky brown that passes for low-intensity yellow: |
352 | the murky brown that passes for low-intensity yellow: |
318 | |
353 | |
… | |
… | |
332 | URxvt.color12: #0000FF |
367 | URxvt.color12: #0000FF |
333 | URxvt.color13: #FF00FF |
368 | URxvt.color13: #FF00FF |
334 | URxvt.color14: #00FFFF |
369 | URxvt.color14: #00FFFF |
335 | URxvt.color15: #FFFFFF |
370 | URxvt.color15: #FFFFFF |
336 | |
371 | |
337 | And here is a more complete set of non-standard colors. |
372 | And here is a more complete set of non-standard colours. |
338 | |
373 | |
339 | URxvt.cursorColor: #dc74d1 |
374 | URxvt.cursorColor: #dc74d1 |
340 | URxvt.pointerColor: #dc74d1 |
375 | URxvt.pointerColor: #dc74d1 |
341 | URxvt.background: #0e0e0e |
376 | URxvt.background: #0e0e0e |
342 | URxvt.foreground: #4ad5e1 |
377 | URxvt.foreground: #4ad5e1 |
… | |
… | |
415 | 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 |
416 | like: |
451 | like: |
417 | |
452 | |
418 | 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...' |
419 | |
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 | |
420 | Keyboard, Mouse & User Interaction |
475 | Keyboard, Mouse & User Interaction |
421 | 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? |
422 | 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 |
423 | setting: |
478 | setting: |
424 | |
479 | |
… | |
… | |
449 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
504 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
450 | |
505 | |
451 | This will keep the default extensions, but disable the two popup |
506 | This will keep the default extensions, but disable the two popup |
452 | extensions. Some extensions can also be configured, for example, |
507 | extensions. Some extensions can also be configured, for example, |
453 | 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 |
454 | 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: |
455 | |
512 | |
456 | URxvt.searchable-scrollback: CM-s |
513 | URxvt.keysym.CM-s: searchable-scrollback:start |
|
|
514 | URxvt.keysym.M-s: builtin: |
457 | |
515 | |
458 | 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? |
459 | See next entry. |
517 | See next entry. |
460 | |
518 | |
461 | 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? |
… | |
… | |
468 | You can permanently switch this feature off by disabling the "readline" |
526 | You can permanently switch this feature off by disabling the "readline" |
469 | extension: |
527 | extension: |
470 | |
528 | |
471 | URxvt.perl-ext-common: default,-readline |
529 | URxvt.perl-ext-common: default,-readline |
472 | |
530 | |
473 | My numerical keypad acts weird and generates differing output? |
531 | My numeric keypad acts weird and generates differing output? |
474 | 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 |
475 | 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 |
476 | 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 |
477 | 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 |
478 | compatible keymap. See the answer to the previous question, and please |
536 | compatible keymap. See the answer to the previous question, and please |
479 | report if that helped. |
537 | report if that helped. |
480 | |
538 | |
481 | My Compose (Multi_key) key is no longer working. |
539 | My Compose (Multi_key) key is no longer working. |
482 | 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 |
483 | 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 |
484 | input method. For example, if you specified OverTheSpot and your input |
542 | input method. For example, if you specified OverTheSpot and your input |
485 | 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 |
486 | 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 |
487 | will continue without an input method. |
545 | will continue without an input method. |
488 | |
546 | |
489 | 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 |
490 | one pre-edit style, such as OverTheSpot,Root,None. |
548 | one pre-edit style, such as OverTheSpot,Root,None. |
|
|
549 | |
|
|
550 | If it still doesn't work, then maybe your input method doesn't support |
|
|
551 | compose sequences - to fall back to the built-in one, make sure you |
|
|
552 | don't specify an input method via "-im" or "XMODIFIERS". |
491 | |
553 | |
492 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 |
554 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 |
493 | Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
555 | Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
494 | international keyboards) or simply use ISO 14755 support to your |
556 | international keyboards) or simply use ISO 14755 support to your |
495 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
557 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
496 | 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 |
497 | escape character and so on. |
559 | escape character and so on. |
498 | |
560 | |
499 | Mouse cut/paste suddenly no longer works. |
561 | Mouse cut/paste suddenly no longer works. |
500 | 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 |
501 | 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 |
502 | 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 |
503 | 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. |
504 | depressed. |
|
|
505 | |
566 | |
506 | What's with the strange Backspace/Delete key behaviour? |
567 | What's with the strange Backspace/Delete key behaviour? |
507 | Assuming that the physical Backspace key corresponds to the Backspace |
568 | Assuming that the physical Backspace key corresponds to the Backspace |
508 | keysym (not likely for Linux ... see the following question) there are |
569 | keysym (not likely for Linux ... see the following question) there are |
509 | two standard values that can be used for Backspace: "^H" and "^?". |
570 | two standard values that can be used for Backspace: "^H" and "^?". |
510 | |
571 | |
511 | Historically, either value is correct, but rxvt-unicode adopts the |
572 | Historically, either value is correct, but rxvt-unicode adopts the |
512 | 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 |
513 | correct choice :). |
574 | correct choice :). |
514 | |
575 | |
515 | 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 |
516 | value of `erase' to guess the value for backspace. If rxvt-unicode |
577 | mode: |
517 | wasn't started from a terminal (say, from a menu or by remote shell), |
|
|
518 | then the system value of `erase', which corresponds to CERASE in |
|
|
519 | <termios.h>, will be used (which may not be the same as your stty |
|
|
520 | setting). |
|
|
521 | |
|
|
522 | For starting a new rxvt-unicode: |
|
|
523 | |
578 | |
524 | # use Backspace = ^H |
579 | # use Backspace = ^H |
525 | $ stty erase ^H |
580 | $ stty erase ^H |
526 | $ urxvt |
581 | $ printf "\e[?67h" |
527 | |
582 | |
528 | # use Backspace = ^? |
583 | # use Backspace = ^? |
529 | $ stty erase ^? |
584 | $ stty erase ^? |
530 | $ urxvt |
585 | $ printf "\e[?67l" |
531 | |
|
|
532 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
|
|
533 | |
|
|
534 | For an existing rxvt-unicode: |
|
|
535 | |
|
|
536 | # use Backspace = ^H |
|
|
537 | $ stty erase ^H |
|
|
538 | $ echo -n "^[[36h" |
|
|
539 | |
|
|
540 | # use Backspace = ^? |
|
|
541 | $ stty erase ^? |
|
|
542 | $ echo -n "^[[36l" |
|
|
543 | |
586 | |
544 | This helps satisfy some of the Backspace discrepancies that occur, but |
587 | This helps satisfy some of the Backspace discrepancies that occur, but |
545 | 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 |
546 | properly reflects that. |
589 | properly reflects that. |
547 | |
590 | |
… | |
… | |
563 | use the `keysym' resource to alter the keystrings associated with |
606 | use the `keysym' resource to alter the keystrings associated with |
564 | keysyms. |
607 | keysyms. |
565 | |
608 | |
566 | 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" |
567 | |
610 | |
|
|
611 | URxvt.keysym.Prior: \033[5~ |
|
|
612 | URxvt.keysym.Next: \033[6~ |
568 | URxvt.keysym.Home: \033[1~ |
613 | URxvt.keysym.Home: \033[7~ |
569 | URxvt.keysym.End: \033[4~ |
614 | URxvt.keysym.End: \033[8~ |
570 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
571 | URxvt.keysym.C-slash: \033<C-/> |
|
|
572 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
573 | URxvt.keysym.C-grave: \033<C-`> |
|
|
574 | URxvt.keysym.C-comma: \033<C-,> |
|
|
575 | URxvt.keysym.C-period: \033<C-.> |
|
|
576 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
577 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
578 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
579 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
580 | URxvt.keysym.S-space: \033<S-Space> |
|
|
581 | URxvt.keysym.M-Up: \033<M-Up> |
615 | URxvt.keysym.Up: \033[A |
582 | URxvt.keysym.M-Down: \033<M-Down> |
616 | URxvt.keysym.Down: \033[B |
|
|
617 | URxvt.keysym.Right: \033[C |
583 | URxvt.keysym.M-Left: \033<M-Left> |
618 | URxvt.keysym.Left: \033[D |
584 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
585 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
586 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
587 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
|
|
588 | |
619 | |
589 | See some more examples in the documentation for the keysym resource. |
620 | See some more examples in the documentation for the keysym resource. |
590 | |
621 | |
591 | 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 |
592 | KP_Insert == Insert |
623 | KP_Insert == Insert |
… | |
… | |
609 | 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 |
610 | 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 |
611 | certainly not *typical*, but what's typical... |
642 | certainly not *typical*, but what's typical... |
612 | |
643 | |
613 | URxvt.cutchars: "()*,<>[]{}|' |
644 | URxvt.cutchars: "()*,<>[]{}|' |
614 | URxvt.print-pipe: cat >/tmp/xxx |
645 | URxvt.print-pipe: cat >/some/path |
615 | |
646 | |
616 | These are just for testing stuff. |
647 | These are just for testing stuff. |
617 | |
648 | |
618 | URxvt.imLocale: ja_JP.UTF-8 |
649 | URxvt.imLocale: ja_JP.UTF-8 |
619 | URxvt.preeditType: OnTheSpot,None |
650 | URxvt.preeditType: OnTheSpot,None |
… | |
… | |
635 | 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 |
636 | write. |
667 | write. |
637 | |
668 | |
638 | The selection stuff mainly makes the selection perl-error-message aware |
669 | The selection stuff mainly makes the selection perl-error-message aware |
639 | 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 |
640 | relevant file and go tot he error line number. |
671 | relevant file and go to the error line number. |
641 | |
672 | |
642 | URxvt.scrollstyle: plain |
673 | URxvt.scrollstyle: plain |
643 | URxvt.secondaryScroll: true |
674 | URxvt.secondaryScroll: true |
644 | |
675 | |
645 | As the documentation says: plain is the preferred scrollbar for the |
676 | As the documentation says: plain is the preferred scrollbar for the |
… | |
… | |
718 | 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 |
719 | (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 |
720 | bold and normal fonts. |
751 | bold and normal fonts. |
721 | |
752 | |
722 | 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" |
723 | class name. Thats because I use different configs for different |
754 | class name. That is because I use different configs for different |
724 | 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 |
725 | uses these defaults: |
756 | uses these defaults: |
726 | |
757 | |
727 | IRC*title: IRC |
758 | IRC*title: IRC |
728 | IRC*geometry: 87x12+535+542 |
759 | IRC*geometry: 87x12+535+542 |
… | |
… | |
732 | IRC*boldFont: suxuseuro |
763 | IRC*boldFont: suxuseuro |
733 | IRC*colorBD: white |
764 | IRC*colorBD: white |
734 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
765 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
735 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
766 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
736 | |
767 | |
737 | "Alt-Shift-1" and "Alt-Shift-2" switch between two different font sizes. |
768 | "Alt-Ctrl-1" and "Alt-Ctrl-2" switch between two different font sizes. |
738 | "suxuseuro" allows me to keep an eye (and actually read) stuff while |
769 | "suxuseuro" allows me to keep an eye (and actually read) stuff while |
739 | keeping a very small window. If somebody pastes something complicated |
770 | keeping a very small window. If somebody pastes something complicated |
740 | (e.g. japanese), I temporarily switch to a larger font. |
771 | (e.g. japanese), I temporarily switch to a larger font. |
741 | |
772 | |
742 | 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 |
743 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
774 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
744 | 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: |
745 | |
776 | |
746 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
777 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
747 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
778 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
748 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
779 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
749 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
780 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
… | |
… | |
778 | The terminal description used by rxvt-unicode is not as widely available |
809 | The terminal description used by rxvt-unicode is not as widely available |
779 | as that for xterm, or even rxvt (for which the same problem often |
810 | as that for xterm, or even rxvt (for which the same problem often |
780 | arises). |
811 | arises). |
781 | |
812 | |
782 | The correct solution for this problem is to install the terminfo, this |
813 | The correct solution for this problem is to install the terminfo, this |
783 | can be done like this (with ncurses' infocmp and works as user and |
814 | can be done by simply installing rxvt-unicode on the remote system as |
784 | admin): |
815 | well (in case you have a nice package manager ready), or you can install |
|
|
816 | the terminfo database manually like this (with ncurses infocmp. works as |
|
|
817 | user and root): |
785 | |
818 | |
786 | REMOTE=remotesystem.domain |
819 | REMOTE=remotesystem.domain |
787 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
820 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
788 | |
|
|
789 | ... or by installing rxvt-unicode normally on the remote system, |
|
|
790 | |
821 | |
791 | One some systems you might need to set $TERMINFO to the full path of |
822 | One some systems you might need to set $TERMINFO to the full path of |
792 | $HOME/.terminfo for this to work. |
823 | $HOME/.terminfo for this to work. |
793 | |
824 | |
794 | If you cannot or do not want to do this, then you can simply set |
825 | If you cannot or do not want to do this, then you can simply set |
… | |
… | |
804 | URxvt.termName: rxvt |
835 | URxvt.termName: rxvt |
805 | |
836 | |
806 | If you don't plan to use rxvt (quite common...) you could also replace |
837 | If you don't plan to use rxvt (quite common...) you could also replace |
807 | the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". |
838 | the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". |
808 | |
839 | |
|
|
840 | nano fails with "Error opening terminal: rxvt-unicode" |
|
|
841 | This exceptionally confusing and useless error message is printed by |
|
|
842 | nano when it can't find the terminfo database. Nothing is wrong with |
|
|
843 | your terminal, read the previous answer for a solution. |
|
|
844 | |
809 | "tic" outputs some error when compiling the terminfo entry. |
845 | "tic" outputs some error when compiling the terminfo entry. |
810 | Most likely it's the empty definition for "enacs=". Just replace it by |
846 | Most likely it's the empty definition for "enacs=". Just replace it by |
811 | "enacs=\E[0@" and try again. |
847 | "enacs=\E[0@" and try again. |
812 | |
848 | |
813 | "bash"'s readline does not work correctly under urxvt. |
849 | "bash"'s readline does not work correctly under urxvt. |
814 | See next entry. |
850 | See next entry. |
815 | |
851 | |
816 | I need a termcap file entry. |
852 | I need a termcap file entry. |
817 | 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 |
818 | systems still compile some programs using the long-obsoleted termcap |
854 | systems still compile some programs using the long-obsoleted termcap |
819 | 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 |
820 | for "rxvt-unicode". |
856 | "rxvt-unicode". |
821 | |
857 | |
822 | 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 |
823 | 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 |
824 | program like this: |
860 | program like this: |
825 | |
861 | |
826 | infocmp -C rxvt-unicode |
862 | infocmp -C rxvt-unicode |
827 | |
863 | |
828 | Or you could use this termcap entry, generated by the command above: |
864 | Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap, |
829 | |
865 | generated by the command above. |
830 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
|
|
831 | :am:bw:eo:km:mi:ms:xn:xo:\ |
|
|
832 | :co#80:it#8:li#24:lm#0:\ |
|
|
833 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
|
|
834 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
|
|
835 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
|
|
836 | :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
|
|
837 | :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
|
|
838 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
|
|
839 | :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
|
|
840 | :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
|
|
841 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
|
|
842 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
|
|
843 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
|
|
844 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
|
|
845 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
|
|
846 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
|
|
847 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
|
|
848 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
|
|
849 | :vs=\E[?25h: |
|
|
850 | |
866 | |
851 | Why does "ls" no longer have coloured output? |
867 | Why does "ls" no longer have coloured output? |
852 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
868 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
853 | decide whether a terminal has colour, but uses its own configuration |
869 | decide whether a terminal has colour, but uses its own configuration |
854 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
870 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
… | |
… | |
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 | |
… | |
… | |
1076 | As you might have guessed, FreeBSD does neither define this symbol nor |
1074 | As you might have guessed, FreeBSD does neither define this symbol nor |
1077 | does it support it. Instead, it uses its own internal representation of |
1075 | does it support it. Instead, it uses its own internal representation of |
1078 | wchar_t. This is, of course, completely fine with respect to standards. |
1076 | wchar_t. This is, of course, completely fine with respect to standards. |
1079 | |
1077 | |
1080 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
1078 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
1081 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
1079 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t). |
1082 | |
1080 | |
1083 | "__STDC_ISO_10646__" is the only sane way to support multi-language apps |
1081 | "__STDC_ISO_10646__" is the only sane way to support multi-language apps |
1084 | in an OS, as using a locale-dependent (and non-standardized) |
1082 | in an OS, as using a locale-dependent (and non-standardized) |
1085 | representation of wchar_t makes it impossible to convert between wchar_t |
1083 | representation of wchar_t makes it impossible to convert between wchar_t |
1086 | (as used by X11 and your applications) and any other encoding without |
1084 | (as used by X11 and your applications) and any other encoding without |