| … | |
… | |
| 469 | 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. |
| 470 | |
470 | |
| 471 | Can I speed up Xft rendering somehow? |
471 | Can I speed up Xft rendering somehow? |
| 472 | 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, |
| 473 | 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 |
| 474 | disable antialiasing (by appending ":antialiasing=false"), which |
474 | disable antialiasing (by appending ":antialias=false"), which saves |
| 475 | saves lots of memory and also speeds up rendering considerably. |
475 | lots of memory and also speeds up rendering considerably. |
| 476 | |
476 | |
| 477 | 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? |
| 478 | 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 |
| 479 | 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 |
| 480 | 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 |
| … | |
… | |
| 552 | URxvt.color14: #73f7ff |
552 | URxvt.color14: #73f7ff |
| 553 | URxvt.color7: #e1dddd |
553 | URxvt.color7: #e1dddd |
| 554 | URxvt.color15: #e1dddd |
554 | URxvt.color15: #e1dddd |
| 555 | |
555 | |
| 556 | How can I start rxvtd in a race-free way? |
556 | How can I start rxvtd in a race-free way? |
| 557 | 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 |
| 558 | server that answers rxvtc's requests, so it doesn't background |
558 | listening socket and then fork. |
| 559 | itself. |
|
|
| 560 | |
|
|
| 561 | To ensure rxvtd is listening on it's socket, you can use the |
|
|
| 562 | following method to wait for the startup message before continuing: |
|
|
| 563 | |
|
|
| 564 | { rxvtd & } | read |
|
|
| 565 | |
559 | |
| 566 | What's with the strange Backspace/Delete key behaviour? |
560 | What's with the strange Backspace/Delete key behaviour? |
| 567 | Assuming that the physical Backspace key corresponds to the |
561 | Assuming that the physical Backspace key corresponds to the |
| 568 | BackSpace keysym (not likely for Linux ... see the following |
562 | BackSpace keysym (not likely for Linux ... see the following |
| 569 | question) there are two standard values that can be used for |
563 | question) there are two standard values that can be used for |
