about summary refs log tree commit diff stats
path: root/edit.mu
Commit message (Collapse)AuthorAgeFilesLines
* 1804Kartik K. Agaram2015-07-171-16/+16
|
* 1803Kartik K. Agaram2015-07-171-2/+2
| | | | | Bring back my optimizations for avoiding unnecessary work. But they shouldn't be needed for correctness, and they aren't.
* 1802 - cleanupKartik K. Agaram2015-07-171-31/+45
|
* 1801 - assertion failures fixedKartik K. Agaram2015-07-171-12/+11
| | | | | | Now we can investigate the remaining issues: print-string to main screen not working to print 'screen:' print-integer to toy screen not working to print '4'
* 1800 - ah, found the bounds-checking bugKartik K. Agaram2015-07-171-7/+11
| | | | I was counting locations when I should have been counting elements.
* 1799 - continue to debug memory corruption of 1795Kartik K. Agaram2015-07-171-208/+147
| | | | | | | | | | | | Things I figured out: - 'row' in render-screen doesn't perfectly track cursor-row in screen - proximal cause was forgetting to add left:number to stop-printing - trying to print to screen outside bounds was silently succeeding and corrupting simulated memory - if we silently ignore prints outside bounds things are fine But why are prints outside screen bounds working? We should be accessing screen data using 'index', and that's checking its bounds.
* 1798 - support for deleting sandboxesKartik K. Agaram2015-07-161-1/+144
|
* 1797 - widget to delete sandboxKartik K. Agaram2015-07-161-7/+24
| | | | Doesn't work yet.
* 1796 - temporarily undo 1795Kartik K. Agaram2015-07-161-150/+2
| | | | | Debugging simulated-screen support is taking too long, and I suddenly have a few higher priorities.
* 1795 - still debugging screen-in-screen renderingKartik K. Agaram2015-07-161-2/+150
| | | | I'm writing to location 'screen' somehow that's not the raw location.
* 1792 - better semantics for ctrl-kKartik K. Agaram2015-07-151-3/+122
| | | | More evidence that the choice of 'before-cursor' was inspired.
* 1791 - delete to start/end of lineKartik K. Agaram2015-07-151-0/+166
|
* 1790 - move to end of lineKartik K. Agaram2015-07-151-0/+145
|
* 1789 - move to start of line with home/ctrl-aKartik K. Agaram2015-07-151-2/+133
|
* 1788Kartik K. Agaram2015-07-151-1/+3
|
* 1787 - clear warnings between runsKartik K. Agaram2015-07-151-0/+30
|
* 1786 - render only the side that changedKartik K. Agaram2015-07-151-8/+33
|
* 1785Kartik K. Agaram2015-07-151-5/+23
|
* 1784 - start making render more efficientKartik K. Agaram2015-07-151-1/+0
| | | | | We stopped rendering just the widget under focus when we switched away from the simplistic list of editors. Need to bring that back.
* 1783 - stable if sluggish on caleb's 512MB serverKartik K. Agaram2015-07-141-6/+45
| | | | | Profiling shows the bulk of time is spent in read_memory, canonize, absolutize. But I'm not sure how to optimize those places.
* 1780 - now we always reclaim local scopesKartik K. Agaram2015-07-131-26/+26
| | | | | | But still no difference in either memory footprint or in running time. This will teach me -- for the umpteenth time -- to optimize before measuring.
* 1773 - update all mu recipes to new-default-spaceKartik K. Agaram2015-07-131-26/+26
| | | | | Turns out to not affect memory utilization or run-time. At all. But still looks nicer and requires less fudging on our part.
* 1765Kartik K. Agaram2015-07-111-18/+52
| | | | | As usual, trying to fix this manually was a false economy. Writing this test in the first place would have made debugging much simpler.
* 1764 - editor now updates all sandboxesKartik K. Agaram2015-07-111-15/+46
| | | | Finally, albeit too late for my demo.
* 1761 - multiple sandboxes seems to be workingKartik K. Agaram2015-07-111-1/+0
| | | | No idea why this was wrong, but whatever..
* 1760 - failing test for multiple sandboxesKartik K. Agaram2015-07-111-53/+76
| | | | | | | | | We're starting to hit the limits of my 8GB RAM, to the point where I'm starting to economize on the size of the screen. Time to start thinking about reclaiming memory. Anyways, test now fails in the right place. I'm failing to propertly render intermediate lines between sandboxes.
* 1759Kartik K. Agaram2015-07-111-2/+2
|
* 1758 - now clear sandbox editor on F10Kartik K. Agaram2015-07-111-13/+47
| | | | We're ready to start displaying multiple sandboxes.
* 1757Kartik K. Agaram2015-07-111-7/+12
|
* 1756Kartik K. Agaram2015-07-111-7/+19
|
* 1755Kartik K. Agaram2015-07-101-13/+13
|
* 1754Kartik K. Agaram2015-07-101-15/+16
|
* 1753 - all tests passing againKartik K. Agaram2015-07-101-41/+47
| | | | Cleanup below editors is now all done.
* 1752 - cursor positioning fixedKartik K. Agaram2015-07-101-6/+8
|
* 1751 - sluggishness fixedKartik K. Agaram2015-07-101-36/+21
| | | | | | | Ah, I was indeed double-rendering, but somehow it was still hard to see the problem past that preliminary diagnosis. Still two failing tests to fix.
* 1748Kartik K. Agaram2015-07-101-3/+3
|
* 1747Kartik K. Agaram2015-07-101-4/+3
|
* 1745 - hoist warning/response strings out of editor-dataKartik K. Agaram2015-07-101-276/+308
| | | | | | | | | | Still ugly as hell. Some tests failing, but they're most likely wrong. We need to test cursor positioning at the level of the environment and take it away from the responsibilities of individual editors. Also bring back the line at the bottom of each editor. The non-test run ('main' in edit.mu) is completely borked. Sluggish as hell, and I can't seem to switch focus to the sandbox editor.
* 1744 - support just two editors rather than a listKartik K. Agaram2015-07-091-244/+147
| | | | | Current model: you click on something to put it on the editor at the top of the column. Worth a shot.
* 1743Kartik K. Agaram2015-07-091-177/+185
|
* 1742Kartik K. Agaram2015-07-091-23/+19
|
* 1741 - start cleaning up editor-dataKartik K. Agaram2015-07-091-19/+14
|
* 1740 - correct redraw after reducing editor sizeKartik K. Agaram2015-07-091-20/+17
| | | | | I probably need another test like editor-clears-last-line-on-backspace, but we aren't testing the boundary, and we're pushing on anyway.
* 1739Kartik K. Agaram2015-07-091-1/+0
| | | | Leaves a line blank after printing result/warnings, for some reason.
* 1738Kartik K. Agaram2015-07-091-9/+1
|
* 1737 - allow editors to 'grow'Kartik K. Agaram2015-07-091-16/+24
|
* 1735Kartik K. Agaram2015-07-081-0/+1
| | | | | | Hmm, this is undesirable, that recipes don't need to explicitly reply. Need to fix. Also need to have run-interactive create scenarios at some point.
* 1734Kartik K. Agaram2015-07-081-42/+20
| | | | Pushing back some of the weight of repetitive boilerplate.
* 1733 - load all recipes before running sandboxesKartik K. Agaram2015-07-081-37/+152
| | | | | This is starting to look good! I need to add some tests for render-string, but we'll see.
* 1731 - ah, now fully responsiveKartik K. Agaram2015-07-081-1/+5
| | | | The trick is to check for more events and not bother rendering if so.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2025-01-28 18:31:26 +0000