about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 2067Kartik K. Agaram2015-08-242-3/+3
|
* 2066Kartik K. Agaram2015-08-241-3/+1
|
* 2065 - arrow bugfixKartik K. Agaram2015-08-241-3/+37
|
* 2064Kartik K. Agaram2015-08-244-6/+6
| | | | Adjust spaces in 'stash'.
* 2063Kartik K. Agaram2015-08-241-1/+1
| | | | Extend deadline for run-interactive.
* 2062Kartik K. Agaram2015-08-2366-2622/+4547
|
* 2061 - clear status only after repaintKartik K. Agaram2015-08-221-4/+8
|
* 2060 - even more efficient up/downKartik K. Agaram2015-08-222-4/+103
|
* 2059Kartik K. Agaram2015-08-221-1/+1
|
* 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
|
* 2054Kartik K. Agaram2015-08-213-3/+2
|
* 2053Kartik K. Agaram2015-08-211-13/+49
|
* 2052Kartik K. Agaram2015-08-211-1/+1
| | | | | | | If I try to run a single test and it triggers an error the trace gets saved in the current directory, as if I was trying to log an interactive run. Then when I try to rerun the test the trace tries to load as mu code, and hilarity ensues. Just log interactive runs in .traces/ as well.
* 2051Kartik K. Agaram2015-08-211-12/+12
| | | | | Forgot to fix chessboard tests during commit 2022: running sandboxes in separate routines.
* 2050Kartik K. Agaram2015-08-211-2/+2
|
* 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.
* 2043Kartik K. Agaram2015-08-202-1/+2
| | | | | Traces were changing based on whether I was loading a .mu file with 'main' or not.
* 2042Kartik K. Agaram2015-08-201-0/+7
| | | | | | Mouse clicks towards the right of very wide windows weren't working. Turns out to be a limitation of the X10 protocol: https://github.com/nsf/termbox-go/issues/32
* 2041Kartik K. Agaram2015-08-201-2/+1
|
* 2040Kartik K. Agaram2015-08-201-3/+16
| | | | Back to checking render performance everywhere.
* 2039 - warn on unbalanced '['Kartik K. Agaram2015-08-195-17/+139
|
* 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.
* 2031 - always position cursor after repaintingKartik K. Agaram2015-08-171-0/+25
|
* 2030Kartik K. Agaram2015-08-171-13/+39
|
* 2029Kartik K. Agaram2015-08-172-6/+29
|
* 2028Kartik K. Agaram2015-08-161-1/+1
|
* 2027Kartik K. Agaram2015-08-161-33/+57
|
* 2026Kartik K. Agaram2015-08-161-27/+57
|
* 2025 - back to speeding up renderKartik K. Agaram2015-08-161-31/+31
| | | | | | | | | First step: drop the existing optimization of not redrawing after every character. Gives the editor a jumpy feel. I'm also hoisting the render into handle-keyboard event as a first step to duplicating it everywhere. One test temporarily failing: we're gonna sometimes forget to draw the line below editors.
* 2024 - mu environment now handles infinite loops gracefullyKartik K. Agaram2015-08-162-3/+44
|
* 2023 - give routines time limitsKartik K. Agaram2015-08-161-0/+63
|
* 2022 - run sandboxes in separate routinesKartik K. Agaram2015-08-163-39/+104
|
* 2021Kartik K. Agaram2015-08-161-5/+3
|
* 2020Kartik K. Agaram2015-08-161-11/+2
|
* 2019 - simplify run-interactive furtherKartik K. Agaram2015-08-161-41/+25
| | | | | | | | | | | | | | | | | This time I'm getting rid of all the intricate SCREEN hacking. Now run-interactive is idiomatic: it creates a recipe on the fly, runs it, and returns various results and stats about it. One big consequence of the recipe now running interactively inside a local-scope: you can't just use numeric addresses anymore -- not without using /raw. Fixed one of the tests to reflect this. I realize now that I don't really want my students to be using raw addresses in their sandboxes, even if that was my idiom for lower-level scenarios. Hopefully running sandboxes in separate (synchronous) routines will be easy now.
* 2018Kartik K. Agaram2015-08-151-1/+0
| | | | | Still trying to minimize the work around run-interactive so I can build it with a sandboxed routine rather than a call in editor space.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-17 18:36:12 +0000