… | |
… | |
20 | DUMB: support tex fonts |
20 | DUMB: support tex fonts |
21 | |
21 | |
22 | TODO: investigate -pe tabbed -g 80x25 being 23 not 24 or 25 lines |
22 | TODO: investigate -pe tabbed -g 80x25 being 23 not 24 or 25 lines |
23 | TODO: zero scorllback buffer should free memory |
23 | TODO: zero scorllback buffer should free memory |
24 | TODO: kuake |
24 | TODO: kuake |
25 | TODO: depth resource not working(?) |
|
|
26 | TODO: fix the flaw in the url regex jost pointed out |
25 | TODO: fix the flaw in the url regex jost pointed out |
27 | TODO: look into the selection hilight patch |
26 | TODO: look into the selection hilight patch |
28 | TODO: implement smartcase-like search in searchable-scrollback |
27 | TODO: implement smartcase-like search in searchable-scrollback |
29 | TODO: check wether -depth works as resource |
|
|
30 | TODO: digital clock gets nuked after searching |
28 | TODO: digital clock gets nuked after searching |
31 | TODO: read .Xdefaults even when we have display resources, but give them lower priority |
29 | - INCOMPATIBLE CHANGE: this version will always read ~/.Xdefaults, earlier |
|
|
30 | versions only read it if display-resources (usually from .Xresources) |
|
|
31 | are not set. This avoids the #1 FAQ ("why isn't my resource used") and |
|
|
32 | seems to be logical behaviour, too. .Xdefaults resources have a lower |
|
|
33 | priority than display-specific resources. |
32 | - use less "correct" color scaling that is compatible with libX11 and Xft |
34 | - use less "correct" color scaling that is compatible with libX11 and Xft |
33 | (avoids off-by-one colors resulting in striped backgrounds). |
35 | (avoids off-by-one colors resulting in striped backgrounds). |
34 | - the "depth" resource is now respected. |
36 | - the "depth" resource is now respected. |
35 | - add FORCE_UNBUFFERED_XFT define to features.h. |
37 | - add FORCE_UNBUFFERED_XFT define to features.h. |
36 | - double-buffered xft drawing did suffer from pixel offset issues |
38 | - double-buffered xft drawing did suffer from pixel offset issues |