| … | |
… | |
| 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 | How do I distinguish whether I'm running rxvt-unicode or a regular |
|
|
74 | xterm? I need this to decide about setting colours etc. |
| 64 | The original rxvt and rxvt-unicode always export the variable |
75 | 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 |
76 | "COLORTERM", so you can check and see if that is set. Note that several |
| 66 | programs, JED, slrn, Midnight Commander automatically check this |
77 | programs, JED, slrn, Midnight Commander automatically check this |
| 67 | variable to decide whether or not to use color. |
78 | variable to decide whether or not to use colour. |
| 68 | |
79 | |
| 69 | 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? |
| 70 | 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 |
| 71 | 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 |
| 72 | 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 |
| … | |
… | |
| 79 | |
90 | |
| 80 | # Bourne/Korn/POSIX family of shells: |
91 | # Bourne/Korn/POSIX family of shells: |
| 81 | [ ${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 |
| 82 | if [ ${TERM:-foo} = xterm ]; then |
93 | if [ ${TERM:-foo} = xterm ]; then |
| 83 | 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 |
| 84 | echo -n '^[Z' |
95 | printf "\eZ" |
| 85 | read term_id |
96 | read term_id |
| 86 | stty icanon echo |
97 | stty icanon echo |
| 87 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
98 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
| 88 | 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 |
| 89 | read DISPLAY # set it in our local shell |
100 | read DISPLAY # set it in our local shell |
| 90 | fi |
101 | fi |
| 91 | fi |
102 | fi |
| 92 | |
103 | |
| 93 | How do I compile the manual pages on my own? |
104 | 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, |
105 | You need to have a recent version of perl installed as /usr/bin/perl, |
| 95 | one that comes with pod2man, pod2text and pod2xhtml (from Pod::XHTML). |
106 | one that comes with pod2man, pod2text and pod2xhtml (from Pod::Xhtml). |
| 96 | Then go to the doc subdirectory and enter "make alldoc". |
107 | Then go to the doc subdirectory and enter "make alldoc". |
| 97 | |
108 | |
| 98 | Isn't rxvt-unicode supposed to be small? Don't all those features bloat? |
109 | Isn't rxvt-unicode supposed to be small? Don't all those features bloat? |
| 99 | I often get asked about this, and I think, no, they didn't cause extra |
110 | I often get asked about this, and I think, no, they didn't cause extra |
| 100 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
111 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
| … | |
… | |
| 146 | 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 |
| 147 | are defined by things like X11, pseudo terminals, locale support and |
158 | are defined by things like X11, pseudo terminals, locale support and |
| 148 | unix domain sockets, which are all less portable than C++ itself. |
159 | unix domain sockets, which are all less portable than C++ itself. |
| 149 | |
160 | |
| 150 | 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 |
| 151 | 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 |
| 152 | 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 |
| 153 | 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 |
| 154 | system with a minimal config: |
165 | my system with a minimal config: |
| 155 | |
166 | |
| 156 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
167 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
| 157 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
168 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
| 158 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
169 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
| 159 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
170 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
| 160 | |
171 | |
| 161 | And here is rxvt-unicode: |
172 | And here is rxvt-unicode: |
| 162 | |
173 | |
| 163 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
174 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
| 164 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
175 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
| 165 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
176 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
| 166 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
177 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
| 167 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
178 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
| 168 | |
179 | |
| 169 | No large bloated libraries (of course, none were linked in statically), |
180 | No large bloated libraries (of course, none were linked in statically), |
| 170 | except maybe libX11 :) |
181 | except maybe libX11 :) |
| 171 | |
182 | |
| 172 | Rendering, Font & Look and Feel Issues |
183 | Rendering, Font & Look and Feel Issues |
| … | |
… | |
| 177 | rite of passage: ... and you failed. |
188 | rite of passage: ... and you failed. |
| 178 | |
189 | |
| 179 | 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 |
| 180 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
191 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
| 181 | |
192 | |
| 182 | 1. Use inheritPixmap: |
193 | 1. Use transparent mode: |
| 183 | |
194 | |
| 184 | Esetroot wallpaper.jpg |
195 | Esetroot wallpaper.jpg |
| 185 | urxvt -ip -tint red -sh 40 |
196 | urxvt -tr -tint red -sh 40 |
| 186 | |
197 | |
| 187 | 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 |
| 188 | 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. |
| 189 | |
202 | |
| 190 | 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 |
| 191 | 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 |
| 192 | your picture with gimp or any other tool: |
205 | your picture with gimp or any other tool: |
| 193 | |
206 | |
| 194 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
207 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
| 195 | urxvt -pixmap background.xpm -pe automove-background |
208 | urxvt -pixmap "background.jpg;:root" |
| 196 | |
209 | |
| 197 | That works. If you think it doesn't, you lack XPM and Perl support, or |
210 | That works. If you think it doesn't, you lack GDK-PixBuf support, or you |
| 198 | you are unable to read. |
211 | are unable to read. |
| 199 | |
212 | |
| 200 | 3. Use an ARGB visual: |
213 | 3. Use an ARGB visual: |
| 201 | |
214 | |
| 202 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
215 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
| 203 | |
216 | |
| … | |
… | |
| 297 | What's with this bold/blink stuff? |
310 | What's with this bold/blink stuff? |
| 298 | If no bold colour is set via "colorBD:", bold will invert text using the |
311 | If no bold colour is set via "colorBD:", bold will invert text using the |
| 299 | standard foreground colour. |
312 | standard foreground colour. |
| 300 | |
313 | |
| 301 | For the standard background colour, blinking will actually make the text |
314 | For the standard background colour, blinking will actually make the text |
| 302 | blink when compiled with "--enable-blinking". with standard colours. |
315 | blink when compiled with "--enable-text-blink". Without |
| 303 | Without "--enable-blinking", the blink attribute will be ignored. |
316 | "--enable-text-blink", the blink attribute will be ignored. |
| 304 | |
317 | |
| 305 | 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 |
| 306 | foreground/background colors. |
319 | foreground/background colours. |
| 307 | |
320 | |
| 308 | color0-7 are the low-intensity colors. |
321 | color0-7 are the low-intensity colours. |
| 309 | |
322 | |
| 310 | color8-15 are the corresponding high-intensity colors. |
323 | color8-15 are the corresponding high-intensity colours. |
| 311 | |
324 | |
| 312 | 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? |
| 313 | You can change the screen colors at run-time using ~/.Xdefaults |
326 | You can change the screen colours at run-time using ~/.Xdefaults |
| 314 | resources (or as long-options). |
327 | resources (or as long-options). |
| 315 | |
328 | |
| 316 | 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 |
| 317 | the murky brown that passes for low-intensity yellow: |
330 | the murky brown that passes for low-intensity yellow: |
| 318 | |
331 | |
| … | |
… | |
| 332 | URxvt.color12: #0000FF |
345 | URxvt.color12: #0000FF |
| 333 | URxvt.color13: #FF00FF |
346 | URxvt.color13: #FF00FF |
| 334 | URxvt.color14: #00FFFF |
347 | URxvt.color14: #00FFFF |
| 335 | URxvt.color15: #FFFFFF |
348 | URxvt.color15: #FFFFFF |
| 336 | |
349 | |
| 337 | And here is a more complete set of non-standard colors. |
350 | And here is a more complete set of non-standard colours. |
| 338 | |
351 | |
| 339 | URxvt.cursorColor: #dc74d1 |
352 | URxvt.cursorColor: #dc74d1 |
| 340 | URxvt.pointerColor: #dc74d1 |
353 | URxvt.pointerColor: #dc74d1 |
| 341 | URxvt.background: #0e0e0e |
354 | URxvt.background: #0e0e0e |
| 342 | URxvt.foreground: #4ad5e1 |
355 | URxvt.foreground: #4ad5e1 |
| … | |
… | |
| 409 | has been designed yet). |
422 | has been designed yet). |
| 410 | |
423 | |
| 411 | Until then, you might get away with switching fonts at runtime (see "Can |
424 | Until then, you might get away with switching fonts at runtime (see "Can |
| 412 | I switch the fonts at runtime?" later in this document). |
425 | I switch the fonts at runtime?" later in this document). |
| 413 | |
426 | |
|
|
427 | How can I make mplayer display video correctly? |
|
|
428 | We are working on it, in the meantime, as a workaround, use something |
|
|
429 | like: |
|
|
430 | |
|
|
431 | urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...' |
|
|
432 | |
| 414 | Keyboard, Mouse & User Interaction |
433 | Keyboard, Mouse & User Interaction |
| 415 | The new selection selects pieces that are too big, how can I select single words? |
434 | The new selection selects pieces that are too big, how can I select single words? |
| 416 | If you want to select e.g. alphanumeric words, you can use the following |
435 | If you want to select e.g. alphanumeric words, you can use the following |
| 417 | setting: |
436 | setting: |
| 418 | |
437 | |
| … | |
… | |
| 424 | To get a selection that is very similar to the old code, try this |
443 | To get a selection that is very similar to the old code, try this |
| 425 | pattern: |
444 | pattern: |
| 426 | |
445 | |
| 427 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
446 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
| 428 | |
447 | |
| 429 | Please also note that the *LeftClick Shift-LeftClik* combination also |
448 | Please also note that the *LeftClick Shift-LeftClick* combination also |
| 430 | selects words like the old code. |
449 | selects words like the old code. |
| 431 | |
450 | |
| 432 | I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
451 | I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
| 433 | You can disable the perl extension completely by setting the |
452 | You can disable the perl extension completely by setting the |
| 434 | perl-ext-common resource to the empty string, which also keeps |
453 | perl-ext-common resource to the empty string, which also keeps |
| … | |
… | |
| 462 | You can permanently switch this feature off by disabling the "readline" |
481 | You can permanently switch this feature off by disabling the "readline" |
| 463 | extension: |
482 | extension: |
| 464 | |
483 | |
| 465 | URxvt.perl-ext-common: default,-readline |
484 | URxvt.perl-ext-common: default,-readline |
| 466 | |
485 | |
| 467 | My numerical keypad acts weird and generates differing output? |
486 | My numeric keypad acts weird and generates differing output? |
| 468 | Some Debian GNUL/Linux users seem to have this problem, although no |
487 | Some Debian GNU/Linux users seem to have this problem, although no |
| 469 | specific details were reported so far. It is possible that this is |
488 | specific details were reported so far. It is possible that this is |
| 470 | caused by the wrong "TERM" setting, although the details of whether and |
489 | caused by the wrong "TERM" setting, although the details of whether and |
| 471 | how this can happen are unknown, as "TERM=rxvt" should offer a |
490 | how this can happen are unknown, as "TERM=rxvt" should offer a |
| 472 | compatible keymap. See the answer to the previous question, and please |
491 | compatible keymap. See the answer to the previous question, and please |
| 473 | report if that helped. |
492 | report if that helped. |
| 474 | |
493 | |
| 475 | My Compose (Multi_key) key is no longer working. |
494 | My Compose (Multi_key) key is no longer working. |
| 476 | The most common causes for this are that either your locale is not set |
495 | The most common causes for this are that either your locale is not set |
| 477 | correctly, or you specified a preeditStyle that is not supported by your |
496 | correctly, or you specified a preeditType that is not supported by your |
| 478 | input method. For example, if you specified OverTheSpot and your input |
497 | input method. For example, if you specified OverTheSpot and your input |
| 479 | method (e.g. the default input method handling Compose keys) does not |
498 | method (e.g. the default input method handling Compose keys) does not |
| 480 | support this (for instance because it is not visual), then rxvt-unicode |
499 | support this (for instance because it is not visual), then rxvt-unicode |
| 481 | will continue without an input method. |
500 | will continue without an input method. |
| 482 | |
501 | |
| 483 | In this case either do not specify a preeditStyle or specify more than |
502 | In this case either do not specify a preeditType or specify more than |
| 484 | one pre-edit style, such as OverTheSpot,Root,None. |
503 | one pre-edit style, such as OverTheSpot,Root,None. |
|
|
504 | |
|
|
505 | If it still doesn't work, then maybe your input method doesn't support |
|
|
506 | compose sequences - to fall back to the built-in one, make sure you |
|
|
507 | don't specify an input method via "-im" or "XMODIFIERS". |
| 485 | |
508 | |
| 486 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 |
509 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 |
| 487 | Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
510 | Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
| 488 | international keyboards) or simply use ISO 14755 support to your |
511 | international keyboards) or simply use ISO 14755 support to your |
| 489 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
512 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
| 490 | other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet |
513 | other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet |
| 491 | escape character and so on. |
514 | escape character and so on. |
| 492 | |
515 | |
| 493 | Mouse cut/paste suddenly no longer works. |
516 | Mouse cut/paste suddenly no longer works. |
| 494 | Make sure that mouse reporting is actually turned off since killing some |
517 | Make sure that mouse reporting is actually turned off since killing some |
| 495 | editors prematurely may leave the mouse in mouse report mode. I've heard |
518 | editors prematurely may leave it active. I've heard that tcsh may use |
| 496 | that tcsh may use mouse reporting unless it otherwise specified. A quick |
519 | mouse reporting unless it is otherwise specified. A quick check is to |
| 497 | check is to see if cut/paste works when the Alt or Shift keys are |
520 | see if cut/paste works when the Alt or Shift keys are pressed. |
| 498 | depressed. |
|
|
| 499 | |
521 | |
| 500 | What's with the strange Backspace/Delete key behaviour? |
522 | What's with the strange Backspace/Delete key behaviour? |
| 501 | Assuming that the physical Backspace key corresponds to the Backspace |
523 | Assuming that the physical Backspace key corresponds to the Backspace |
| 502 | keysym (not likely for Linux ... see the following question) there are |
524 | keysym (not likely for Linux ... see the following question) there are |
| 503 | two standard values that can be used for Backspace: "^H" and "^?". |
525 | two standard values that can be used for Backspace: "^H" and "^?". |
| 504 | |
526 | |
| 505 | Historically, either value is correct, but rxvt-unicode adopts the |
527 | Historically, either value is correct, but rxvt-unicode adopts the |
| 506 | debian policy of using "^?" when unsure, because it's the one and only |
528 | debian policy of using "^?" when unsure, because it's the one and only |
| 507 | correct choice :). |
529 | correct choice :). |
| 508 | |
530 | |
| 509 | Rxvt-unicode tries to inherit the current stty settings and uses the |
531 | It is possible to toggle between "^H" and "^?" with the DECBKM private |
| 510 | value of `erase' to guess the value for backspace. If rxvt-unicode |
532 | mode: |
| 511 | wasn't started from a terminal (say, from a menu or by remote shell), |
|
|
| 512 | then the system value of `erase', which corresponds to CERASE in |
|
|
| 513 | <termios.h>, will be used (which may not be the same as your stty |
|
|
| 514 | setting). |
|
|
| 515 | |
|
|
| 516 | For starting a new rxvt-unicode: |
|
|
| 517 | |
533 | |
| 518 | # use Backspace = ^H |
534 | # use Backspace = ^H |
| 519 | $ stty erase ^H |
535 | $ stty erase ^H |
| 520 | $ urxvt |
536 | $ printf "\e[?67h" |
| 521 | |
537 | |
| 522 | # use Backspace = ^? |
538 | # use Backspace = ^? |
| 523 | $ stty erase ^? |
539 | $ stty erase ^? |
| 524 | $ urxvt |
540 | $ printf "\e[?67l" |
| 525 | |
|
|
| 526 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
|
|
| 527 | |
|
|
| 528 | For an existing rxvt-unicode: |
|
|
| 529 | |
|
|
| 530 | # use Backspace = ^H |
|
|
| 531 | $ stty erase ^H |
|
|
| 532 | $ echo -n "^[[36h" |
|
|
| 533 | |
|
|
| 534 | # use Backspace = ^? |
|
|
| 535 | $ stty erase ^? |
|
|
| 536 | $ echo -n "^[[36l" |
|
|
| 537 | |
541 | |
| 538 | This helps satisfy some of the Backspace discrepancies that occur, but |
542 | This helps satisfy some of the Backspace discrepancies that occur, but |
| 539 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
543 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
| 540 | properly reflects that. |
544 | properly reflects that. |
| 541 | |
545 | |
| … | |
… | |
| 557 | use the `keysym' resource to alter the keystrings associated with |
561 | use the `keysym' resource to alter the keystrings associated with |
| 558 | keysyms. |
562 | keysyms. |
| 559 | |
563 | |
| 560 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
564 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
| 561 | |
565 | |
|
|
566 | URxvt.keysym.Prior: \033[5~ |
|
|
567 | URxvt.keysym.Next: \033[6~ |
| 562 | URxvt.keysym.Home: \033[1~ |
568 | URxvt.keysym.Home: \033[7~ |
| 563 | URxvt.keysym.End: \033[4~ |
569 | URxvt.keysym.End: \033[8~ |
| 564 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
| 565 | URxvt.keysym.C-slash: \033<C-/> |
|
|
| 566 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
| 567 | URxvt.keysym.C-grave: \033<C-`> |
|
|
| 568 | URxvt.keysym.C-comma: \033<C-,> |
|
|
| 569 | URxvt.keysym.C-period: \033<C-.> |
|
|
| 570 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
| 571 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
| 572 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
| 573 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
| 574 | URxvt.keysym.S-space: \033<S-Space> |
|
|
| 575 | URxvt.keysym.M-Up: \033<M-Up> |
570 | URxvt.keysym.Up: \033[A |
| 576 | URxvt.keysym.M-Down: \033<M-Down> |
571 | URxvt.keysym.Down: \033[B |
|
|
572 | URxvt.keysym.Right: \033[C |
| 577 | URxvt.keysym.M-Left: \033<M-Left> |
573 | URxvt.keysym.Left: \033[D |
| 578 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
| 579 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
| 580 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
| 581 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
|
|
| 582 | |
574 | |
| 583 | See some more examples in the documentation for the keysym resource. |
575 | See some more examples in the documentation for the keysym resource. |
| 584 | |
576 | |
| 585 | 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 |
577 | 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 |
| 586 | KP_Insert == Insert |
578 | KP_Insert == Insert |
| … | |
… | |
| 629 | develop for myself mostly, so I actually use most of the extensions I |
621 | develop for myself mostly, so I actually use most of the extensions I |
| 630 | write. |
622 | write. |
| 631 | |
623 | |
| 632 | The selection stuff mainly makes the selection perl-error-message aware |
624 | The selection stuff mainly makes the selection perl-error-message aware |
| 633 | and tells it to convert perl error messages into vi-commands to load the |
625 | and tells it to convert perl error messages into vi-commands to load the |
| 634 | relevant file and go tot he error line number. |
626 | relevant file and go to the error line number. |
| 635 | |
627 | |
| 636 | URxvt.scrollstyle: plain |
628 | URxvt.scrollstyle: plain |
| 637 | URxvt.secondaryScroll: true |
629 | URxvt.secondaryScroll: true |
| 638 | |
630 | |
| 639 | As the documentation says: plain is the preferred scrollbar for the |
631 | As the documentation says: plain is the preferred scrollbar for the |
| … | |
… | |
| 712 | my purposes, it works, and gives a different look, as my normal |
704 | my purposes, it works, and gives a different look, as my normal |
| 713 | (Non-bold) font is already bold, and I want to see a difference between |
705 | (Non-bold) font is already bold, and I want to see a difference between |
| 714 | bold and normal fonts. |
706 | bold and normal fonts. |
| 715 | |
707 | |
| 716 | Please note that I used the "urxvt" instance name and not the "URxvt" |
708 | Please note that I used the "urxvt" instance name and not the "URxvt" |
| 717 | class name. Thats because I use different configs for different |
709 | class name. That is because I use different configs for different |
| 718 | purposes, for example, my IRC window is started with "-name IRC", and |
710 | purposes, for example, my IRC window is started with "-name IRC", and |
| 719 | uses these defaults: |
711 | uses these defaults: |
| 720 | |
712 | |
| 721 | IRC*title: IRC |
713 | IRC*title: IRC |
| 722 | IRC*geometry: 87x12+535+542 |
714 | IRC*geometry: 87x12+535+542 |
| … | |
… | |
| 726 | IRC*boldFont: suxuseuro |
718 | IRC*boldFont: suxuseuro |
| 727 | IRC*colorBD: white |
719 | IRC*colorBD: white |
| 728 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
720 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
| 729 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
721 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
| 730 | |
722 | |
| 731 | "Alt-Shift-1" and "Alt-Shift-2" switch between two different font sizes. |
723 | "Alt-Ctrl-1" and "Alt-Ctrl-2" switch between two different font sizes. |
| 732 | "suxuseuro" allows me to keep an eye (and actually read) stuff while |
724 | "suxuseuro" allows me to keep an eye (and actually read) stuff while |
| 733 | keeping a very small window. If somebody pastes something complicated |
725 | keeping a very small window. If somebody pastes something complicated |
| 734 | (e.g. japanese), I temporarily switch to a larger font. |
726 | (e.g. japanese), I temporarily switch to a larger font. |
| 735 | |
727 | |
| 736 | The above is all in my ".Xdefaults" (I don't use ".Xresources" nor |
728 | The above is all in my ".Xdefaults" (I don't use ".Xresources" nor |
| 737 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
729 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
| 738 | file for different hosts, for example, on ym main desktop, I use: |
730 | file for different hosts, for example, on my main desktop, I use: |
| 739 | |
731 | |
| 740 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
732 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
| 741 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
733 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
| 742 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
734 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
| 743 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
735 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
| … | |
… | |
| 772 | The terminal description used by rxvt-unicode is not as widely available |
764 | The terminal description used by rxvt-unicode is not as widely available |
| 773 | as that for xterm, or even rxvt (for which the same problem often |
765 | as that for xterm, or even rxvt (for which the same problem often |
| 774 | arises). |
766 | arises). |
| 775 | |
767 | |
| 776 | The correct solution for this problem is to install the terminfo, this |
768 | The correct solution for this problem is to install the terminfo, this |
| 777 | can be done like this (with ncurses' infocmp and works as user and |
769 | can be done by simply installing rxvt-unicode on the remote system as |
| 778 | admin): |
770 | well (in case you have a nice package manager ready), or you can install |
|
|
771 | the terminfo database manually like this (with ncurses infocmp. works as |
|
|
772 | user and root): |
| 779 | |
773 | |
| 780 | REMOTE=remotesystem.domain |
774 | REMOTE=remotesystem.domain |
| 781 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
775 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
| 782 | |
|
|
| 783 | ... or by installing rxvt-unicode normally on the remote system, |
|
|
| 784 | |
776 | |
| 785 | One some systems you might need to set $TERMINFO to the full path of |
777 | One some systems you might need to set $TERMINFO to the full path of |
| 786 | $HOME/.terminfo for this to work. |
778 | $HOME/.terminfo for this to work. |
| 787 | |
779 | |
| 788 | If you cannot or do not want to do this, then you can simply set |
780 | If you cannot or do not want to do this, then you can simply set |
| … | |
… | |
| 798 | URxvt.termName: rxvt |
790 | URxvt.termName: rxvt |
| 799 | |
791 | |
| 800 | If you don't plan to use rxvt (quite common...) you could also replace |
792 | If you don't plan to use rxvt (quite common...) you could also replace |
| 801 | the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". |
793 | the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". |
| 802 | |
794 | |
|
|
795 | nano fails with "Error opening terminal: rxvt-unicode" |
|
|
796 | This exceptionally confusing and useless error message is printed by |
|
|
797 | nano when it can't find the terminfo database. Nothing is wrong with |
|
|
798 | your terminal, read the previous answer for a solution. |
|
|
799 | |
| 803 | "tic" outputs some error when compiling the terminfo entry. |
800 | "tic" outputs some error when compiling the terminfo entry. |
| 804 | Most likely it's the empty definition for "enacs=". Just replace it by |
801 | Most likely it's the empty definition for "enacs=". Just replace it by |
| 805 | "enacs=\E[0@" and try again. |
802 | "enacs=\E[0@" and try again. |
| 806 | |
803 | |
| 807 | "bash"'s readline does not work correctly under urxvt. |
804 | "bash"'s readline does not work correctly under urxvt. |
| … | |
… | |
| 817 | cases. You can also create a termcap entry by using terminfo's infocmp |
814 | cases. You can also create a termcap entry by using terminfo's infocmp |
| 818 | program like this: |
815 | program like this: |
| 819 | |
816 | |
| 820 | infocmp -C rxvt-unicode |
817 | infocmp -C rxvt-unicode |
| 821 | |
818 | |
| 822 | Or you could use this termcap entry, generated by the command above: |
819 | Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap, |
| 823 | |
820 | generated by the command above. |
| 824 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
|
|
| 825 | :am:bw:eo:km:mi:ms:xn:xo:\ |
|
|
| 826 | :co#80:it#8:li#24:lm#0:\ |
|
|
| 827 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
|
|
| 828 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
|
|
| 829 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
|
|
| 830 | :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
|
|
| 831 | :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
|
|
| 832 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
|
|
| 833 | :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
|
|
| 834 | :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
|
|
| 835 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
|
|
| 836 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
|
|
| 837 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
|
|
| 838 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
|
|
| 839 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
|
|
| 840 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
|
|
| 841 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
|
|
| 842 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
|
|
| 843 | :vs=\E[?25h: |
|
|
| 844 | |
821 | |
| 845 | Why does "ls" no longer have coloured output? |
822 | Why does "ls" no longer have coloured output? |
| 846 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
823 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
| 847 | decide whether a terminal has colour, but uses its own configuration |
824 | decide whether a terminal has colour, but uses its own configuration |
| 848 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
825 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
| … | |
… | |
| 862 | Why doesn't vim/emacs etc. make use of italic? |
839 | Why doesn't vim/emacs etc. make use of italic? |
| 863 | See next entry. |
840 | See next entry. |
| 864 | |
841 | |
| 865 | Why are the secondary screen-related options not working properly? |
842 | Why are the secondary screen-related options not working properly? |
| 866 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
843 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
| 867 | distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
844 | distributions break rxvt-unicode by setting "TERM" to "rxvt", which |
| 868 | setting "TERM" to "rxvt", which doesn't have these extra features. |
845 | doesn't have these extra features. Unfortunately, some of these |
| 869 | Unfortunately, some of these (most notably, again, Debian GNU/Linux) |
|
|
| 870 | furthermore fail to even install the "rxvt-unicode" terminfo file, so |
846 | furthermore fail to even install the "rxvt-unicode" terminfo file, so |
| 871 | you will need to install it on your own (See the question When I log-in |
847 | you will need to install it on your own (See the question When I log-in |
| 872 | to another system it tells me about missing terminfo data? on how to do |
848 | to another system it tells me about missing terminfo data? on how to do |
| 873 | this). |
849 | this). |
| 874 | |
850 | |
| … | |
… | |
| 985 | For scim, use "@im=SCIM". You can see what input method servers are |
961 | For scim, use "@im=SCIM". You can see what input method servers are |
| 986 | running with this command: |
962 | running with this command: |
| 987 | |
963 | |
| 988 | xprop -root XIM_SERVERS |
964 | xprop -root XIM_SERVERS |
| 989 | |
965 | |
| 990 | * |
|
|
| 991 | |
|
|
| 992 | My input method wants <some encoding> but I want UTF-8, what can I do? |
966 | My input method wants <some encoding> but I want UTF-8, what can I do? |
| 993 | You can specify separate locales for the input method and the rest of |
967 | You can specify separate locales for the input method and the rest of |
| 994 | the terminal, using the resource "imlocale": |
968 | the terminal, using the resource "imlocale": |
| 995 | |
969 | |
| 996 | URxvt.imlocale: ja_JP.EUC-JP |
970 | URxvt.imlocale: ja_JP.EUC-JP |
| … | |
… | |
| 1009 | cannot be completely avoided even if both sides cooperate. |
983 | cannot be completely avoided even if both sides cooperate. |
| 1010 | |
984 | |
| 1011 | So the only workaround is not to kill your Input Method Servers. |
985 | So the only workaround is not to kill your Input Method Servers. |
| 1012 | |
986 | |
| 1013 | Operating Systems / Package Maintaining |
987 | Operating Systems / Package Maintaining |
| 1014 | I am using Debian GNU/Linux and have a problem... |
|
|
| 1015 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
| 1016 | patches that considerably change the behaviour of rxvt-unicode (but |
|
|
| 1017 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
| 1018 | the original rxvt-unicode author please download and install the genuine |
|
|
| 1019 | version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
|
|
| 1020 | the problem. If you cannot, chances are that the problems are specific |
|
|
| 1021 | to Debian GNU/Linux, in which case it should be reported via the Debian |
|
|
| 1022 | Bug Tracking System (use "reportbug" to report the bug). |
|
|
| 1023 | |
|
|
| 1024 | For other problems that also affect the Debian package, you can and |
|
|
| 1025 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
| 1026 | bug in the Debian version and it serves as a reminder for other users |
|
|
| 1027 | that might encounter the same issue. |
|
|
| 1028 | |
|
|
| 1029 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
988 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
| 1030 | You should build one binary with the default options. configure now |
989 | You should build one binary with the default options. configure now |
| 1031 | enables most useful options, and the trend goes to making them |
990 | enables most useful options, and the trend goes to making them |
| 1032 | runtime-switchable, too, so there is usually no drawback to enabling |
991 | runtime-switchable, too, so there is usually no drawback to enabling |
| 1033 | them, except higher disk and possibly memory usage. The perl interpreter |
992 | them, except higher disk and possibly memory usage. The perl interpreter |
| 1034 | should be enabled, as important functionality (menus, selection, likely |
993 | should be enabled, as important functionality (menus, selection, likely |
| 1035 | more in the future) depends on it. |
994 | more in the future) depends on it. |
| 1036 | |
995 | |
| 1037 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
996 | You should not overwrite the "perl-ext-common" and "perl-ext" resources |
| 1038 | system-wide (except maybe with "defaults"). This will result in useful |
997 | system-wide (except maybe with "defaults"). This will result in useful |
| 1039 | behaviour. If your distribution aims at low memory, add an empty |
998 | behaviour. If your distribution aims at low memory, add an empty |
| 1040 | "perl-ext-common" resource to the app-defaults file. This will keep the |
999 | "perl-ext-common" resource to the app-defaults file. This will keep the |
| 1041 | perl interpreter disabled until the user enables it. |
1000 | perl interpreter disabled until the user enables it. |
| 1042 | |
1001 | |
| … | |
… | |
| 1059 | This forking is done as the very first within main(), which is very |
1018 | This forking is done as the very first within main(), which is very |
| 1060 | early and reduces possible bugs to initialisation code run before |
1019 | early and reduces possible bugs to initialisation code run before |
| 1061 | main(), or things like the dynamic loader of your system, which should |
1020 | main(), or things like the dynamic loader of your system, which should |
| 1062 | result in very little risk. |
1021 | result in very little risk. |
| 1063 | |
1022 | |
| 1064 | On Solaris 9, many line-drawing characters are too wide. |
|
|
| 1065 | Seems to be a known bug, read |
|
|
| 1066 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
|
|
| 1067 | following ugly workaround to get non-double-wide-characters working: |
|
|
| 1068 | |
|
|
| 1069 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
|
|
| 1070 | |
|
|
| 1071 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
1023 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
| 1072 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in |
1024 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in |
| 1073 | your compile environment, or an implementation that implements it, |
1025 | your compile environment, or an implementation that implements it, |
| 1074 | whether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
1026 | whether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
| 1075 | wchar_t is represented as unicode. |
1027 | wchar_t is represented as unicode. |
| … | |
… | |
| 1077 | As you might have guessed, FreeBSD does neither define this symbol nor |
1029 | As you might have guessed, FreeBSD does neither define this symbol nor |
| 1078 | does it support it. Instead, it uses its own internal representation of |
1030 | does it support it. Instead, it uses its own internal representation of |
| 1079 | wchar_t. This is, of course, completely fine with respect to standards. |
1031 | wchar_t. This is, of course, completely fine with respect to standards. |
| 1080 | |
1032 | |
| 1081 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
1033 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
| 1082 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
1034 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t). |
| 1083 | |
1035 | |
| 1084 | "__STDC_ISO_10646__" is the only sane way to support multi-language apps |
1036 | "__STDC_ISO_10646__" is the only sane way to support multi-language apps |
| 1085 | in an OS, as using a locale-dependent (and non-standardized) |
1037 | in an OS, as using a locale-dependent (and non-standardized) |
| 1086 | representation of wchar_t makes it impossible to convert between wchar_t |
1038 | representation of wchar_t makes it impossible to convert between wchar_t |
| 1087 | (as used by X11 and your applications) and any other encoding without |
1039 | (as used by X11 and your applications) and any other encoding without |
| … | |
… | |
| 1097 | |
1049 | |
| 1098 | The rxvt-unicode author insists that the right way to fix this is in the |
1050 | The rxvt-unicode author insists that the right way to fix this is in the |
| 1099 | system libraries once and for all, instead of forcing every app to carry |
1051 | system libraries once and for all, instead of forcing every app to carry |
| 1100 | complete replacements for them :) |
1052 | complete replacements for them :) |
| 1101 | |
1053 | |
| 1102 | I use Solaris 9 and it doesn't compile/work/etc. |
|
|
| 1103 | Try the diff in doc/solaris9.patch as a base. It fixes the worst |
|
|
| 1104 | problems with "wcwidth" and a compile problem. |
|
|
| 1105 | |
|
|
| 1106 | How can I use rxvt-unicode under cygwin? |
1054 | How can I use rxvt-unicode under cygwin? |
| 1107 | rxvt-unicode should compile and run out of the box on cygwin, using the |
1055 | rxvt-unicode should compile and run out of the box on cygwin, using the |
| 1108 | X11 libraries that come with cygwin. libW11 emulation is no longer |
1056 | X11 libraries that come with cygwin. libW11 emulation is no longer |
| 1109 | supported (and makes no sense, either, as it only supported a single |
1057 | supported (and makes no sense, either, as it only supported a single |
| 1110 | font). I recommend starting the X-server in "-multiwindow" or |
1058 | font). I recommend starting the X-server in "-multiwindow" or |
| … | |
… | |
| 1113 | |
1061 | |
| 1114 | At the time of this writing, cygwin didn't seem to support any |
1062 | At the time of this writing, cygwin didn't seem to support any |
| 1115 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
1063 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
| 1116 | likely limited to 8-bit encodings. |
1064 | likely limited to 8-bit encodings. |
| 1117 | |
1065 | |
|
|
1066 | Character widths are not correct. |
|
|
1067 | urxvt uses the system wcwidth function to know the information about the |
|
|
1068 | width of characters, so on systems with incorrect locale data you will |
|
|
1069 | likely get bad results. Two notorious examples are Solaris 9, where |
|
|
1070 | single-width characters like U+2514 are reported as double-width, and |
|
|
1071 | Darwin 8, where combining chars are reported having width 1. |
|
|
1072 | |
|
|
1073 | The solution is to upgrade your system or switch to a better one. A |
|
|
1074 | possibly working workaround is to use a wcwidth implementation like |
|
|
1075 | |
|
|
1076 | http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c |
|
|
1077 | |
