… | |
… | |
2 | How do I know which rxvt-unicode version I'm using? |
2 | How do I know which rxvt-unicode version I'm using? |
3 | The version number is displayed with the usage (-h). Also the escape |
3 | The version number is displayed with the usage (-h). Also the escape |
4 | sequence "ESC [ 8 n" sets the window title to the version number. |
4 | sequence "ESC [ 8 n" sets the window title to the version number. |
5 | |
5 | |
6 | I am using Debian GNU/Linux and have a problem... |
6 | I am using Debian GNU/Linux and have a problem... |
7 | The Debian GNU/Linux package of rxvt-unicode contains large patches |
7 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
8 | that considerably change the behaviour of rxvt-unicode. Before |
8 | patches that considerably change the behaviour of rxvt-unicode. |
9 | reporting a bug to the original rxvt-unicode author please download |
9 | Before reporting a bug to the original rxvt-unicode author please |
10 | and install the genuine version |
10 | download and install the genuine version |
11 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
11 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
12 | problem. If you cannot, chances are that the problems are specific |
12 | problem. If you cannot, chances are that the problems are specific |
13 | to Debian GNU/Linux, in which case it should be reported via the |
13 | to Debian GNU/Linux, in which case it should be reported via the |
14 | Debian Bug Tracking System (use "reportbug" to report the bug). |
14 | Debian Bug Tracking System (use "reportbug" to report the bug). |
15 | |
15 | |
… | |
… | |
45 | URxvt.termName: rxvt |
45 | URxvt.termName: rxvt |
46 | |
46 | |
47 | If you don't plan to use rxvt (quite common...) you could also |
47 | If you don't plan to use rxvt (quite common...) you could also |
48 | replace the rxvt terminfo file with the rxvt-unicode one. |
48 | replace the rxvt terminfo file with the rxvt-unicode one. |
49 | |
49 | |
|
|
50 | "tic" outputs some error when compiling the terminfo entry. |
|
|
51 | Most likely it's the empty definition for "enacs=". Just replace it |
|
|
52 | by "enacs=\E[0@" and try again. |
|
|
53 | |
50 | "bash"'s readline does not work correctly under rxvt. |
54 | "bash"'s readline does not work correctly under urxvt. |
51 | I need a termcap file entry. |
55 | I need a termcap file entry. |
52 | One reason you might want this is that some distributions or |
56 | One reason you might want this is that some distributions or |
53 | operating systems still compile some programs using the |
57 | operating systems still compile some programs using the |
54 | long-obsoleted termcap library (Fedora Core's bash is one example) |
58 | long-obsoleted termcap library (Fedora Core's bash is one example) |
55 | and rely on a termcap entry for "rxvt-unicode". |
59 | and rely on a termcap entry for "rxvt-unicode". |
… | |
… | |
166 | indeed look correct. |
170 | indeed look correct. |
167 | |
171 | |
168 | In that case, select a font of your taste and add it to the font |
172 | In that case, select a font of your taste and add it to the font |
169 | list, e.g.: |
173 | list, e.g.: |
170 | |
174 | |
171 | rxvt -fn basefont,font2,font3... |
175 | urxvt -fn basefont,font2,font3... |
172 | |
176 | |
173 | When rxvt-unicode sees a character, it will first look at the base |
177 | When rxvt-unicode sees a character, it will first look at the base |
174 | font. If the base font does not contain the character, it will go to |
178 | font. If the base font does not contain the character, it will go to |
175 | the next font, and so on. Specifying your own fonts will also speed |
179 | the next font, and so on. Specifying your own fonts will also speed |
176 | up this search and use less resources within rxvt-unicode and the |
180 | up this search and use less resources within rxvt-unicode and the |
… | |
… | |
312 | |
316 | |
313 | I use Solaris 9 and it doesn't compile/work/etc. |
317 | I use Solaris 9 and it doesn't compile/work/etc. |
314 | Try the diff in doc/solaris9.patch as a base. It fixes the worst |
318 | Try the diff in doc/solaris9.patch as a base. It fixes the worst |
315 | problems with "wcwidth" and a compile problem. |
319 | problems with "wcwidth" and a compile problem. |
316 | |
320 | |
|
|
321 | How can I use rxvt-unicode under cygwin? |
|
|
322 | rxvt-unicode should compile and run out of the box on cygwin, using |
|
|
323 | the X11 libraries that come with cygwin. libW11 emulation is no |
|
|
324 | longer supported (and makes no sense, either, as it only supported a |
|
|
325 | single font). I recommend starting the X-server in "-multiwindow" or |
|
|
326 | "-rootless" mode instead, which will result in similar look&feel as |
|
|
327 | the old libW11 emulation. |
|
|
328 | |
|
|
329 | At the time of this writing, cygwin didn't seem to support any |
|
|
330 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
|
|
331 | likely limited to 8-bit encodings. |
|
|
332 | |
317 | How does rxvt-unicode determine the encoding to use? |
333 | How does rxvt-unicode determine the encoding to use? |
318 | Is there an option to switch encodings? |
334 | Is there an option to switch encodings? |
319 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
335 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
320 | and no specific "utf-8" mode, such as xterm. In fact, it doesn't |
336 | and no specific "utf-8" mode, such as xterm. In fact, it doesn't |
321 | even know about UTF-8 or any other encodings with respect to |
337 | even know about UTF-8 or any other encodings with respect to |
… | |
… | |
432 | it gets worse, as rxvt-unicode then uses 8 bytes per screen cell. |
448 | it gets worse, as rxvt-unicode then uses 8 bytes per screen cell. |
433 | |
449 | |
434 | Can I speed up Xft rendering somehow? |
450 | Can I speed up Xft rendering somehow? |
435 | Yes, the most obvious way to speed it up is to avoid Xft entirely, |
451 | Yes, the most obvious way to speed it up is to avoid Xft entirely, |
436 | as it is simply slow. If you still want Xft fonts you might try to |
452 | as it is simply slow. If you still want Xft fonts you might try to |
437 | disable antialiasing (by appending ":antialiasing=false"), which |
453 | disable antialiasing (by appending ":antialias=false"), which saves |
438 | saves lots of memory and also speeds up rendering considerably. |
454 | lots of memory and also speeds up rendering considerably. |
439 | |
455 | |
440 | Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
456 | Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
441 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
457 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
442 | fall back to it's default font search list it will prefer X11 core |
458 | fall back to it's default font search list it will prefer X11 core |
443 | fonts, because they are small and fast, and then use Xft fonts. It |
459 | fonts, because they are small and fast, and then use Xft fonts. It |
… | |
… | |
449 | Mouse cut/paste suddenly no longer works. |
465 | Mouse cut/paste suddenly no longer works. |
450 | Make sure that mouse reporting is actually turned off since killing |
466 | Make sure that mouse reporting is actually turned off since killing |
451 | some editors prematurely may leave the mouse in mouse report mode. |
467 | some editors prematurely may leave the mouse in mouse report mode. |
452 | I've heard that tcsh may use mouse reporting unless it otherwise |
468 | I've heard that tcsh may use mouse reporting unless it otherwise |
453 | specified. A quick check is to see if cut/paste works when the Alt |
469 | specified. A quick check is to see if cut/paste works when the Alt |
454 | or Shift keys are depressed. See rxvt(7) |
470 | or Shift keys are depressed. See urxvt(7) |
455 | |
471 | |
456 | What's with this bold/blink stuff? |
472 | What's with this bold/blink stuff? |
457 | If no bold colour is set via "colorBD:", bold will invert text using |
473 | If no bold colour is set via "colorBD:", bold will invert text using |
458 | the standard foreground colour. |
474 | the standard foreground colour. |
459 | |
475 | |
… | |
… | |
514 | URxvt.color6: #73f7ff |
530 | URxvt.color6: #73f7ff |
515 | URxvt.color14: #73f7ff |
531 | URxvt.color14: #73f7ff |
516 | URxvt.color7: #e1dddd |
532 | URxvt.color7: #e1dddd |
517 | URxvt.color15: #e1dddd |
533 | URxvt.color15: #e1dddd |
518 | |
534 | |
519 | How can I start rxvtd in a race-free way? |
535 | How can I start urxvtd in a race-free way? |
520 | Despite it's name, rxvtd is not a real daemon, but more like a |
536 | Try "urxvtd -f -o", which tells urxvtd to open the display, create |
521 | server that answers rxvtc's requests, so it doesn't background |
537 | the listening socket and then fork. |
522 | itself. |
|
|
523 | |
|
|
524 | To ensure rxvtd is listening on it's socket, you can use the |
|
|
525 | following method to wait for the startup message before continuing: |
|
|
526 | |
|
|
527 | { rxvtd & } | read |
|
|
528 | |
538 | |
529 | What's with the strange Backspace/Delete key behaviour? |
539 | What's with the strange Backspace/Delete key behaviour? |
530 | Assuming that the physical Backspace key corresponds to the |
540 | Assuming that the physical Backspace key corresponds to the |
531 | BackSpace keysym (not likely for Linux ... see the following |
541 | BackSpace keysym (not likely for Linux ... see the following |
532 | question) there are two standard values that can be used for |
542 | question) there are two standard values that can be used for |
… | |
… | |
545 | |
555 | |
546 | For starting a new rxvt-unicode: |
556 | For starting a new rxvt-unicode: |
547 | |
557 | |
548 | # use Backspace = ^H |
558 | # use Backspace = ^H |
549 | $ stty erase ^H |
559 | $ stty erase ^H |
550 | $ rxvt |
560 | $ urxvt |
551 | |
561 | |
552 | # use Backspace = ^? |
562 | # use Backspace = ^? |
553 | $ stty erase ^? |
563 | $ stty erase ^? |
554 | $ rxvt |
564 | $ urxvt |
555 | |
565 | |
556 | Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7). |
566 | Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in urxvt(7). |
557 | |
567 | |
558 | For an existing rxvt-unicode: |
568 | For an existing rxvt-unicode: |
559 | |
569 | |
560 | # use Backspace = ^H |
570 | # use Backspace = ^H |
561 | $ stty erase ^H |
571 | $ stty erase ^H |
… | |
… | |
587 | There are some compile-time selections available via configure. |
597 | There are some compile-time selections available via configure. |
588 | Unless you have run "configure" with the "--disable-resources" |
598 | Unless you have run "configure" with the "--disable-resources" |
589 | option you can use the `keysym' resource to alter the keystrings |
599 | option you can use the `keysym' resource to alter the keystrings |
590 | associated with keysyms. |
600 | associated with keysyms. |
591 | |
601 | |
592 | Here's an example for a URxvt session started using "rxvt -name |
602 | Here's an example for a URxvt session started using "urxvt -name |
593 | URxvt" |
603 | URxvt" |
594 | |
604 | |
595 | URxvt.keysym.Home: \033[1~ |
605 | URxvt.keysym.Home: \033[1~ |
596 | URxvt.keysym.End: \033[4~ |
606 | URxvt.keysym.End: \033[4~ |
597 | URxvt.keysym.C-apostrophe: \033<C-'> |
607 | URxvt.keysym.C-apostrophe: \033<C-'> |