about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 1867 - keep tests from corrupting lesson/ directoryKartik K. Agaram2015-07-282-3/+8
|
* 1866Kartik K. Agaram2015-07-281-3/+3
|
* 1865 - emergency hotkey; mouse sometimes doesn't workKartik K. Agaram2015-07-281-0/+13
|
* 1864Kartik K. Agaram2015-07-282-12/+13
|
* 1863 - two bugfixes in deleting sandboxesKartik K. Agaram2015-07-282-4/+22
| | | | | Forgot to show screen after delete, and 'release' events were causing double deletions.
* 1862Kartik K. Agaram2015-07-281-1/+1
|
* 1861 - bugfix: saving sandboxesKartik K. Agaram2015-07-271-0/+2
| | | | Still no tests for save/restore. Gigantic hacks.
* 1860 - new primitive: $systemKartik K. Agaram2015-07-275-195/+217
| | | | Also reorganize my miscellaneous hacky primitives.
* 1859Kartik K. Agaram2015-07-271-1/+1
|
* 1858 - switch from F10 to F4Kartik K. Agaram2015-07-271-37/+37
| | | | F10 seems to be a popular keybinding in the window manager.
* 1857 - editor supports autoindentKartik K. Agaram2015-07-271-4/+80
|
* 1856Kartik K. Agaram2015-07-261-2/+3
|
* 1855Kartik K. Agaram2015-07-261-5/+5
|
* 1854 - 'tab' key supportKartik K. Agaram2015-07-261-4/+33
|
* 1853Kartik K. Agaram2015-07-2569-2104/+2579
|
* 1852Kartik K. Agaram2015-07-251-1/+1
|
* 1851Kartik K. Agaram2015-07-251-2/+2
|
* 1850 - fix a warning on 32-bit systemsKartik K. Agaram2015-07-251-1/+1
|
* 1849Kartik K. Agaram2015-07-255-49/+4
|
* 1848 - core instructions now check for ingredientsKartik K. Agaram2015-07-2528-154/+358
| | | | Also standardized warnings.
* 1847Kartik K. Agaram2015-07-251-2/+2
|
* 1846Kartik K. Agaram2015-07-253-6/+6
|
* 1845 - never ever redefine the scenario's recipeKartik K. Agaram2015-07-252-7/+27
| | | | | | A couple of times now I've accidentally named a scenario the same thing as a recipe inside it that I define using 'run' or something. The resulting infinite loop is invariably non-trivial to debug.
* 1844 - explicitly end each trace lineKartik K. Agaram2015-07-2529-203/+205
| | | | | | | | | More verbose, but it saves trouble when debugging; there's never something you thought should be traced but just never came out the other end. Also got rid of fatal errors entirely. Everything's a warning now, and code after a warning isn't guaranteed to run.
* 1843Kartik K. Agaram2015-07-241-0/+4
|
* 1842 - get layers building again after 2 weeksKartik K. Agaram2015-07-246-121/+120
| | | | | Also, turns out I haven't been building 999spaces.cc in my default build. Now fixed.
* 1841 - reenable old layersKartik K. Agaram2015-07-242-9/+16
|
* 1840Kartik K. Agaram2015-07-241-1/+0
|
* 1839 - clear entire screen on F10Kartik K. Agaram2015-07-241-2/+14
| | | | | Just in case we had many lines of warnings before that are now cleared up. Again, I'm feeling confident enough to not write a test.
* 1838Kartik K. Agaram2015-07-241-17/+19
|
* 1837Kartik K. Agaram2015-07-241-4/+4
| | | | | | Don't die on unbalanced '{'. I won't bother adding more tests for warnings. Suffice it to say that we need to gradually eliminate all asserts that check for illegal mu code.
* 1836Kartik K. Agaram2015-07-241-2/+8
|
* 1835Kartik K. Agaram2015-07-241-3/+12
|
* 1834Kartik K. Agaram2015-07-241-4/+8
|
* 1833Kartik K. Agaram2015-07-241-1/+8
|
* 1832Kartik K. Agaram2015-07-244-3/+38
|
* 1831Kartik K. Agaram2015-07-241-0/+28
|
* 1830Kartik K. Agaram2015-07-234-7/+10
|
* 1829Kartik K. Agaram2015-07-233-7/+38
|
* 1828Kartik K. Agaram2015-07-231-6/+6
|
* 1827Kartik K. Agaram2015-07-231-2/+2
|
* 1826 - edit: start carefully showing all errorsKartik K. Agaram2015-07-214-4/+55
| | | | | | | | | | | | | | | | | | | | | Eventually we might be able to get rid of die entirely. This is just a preliminary stab at a random error. In the process I ran into two issues that have impeded debugging before: a) Naming conflicts within scenarios are a real no-no. I need to warn on them, but the rules are getting complicated: Always print warnings on redefine But not in interactive mode Or in scenarios checking warning behavior Unless the scenario recipe itself is overridden b) Now that we've added collect_layers and a long time can go between traces, debugging is a minefield because trace lines don't print to screen immediately after they're created. Need to do something about that. Maybe explicitly trigger collection by tracing '\n' or something. These are the next two items on my todo list.
* 1825Kartik K. Agaram2015-07-211-0/+10
|
* 1824Kartik K. Agaram2015-07-201-1/+2
|
* 1823 - restore sandboxes from previous sessionKartik K. Agaram2015-07-192-7/+43
| | | | | | Starting to feel some need to test this persistence support. Next time I'll create a fake storage handle and support for 'assume-storage filename'.
* 1822Kartik K. Agaram2015-07-193-11/+11
|
* 1821Kartik K. Agaram2015-07-191-82/+82
|
* 1820Kartik K. Agaram2015-07-191-2/+2
|
* 1819Kartik K. Agaram2015-07-181-0/+0
| | | | How did this image get corrupted?
* 1818Kartik K. Agaram2015-07-1828-382/+1785
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-02 15:39:27 +0000