about summary refs log tree commit diff stats
path: root/cannot_write_tests_for
Commit message (Collapse)AuthorAgeFilesLines
* 3854Kartik K. Agaram2017-05-131-4/+6
| | | | Revert commits 3824, 3850 and 3852. We'll redo them more carefully.
* 3853Kartik K. Agaram2017-05-121-0/+6
| | | | | | Bring back commit 3844, albeit in simplified form. I'd forgotten that the one place where we still need to buffer rendering is when people hold down up/down arrow keys.
* 3844Kartik K. Agaram2017-05-061-4/+3
| | | | | Once I start optimizing most events to not repaint everything there's no need to be smart about queued-up events.
* 3824 - experiment: stop buffering in termboxKartik K. Agaram2017-04-161-5/+3
| | | | | | | | | | | | | | | | Now it's much more apparent why things are slow. You can see each repaint happening. Already I fixed one performance bug -- in clear-rest-of-screen. Since this subverts Mu's fake screen there may be bugs. Another salubrious side effect: I've finally internalized that switching to raw mode doesn't have to clear the screen. That was just an artifact of how termbox abstracted operations. Now I can conceive of using termbox to build a repl as well. (I was inspired to poke into termbox internals by http://viewsourcecode.org/snaptoken/kilo and https://github.com/antirez/linenoise)
* 3705 - switch to tested file-system primitivesKartik K. Agaram2016-12-111-1/+1
|
* 3629 - refcount commandline argsKartik K. Agaram2016-11-061-0/+1
|
* 3140Kartik K. Agaram2016-07-231-6/+7
| | | | | Manual tests for parse errors because scenarios can't handle assertion failures yet.
* 2192Kartik K. Agaram2015-09-141-0/+1
|
* 2141 - attempt to deal with slow networksKartik K. Agaram2015-09-041-0/+4
| | | | | | | | | | | | | On slow networks sometimes escape sequences were being partially consumed, causing junk to be added to the editor when you pressed arrow keys and so on. Now we have a way to wait. Empirically seems to work if I page-up and then scroll back up using up-arrow. Before I'd consistently get junk even on my local machine. Now I no longer do. If we still see problems I'll increase the wait time and see if the increase helps. Then we'll know more about this approach.
* 2140 - refresh screen after falling behindKartik K. Agaram2015-09-041-0/+5
This bit of code is complex enough now that I'm bothered I can't write tests for has-more-events?