about summary refs log tree commit diff stats
path: root/edit.mu
Commit message (Collapse)AuthorAgeFilesLines
* 2100 - starting to flesh out coalescing of undo operationsKartik K. Agaram2015-08-291-2/+17
|
* 2099 - undo support for moving to start/end of lineKartik K. Agaram2015-08-291-0/+200
|
* 2098 - undo support for page-up/downKartik K. Agaram2015-08-291-0/+164
|
* 2097 - undo support for arrow keysKartik K. Agaram2015-08-291-78/+246
|
* 2096 - clear redo when adding to undoKartik K. Agaram2015-08-291-3/+59
| | | | One drawback of my approach: if you move the cursor you lose your redo.
* 2095Kartik K. Agaram2015-08-281-49/+34
| | | | | | | | | | | | Finally terminate the experiment of keeping debug prints around. I'm also going to give up on maintaining counts. What we really need is two kinds of tracing: a) For tests, just the domain-specific facts, organized by labels. b) For debugging, just transient dumps to stdout. b) only works if stdout is clean by default. Hmm, I think this means 'stash' should be the transient kind of trace.
* 2094Kartik K. Agaram2015-08-281-45/+126
|
* 2093Kartik K. Agaram2015-08-281-6/+6
|
* 2092Kartik K. Agaram2015-08-281-5/+5
|
* 2091Kartik K. Agaram2015-08-281-30/+30
|
* 2090Kartik K. Agaram2015-08-281-0/+61
|
* 2089 - undo support for mouse clicksKartik K. Agaram2015-08-281-2/+75
|
* 2088 - warn on duplicate scenario nameKartik K. Agaram2015-08-281-1/+1
|
* 2087Kartik K. Agaram2015-08-281-1/+4
|
* 2086 - reset cursor on resizeKartik K. Agaram2015-08-281-13/+11
| | | | Also drop some redundancy with 'render-all'.
* 2085 - undo/redo now working for simple typingKartik K. Agaram2015-08-271-0/+50
| | | | | Not yet useable, because we never ever stop coalescing operations. That will happen when we introduce a second type of operation.
* 2084Kartik K. Agaram2015-08-271-23/+155
|
* 2083Kartik K. Agaram2015-08-261-2/+42
|
* 2082Kartik K. Agaram2015-08-261-1/+92
|
* 2081 - preliminary data model for undoKartik K. Agaram2015-08-261-4/+44
|
* 2079Kartik K. Agaram2015-08-261-12/+7
| | | | Cleanup 2078.
* 2078 - update entire screen on tb_present()Kartik K. Agaram2015-08-261-1/+11
| | | | | | | | | | | | | | | | | | | Termbox had been taking shortcuts when it thinks the screen hasn't changed, which doesn't work if some other process messes up the screen. The Go version has a Sync method in addition to Flush/tb_present for precisely this eventuality. But it feels like an unnecessary optimization given C's general speed. Just drop it altogether. --- This took me a long time to track down, and interestingly I found myself writing a new tracing primitive before I remembered how to selectively trace just certain layers during manual tests. I'm scared of generating traces not because of performance but because of the visual noise. Be aware of this. I'm going to clean up $log now. Maybe I should also stop using $print..
* 2077Kartik K. Agaram2015-08-251-1/+1
|
* 2076 - ensure cursor doesn't move on non-editor clicksKartik K. Agaram2015-08-241-6/+24
|
* 2069 - arrow bugfixKartik K. Agaram2015-08-241-9/+81
|
* 2068Kartik K. Agaram2015-08-241-2/+38
|
* 2066Kartik K. Agaram2015-08-241-3/+1
|
* 2065 - arrow bugfixKartik K. Agaram2015-08-241-3/+37
|
* 2061 - clear status only after repaintKartik K. Agaram2015-08-221-4/+8
|
* 2060 - even more efficient up/downKartik K. Agaram2015-08-221-2/+101
|
* 2058Kartik K. Agaram2015-08-221-1/+1
|
* 2057 - more efficient render on up/downKartik K. Agaram2015-08-221-8/+18
|
* 2056 - more efficient render on deleteKartik K. Agaram2015-08-211-3/+33
|
* 2055 - more efficient render on backspaceKartik K. Agaram2015-08-211-4/+38
|
* 2053Kartik K. Agaram2015-08-211-13/+49
|
* 2049 - snappier right-arrowKartik K. Agaram2015-08-211-2/+16
|
* 2048Kartik K. Agaram2015-08-211-0/+30
|
* 2047Kartik K. Agaram2015-08-201-5/+23
| | | | Back on a nice cadence of optimizing one case at a time.
* 2046Kartik K. Agaram2015-08-201-256/+67
| | | | | | | | | Redo some of the work of commits 2025-2032. We still need to create special-cases for each branch, but we'll now always update cursor in a single place. We'll also have handle-keyboard-event tell its caller whether it already took care of rendering or not. That way the caller only falls back to painting the entire screen when necessary. No more double-painting.
* 2045Kartik K. Agaram2015-08-201-26/+29
|
* 2044Kartik K. Agaram2015-08-201-8/+45
| | | | Don't render entire screen when appending to line.
* 2040Kartik K. Agaram2015-08-201-3/+16
| | | | Back to checking render performance everywhere.
* 2039 - warn on unbalanced '['Kartik K. Agaram2015-08-191-0/+29
|
* 2038 - toggle trace even if warnings or printsKartik K. Agaram2015-08-191-2/+5
|
* 2037Kartik K. Agaram2015-08-191-43/+42
| | | | | All scenarios should use just numeric locations, and 'run' should encapsulate the code under test.
* 2036Kartik K. Agaram2015-08-191-5/+5
| | | | | Standardize on whether screen operations will explicitly write to 'screen' inside scenarios. (Answer: not for setup code, at least.)
* 2035Kartik K. Agaram2015-08-181-0/+30
|
* 2034Kartik K. Agaram2015-08-171-7/+112
|
* 2033 - minimal render for appending charactersKartik K. Agaram2015-08-171-0/+29
|
* 2032Kartik K. Agaram2015-08-171-3/+3
| | | | | Get all tests passing again. Actually slower now than before, thanks to double-render when editing the sandbox side. But that is temporary.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-20 08:27:47 +0000