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