about summary refs log tree commit diff stats
path: root/sandbox
Commit message (Collapse)AuthorAgeFilesLines
* 3498Kartik K. Agaram2016-10-141-1/+1
|
* 3490Kartik K. Agaram2016-10-098-148/+148
| | | | | | | | | | | | | | | Redo commit 3457. Basically there were 3 unicode characters we changed back then: solid horizontal line: 9473 -> 9472 fuzzy horizontal line: 9480 -> 9548 fuzzy vertical line: 9482 -> 9550 The solid horizontal line has no issues, so we just redo it here. For the other two, we'll perform the substitution only when rendering html. That gives us the best of both worlds: the scenario screens render right in html, and alt-tabbing continues to be snappy when running the edit/ app.
* 3489Kartik K. Agaram2016-10-0811-264/+264
| | | | | | | | | | Revert commit 3457, where I switched the unicode characters used in the edit/ app to something that doesn't render double-wide in html. It turns out that the new unicode characters made iTerm2 sluggish in alt-tabbing between windows. (Commit 3488 only fixed the screen-clearing issue.) I haven't reverted the html files. I'm going to redo commit 3457 next so the html files continue to render like they do now.
* 3457Kartik K. Agaram2016-10-0611-264/+264
| | | | | Switch around some unicode characters in the edit/ app so that it renders more cleanly in html (with monospace fonts).
* 3445Kartik K. Agaram2016-10-0611-395/+395
| | | | | | | Ugly that we didn't need 'screen' to provide a type in scenarios (because assume-screen expands to a definition of 'screen') but we did need a type for 'console'. Just never require types for special names in scenarios.
* 3429 - standardize Mu scenariosKartik K. Agaram2016-09-2811-814/+883
| | | | | | | | | | | | | A long-standing problem has been that I couldn't spread code across 'run' blocks because they were separate scopes, so I've ended up making them effectively comments. Running code inside a 'run' block is identical in every way to simply running the code directly. The 'run' block is merely a visual aid to separate setup from the component under test. In the process I've also standardized all Mu scenarios to always run in a local scope, and only use (raw) numeric addresses for values they want to check later.
* 3428Kartik K. Agaram2016-09-281-2/+2
|
* 3396Kartik K. Agaram2016-09-1712-747/+747
|
* 3391 - type abbreviations everywhereKartik K. Agaram2016-09-1712-1485/+1485
| | | | | | | | | Well, almost. I can't use them in some places in C++ where I'm just creating a temporary reagent without passing it through transforms. Like in some unit tests. I can't use them in memory-should-contain. And there's one remaining bug: I can't use abbreviations in a couple of places in 075channel.mu.
* 3369Kartik K. Agaram2016-09-151-12/+0
| | | | Fix some tests and make them less fragile.
* 3347Kartik K. Agaram2016-09-134-8/+8
| | | | | | | | | Done using 'text' type abbreviation everywhere. There's still a problem. If we define a function with a type abbreviation and then redefine it without, I think we end up creating separate variants. That seems wrong. Let's isolate a scenario for that next.
* 3341Kartik K. Agaram2016-09-123-4/+4
| | | | | | | Process type abbreviations in function headers. Still a couple of places where doing this causes strange errors. We'll track those down next.
* 3338Kartik K. Agaram2016-09-124-6/+6
| | | | Process type abbreviations in container definitions.
* 3337 - first use of type abbreviations: textKartik K. Agaram2016-09-1212-352/+352
| | | | | In the process I've uncover a couple of situations we don't support type abbreviations yet. They're next.
* 3234Kartik K. Agaram2016-08-202-1/+6
| | | | Fix some breaking sandbox/ tests.
* 3233 - change how Mu escapes stringsKartik K. Agaram2016-08-201-4/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | Thanks Sam Putman for helping think through this idea. When you encounter a backslash, strip it out and pass through any following run of backslashes. If we 'escaped' a single following character like C, then the character '\' would be the same as: '\\' escaped once '\\\\' escaped twice '\\\\\\\\' escaped thrice (8 backslashes) ..and so on, the number of backslashes doubling each time. Instead, our approach is to make the character '\' the same as: '\\' escaped once '\\\' escaped twice '\\\\' escaped thrice ..and so on, the number of backslashes merely increasing by one each time. This approach only works as long as backslashes aren't also overloaded to create special characters. So Mu doesn't follow C's approach of overloading backslashes both to escape quote characters and also as a notation for unprintable characters like '\n'.
* 3168 - skip loading recipe 'main' in edit/Kartik K. Agaram2016-08-123-3/+3
| | | | | | | This is part of efforts to allow students to transition gradually from the sandbox to running programs directly on the commandline, writing real scenarios, etc. Running on the commandline requires 'main', but overriding 'main' would mess up edit/ which is itself a Mu program.
* 3101 - purge .traces/ dir from repo historyKartik K. Agaram2016-07-051-4/+0
| | | | | | | | | | | | | | | | | | | | | I'd been toying with this idea for some time now given how large the repo had been growing. The final straw was noticing that people cloning the repo were having to wait *5 minutes*! That's not good, particularly for a project with 'tiny' in its description. After purging .traces/ clone time drops to 7 seconds in my tests. Major issue: some commits refer to .traces/ but don't really change anything there. That could get confusing :/ Minor issues: a) I've linked inside commits on GitHub like a half-dozen times online or over email. Those links are now liable to eventually break. (I seem to recall GitHub keeps them around as long as they get used at least once every 60 days, or something like that.) b) Numbering of commits is messed up because some commits only had changes to the .traces/ sub-directory.
* 3067Kartik K. Agaram2016-06-255-69/+69
|
* 3054 - keep cursor stable on resize in sandbox/Kartik K. Agaram2016-06-127-29/+112
| | | | This ports commits 3052 and 3053 from the edit/ app.
* 3041 - fix 3039 in sandbox/ as wellKartik K. Agaram2016-06-092-0/+42
|
* 3038 - track down a long-standing bugKartik K. Agaram2016-06-081-25/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | In some rare situations the editor would join a line with the next when it should simply wrap to the next screen row. Thanks Caleb and Ella Couch for finally running into a situation that was easy to reproduce. The scenario diffs are misleading on this commit. I had to: a) delete the obsolete 'editor-wraps-cursor-after-inserting-characters' because it was written back when a line just large enough to fit in a single line would not wrap: | | <-- screen boundary abcde These days it will wrap after making room for the wrap indicator: | | <-- screen boundary abcd↩ e b) rename editor-wraps-cursor-after-inserting-characters-2 to editor-wraps-cursor-after-inserting-characters-in-middle-of-line c) create a new scenario demonstrating the bug: editor-wraps-cursor-after-inserting-characters-at-end-of-line
* 2990Kartik K. Agaram2016-05-201-24/+14
| | | | | | | | | | Standardize quotes around reagents in error messages. I'm still sure there's issues. For example, the messages when type-checking 'copy'. I'm not putting quotes around them because in layer 60 I end up creating dilated reagents, and then it's a bit much to have quotes and (two kinds of) brackets. But I'm sure I'm doing that somewhere..
* 2984Kartik K. Agaram2016-05-191-0/+272
| | | | Missed a file.
* 2983 - migrate buttons over to sandbox/Kartik K. Agaram2016-05-199-354/+335
|
* 2975Kartik K. Agaram2016-05-194-9/+10
| | | | Clean up this helper before we start redoing sandbox menubars.
* 2954 - bugfix: $systemKartik K. Agaram2016-05-112-9/+7
| | | | The actual fix is in the layer rewriting literal strings.
* 2953 - use pgup/pgdn to scroll through sandboxesKartik K. Agaram2016-05-116-1569/+79
| | | | | | In the process I've also simplified the sandbox/ app. Since it's impossible for sandbox editors to span multiple pages, we can drop all scroll support altogether.
* 2928 - fix sandbox restore in edit/ and sandbox/Kartik K. Agaram2016-05-051-3/+7
| | | | | This had been broken ever since 2854, because we can't write tests for restore-snapshots at the moment.
* 2926Kartik K. Agaram2016-05-051-2/+4
| | | | Typo introduced in 2854.
* 2890Kartik K. Agaram2016-05-021-1/+1
|
* 2864 - replace all address:shared with just addressKartik K. Agaram2016-04-2411-1262/+1262
| | | | | | | Now that we no longer have non-shared addresses, we can just always track refcounts for all addresses. Phew!
* 2861 - 'maybe-convert' no longer returns addressKartik K. Agaram2016-04-239-121/+125
|
* 2854 - purge get-address from sandbox/ appKartik K. Agaram2016-04-2211-589/+644
|
* 2806 - bugfix: cleaning up in 'reload'Kartik K. Agaram2016-03-211-1/+1
| | | | | | | | | | | | | | | This brings back some of the complexity I thought I'd gotten rid of in 2799. The regression brought home the point that I'd forgotten to write tests for those bits. Written now. It also brought home the point that our cleanup in 'reload' has always been hacky and incomplete. It's also ugly that those tests in the sandbox/ and edit/ apps need changing (particularly when the test is about how the output doesn't change).
* 2805Kartik K. Agaram2016-03-211-4/+4
| | | | Fix test failures caused by 2804 in sandbox/ app.
* 2782 - directly use string literals everywhereKartik K. Agaram2016-03-144-20/+10
|
* 2781Kartik K. Agaram2016-03-141-3/+4
|
* 2735 - define recipes using 'def'Kartik K. Agaram2016-03-0811-182/+182
| | | | | | | | | | | | I'm dropping all mention of 'recipe' terminology from the Readme. That way I hope to avoid further bike-shedding discussions while I very slowly decide on the right terminology with my students. I could be smarter in my error messages and use 'recipe' when code uses it and 'function' otherwise. But what about other words like ingredient? It would all add complexity that I'm not yet sure is worthwhile. But I do want separate experiences for veteran programmers reading about Mu on github and for people learning programming using Mu.
* 2714 - apply 2604 to sandbox/Kartik K. Agaram2016-02-261-1/+1
|
* 2707Kartik K. Agaram2016-02-253-7/+0
|
* 2705 - eradicate 'warning' from appsKartik K. Agaram2016-02-251-52/+52
|
* 2661 - warn if a reply doesn't match recipe headerKartik K. Agaram2016-02-151-1/+2
| | | | | | | | Thanks Nicolas Léveillé for running up against this bug: https://news.ycombinator.com/item?id=11094837 (Also noticed and fixed several subsidiary issues. This whole aspect doesn't seem fully baked yet.)
* 2624Kartik K. Agaram2016-02-012-15/+23
| | | | Reorganize further to make edit/008-sandbox-test more self-contained.
* 2623 - bugfix: editing sandboxesKartik K. Agaram2016-02-013-6/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you restore 2 sandboxes, the first render was setting response-starting-row-on-screen on both, without ever rendering a response. If the lower sandbox contained a print and rendered the screen instead of the response, the original response-starting-row-on-screen was never reset. If the process of running the sandboxes caused the lower sandbox's title bar to move below the now-stale response-starting-row-on-screen[1], editing the lower sandbox no longer works. [1] (Either because the upper sandbox prints to screen as well (causing the first F4 to move the lower sandbox down by several lines), or because a fresh sandbox is created with several lines before the first F4 is hit.) Current solution: never set response-starting-row-on-screen during reload (or otherwise when there's no response). This is hard to test right now because 'restore' is not a tested interface, and I can't come up with another situation where the response-starting-row-on-screen goes stale. So I'm now trying to keep all changes to response-starting-row-on-screen close together. Another idea is to add a check that the click row lies below the response-starting row *and* above the start of the next sandbox. (But what if there's no next sandbox?) (This bug is really a regression, introduced last Sep in 2163.)
* 2622 - bugfix: left-arrowKartik K. Agaram2016-01-311-3/+78
| | | | Moving back to wrapped line was overflowing the right margin.
* 2612 - sandbox/ tests always show recipe errorsKartik K. Agaram2016-01-282-18/+39
| | | | | I spent the longest time trying to understand what bug 2268 fixed. But it's being tested now.
* 2610 - warn when recipes don't use default-spaceKartik K. Agaram2016-01-272-0/+4
| | | | Somehow this never transferred over from the Arc version until now.
* 2609 - reuse test-recipe variables in sandbox/ testsKartik K. Agaram2016-01-272-4/+5
| | | | | | | | I'd feared that the refcount errors in the previous commit meant there was a bug in my ref-counting, so I temporarily used new variables rather than reusing existing ones. But it turns out the one remaining place memory corruption can happen is when recipes don't use default-scope and so end up sharing memory. Don't I have a warning for this?
* 2608 - fix-up tests in sandbox/ appKartik K. Agaram2016-01-275-55/+674
| | | | | | | | | | When I first forked it from the edit/ app, I wasn't sure how to deal with changing the recipe side when the only way the program accesses it is with the untestable 'restore' hack. Now we introduce a little hook into event-loop and pass in any updated recipe side directly. In the process I've cleaned up several minor stylistic inconsistencies between edit/ and sandbox/ apps.