From 20d2a31b40430df73aea3089a5258bf7f7ec68d2 Mon Sep 17 00:00:00 2001 From: Nicholas Marriott Date: Tue, 31 May 2016 22:13:44 +0100 Subject: Update TODO. --- TODO | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/TODO b/TODO index 94fa38af..fbe91744 100644 --- a/TODO +++ b/TODO @@ -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 #() -- cgit