| … | |
… | |
| 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 |
