diff options
| author | Nicholas Marriott <nicholas.marriott@gmail.com> | 2016-05-31 22:13:44 +0100 |
|---|---|---|
| committer | Nicholas Marriott <nicholas.marriott@gmail.com> | 2016-05-31 22:13:44 +0100 |
| commit | 20d2a31b40430df73aea3089a5258bf7f7ec68d2 (patch) | |
| tree | 29c47635dfe5ba16282389f54977757e717a80ef | |
| parent | c7a0f56c71109496a30b7f3463b717a6f0aca1ff (diff) | |
| download | rtmux-20d2a31b40430df73aea3089a5258bf7f7ec68d2.tar.gz rtmux-20d2a31b40430df73aea3089a5258bf7f7ec68d2.tar.bz2 rtmux-20d2a31b40430df73aea3089a5258bf7f7ec68d2.zip | |
Update TODO.
| -rw-r--r-- | TODO | 7 |
1 files changed, 6 insertions, 1 deletions
@@ -119,7 +119,12 @@ or even guarantee that cmdq->c != NULL and provide a better way to tell when in the config file - then we use cmdq->c if we need a client w/o a session else cmd_current_client - * optimize pane redraws, 20120318184853.GK10965@yelena.nicm.ath.cx + * we do more work than we should if a single read() contains operations + that cancel each other out: for example, writing twice to the same + cell, or writing and then clearing a line; it would be nice to + optimize these. would it mean processing the entire read() data first + then applying changes? or an initial optimization step? or something + else? - miscellaneous * way to keep a job running just read its last line of output for #() |