… | |
… | |
23 | How do I know which rxvt-unicode version I'm using? |
23 | How do I know which rxvt-unicode version I'm using? |
24 | The version number is displayed with the usage (-h). Also the escape |
24 | The version number is displayed with the usage (-h). Also the escape |
25 | sequence "ESC [ 8 n" sets the window title to the version number. |
25 | sequence "ESC [ 8 n" sets the window title to the version number. |
26 | |
26 | |
27 | I am using Debian GNU/Linux and have a problem... |
27 | I am using Debian GNU/Linux and have a problem... |
28 | The Debian GNU/Linux package of rxvt-unicode contains large patches |
28 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
29 | that considerably change the behaviour of rxvt-unicode. Before |
29 | patches that considerably change the behaviour of rxvt-unicode. |
30 | reporting a bug to the original rxvt-unicode author please download |
30 | Before reporting a bug to the original rxvt-unicode author please |
31 | and install the genuine version |
31 | download and install the genuine version |
32 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
32 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
33 | problem. If you cannot, chances are that the problems are specific |
33 | problem. If you cannot, chances are that the problems are specific |
34 | to Debian GNU/Linux, in which case it should be reported via the |
34 | to Debian GNU/Linux, in which case it should be reported via the |
35 | Debian Bug Tracking System (use "reportbug" to report the bug). |
35 | Debian Bug Tracking System (use "reportbug" to report the bug). |
36 | |
36 | |
… | |
… | |
65 | |
65 | |
66 | URxvt.termName: rxvt |
66 | URxvt.termName: rxvt |
67 | |
67 | |
68 | If you don't plan to use rxvt (quite common...) you could also |
68 | If you don't plan to use rxvt (quite common...) you could also |
69 | replace the rxvt terminfo file with the rxvt-unicode one. |
69 | replace the rxvt terminfo file with the rxvt-unicode one. |
|
|
70 | |
|
|
71 | "tic" outputs some error when compiling the terminfo entry. |
|
|
72 | Most likely it's the empty definition for "enacs=". Just replace it |
|
|
73 | by "enacs=\E[0@" and try again. |
70 | |
74 | |
71 | "bash"'s readline does not work correctly under rxvt. |
75 | "bash"'s readline does not work correctly under rxvt. |
72 | I need a termcap file entry. |
76 | I need a termcap file entry. |
73 | One reason you might want this is that some distributions or |
77 | One reason you might want this is that some distributions or |
74 | operating systems still compile some programs using the |
78 | operating systems still compile some programs using the |
… | |
… | |
333 | |
337 | |
334 | I use Solaris 9 and it doesn't compile/work/etc. |
338 | I use Solaris 9 and it doesn't compile/work/etc. |
335 | Try the diff in doc/solaris9.patch as a base. It fixes the worst |
339 | Try the diff in doc/solaris9.patch as a base. It fixes the worst |
336 | problems with "wcwidth" and a compile problem. |
340 | problems with "wcwidth" and a compile problem. |
337 | |
341 | |
|
|
342 | How can I use rxvt-unicode under cygwin? |
|
|
343 | rxvt-unicode should compile and run out of the box on cygwin, using |
|
|
344 | the X11 libraries that come with cygwin. libW11 emulation is no |
|
|
345 | longer supported (and makes no sense, either, as it only supported a |
|
|
346 | single font). I recommend starting the X-server in "-multiwindow" or |
|
|
347 | "-rootless" mode instead, which will result in similar look&feel as |
|
|
348 | the old libW11 emulation. |
|
|
349 | |
|
|
350 | At the time of this writing, cygwin didn't seem to support any |
|
|
351 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
|
|
352 | likely limited to 8-bit encodings. |
|
|
353 | |
338 | How does rxvt-unicode determine the encoding to use? |
354 | How does rxvt-unicode determine the encoding to use? |
339 | Is there an option to switch encodings? |
355 | Is there an option to switch encodings? |
340 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
356 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
341 | and no specific "utf-8" mode, such as xterm. In fact, it doesn't |
357 | and no specific "utf-8" mode, such as xterm. In fact, it doesn't |
342 | even know about UTF-8 or any other encodings with respect to |
358 | even know about UTF-8 or any other encodings with respect to |
… | |
… | |
453 | it gets worse, as rxvt-unicode then uses 8 bytes per screen cell. |
469 | it gets worse, as rxvt-unicode then uses 8 bytes per screen cell. |
454 | |
470 | |
455 | Can I speed up Xft rendering somehow? |
471 | Can I speed up Xft rendering somehow? |
456 | Yes, the most obvious way to speed it up is to avoid Xft entirely, |
472 | Yes, the most obvious way to speed it up is to avoid Xft entirely, |
457 | as it is simply slow. If you still want Xft fonts you might try to |
473 | as it is simply slow. If you still want Xft fonts you might try to |
458 | disable antialiasing (by appending ":antialiasing=false"), which |
474 | disable antialiasing (by appending ":antialias=false"), which saves |
459 | saves lots of memory and also speeds up rendering considerably. |
475 | lots of memory and also speeds up rendering considerably. |
460 | |
476 | |
461 | Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
477 | Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
462 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
478 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
463 | fall back to it's default font search list it will prefer X11 core |
479 | fall back to it's default font search list it will prefer X11 core |
464 | fonts, because they are small and fast, and then use Xft fonts. It |
480 | fonts, because they are small and fast, and then use Xft fonts. It |
… | |
… | |
536 | URxvt.color14: #73f7ff |
552 | URxvt.color14: #73f7ff |
537 | URxvt.color7: #e1dddd |
553 | URxvt.color7: #e1dddd |
538 | URxvt.color15: #e1dddd |
554 | URxvt.color15: #e1dddd |
539 | |
555 | |
540 | How can I start rxvtd in a race-free way? |
556 | How can I start rxvtd in a race-free way? |
541 | Despite it's name, rxvtd is not a real daemon, but more like a |
557 | Try "rxvtd -f -o", which tells rxvtd to open the display, create the |
542 | server that answers rxvtc's requests, so it doesn't background |
558 | listening socket and then fork. |
543 | itself. |
|
|
544 | |
|
|
545 | To ensure rxvtd is listening on it's socket, you can use the |
|
|
546 | following method to wait for the startup message before continuing: |
|
|
547 | |
|
|
548 | { rxvtd & } | read |
|
|
549 | |
559 | |
550 | What's with the strange Backspace/Delete key behaviour? |
560 | What's with the strange Backspace/Delete key behaviour? |
551 | Assuming that the physical Backspace key corresponds to the |
561 | Assuming that the physical Backspace key corresponds to the |
552 | BackSpace keysym (not likely for Linux ... see the following |
562 | BackSpace keysym (not likely for Linux ... see the following |
553 | question) there are two standard values that can be used for |
563 | question) there are two standard values that can be used for |