| … | |
… | |
| 448 | 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. |
| 449 | |
449 | |
| 450 | Can I speed up Xft rendering somehow? |
450 | Can I speed up Xft rendering somehow? |
| 451 | 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, |
| 452 | 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 |
| 453 | disable antialiasing (by appending ":antialiasing=false"), which |
453 | disable antialiasing (by appending ":antialias=false"), which saves |
| 454 | saves lots of memory and also speeds up rendering considerably. |
454 | lots of memory and also speeds up rendering considerably. |
| 455 | |
455 | |
| 456 | 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? |
| 457 | 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 |
| 458 | 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 |
| 459 | 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 |
| … | |
… | |
| 531 | URxvt.color14: #73f7ff |
531 | URxvt.color14: #73f7ff |
| 532 | URxvt.color7: #e1dddd |
532 | URxvt.color7: #e1dddd |
| 533 | URxvt.color15: #e1dddd |
533 | URxvt.color15: #e1dddd |
| 534 | |
534 | |
| 535 | How can I start rxvtd in a race-free way? |
535 | How can I start rxvtd in a race-free way? |
| 536 | Despite it's name, rxvtd is not a real daemon, but more like a |
536 | Try "rxvtd -f -o", which tells rxvtd to open the display, create the |
| 537 | server that answers rxvtc's requests, so it doesn't background |
537 | listening socket and then fork. |
| 538 | itself. |
|
|
| 539 | |
|
|
| 540 | To ensure rxvtd is listening on it's socket, you can use the |
|
|
| 541 | following method to wait for the startup message before continuing: |
|
|
| 542 | |
|
|
| 543 | { rxvtd & } | read |
|
|
| 544 | |
538 | |
| 545 | What's with the strange Backspace/Delete key behaviour? |
539 | What's with the strange Backspace/Delete key behaviour? |
| 546 | Assuming that the physical Backspace key corresponds to the |
540 | Assuming that the physical Backspace key corresponds to the |
| 547 | BackSpace keysym (not likely for Linux ... see the following |
541 | BackSpace keysym (not likely for Linux ... see the following |
| 548 | question) there are two standard values that can be used for |
542 | question) there are two standard values that can be used for |
