aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Eklöf <daniel@ekloef.se>2020-02-05 19:23:20 +0000
committerDaniel Eklöf <daniel@ekloef.se>2020-02-05 19:23:20 +0000
commit92376eae01341e8f051f4ceba13d38980312a152 (patch)
tree4a492a5a16ece00bbcd9d3f985e4bef560809237
parentmain: add --print-pid=FILE|FD (diff)
term: language
-rw-r--r--terminal.c10
1 files changed, 5 insertions, 5 deletions
diff --git a/terminal.c b/terminal.c
index 6152c739..35ecb845 100644
--- a/terminal.c
+++ b/terminal.c
@@ -168,15 +168,15 @@ fdm_ptmx(struct fdm *fdm, int fd, int events, void *data)
}
/*
- * We likely need to re-render. But, we don't want to
- * do it immediately. Often, a single client operation
- * is done through multiple writes. Many times, we're
- * so fast that we render mid-operation frames.
+ * We likely need to re-render. But, we don't want to do it
+ * immediately. Often, a single client update is done through
+ * multiple writes. This could lead to us rendering one frame with
+ * "intermediate" state.
*
* For example, we might end up rendering a frame
* where the client just erased a line, while in the
* next frame, the client wrote to the same line. This
- * causes screen "flashes".
+ * causes screen "flickering".
*
* Mitigate by always incuring a small delay before
* rendering the next frame. This gives the client