about summary refs log tree commit diff stats
path: root/edit
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* 3111Stephen Malina2016-07-142-4/+10
| | | | | Show number of instructions in the editor when a user clicks on a run instruction in the sandbox.
* 3067Kartik K. Agaram2016-06-255-69/+69
|
* 3053 - keep cursor stable on resizeKartik K. Agaram2016-06-121-1/+85
| | | | | As much as possible; if the cursor moves off screen, it still resets to top of screen.
* 3052 - make edit/ render functions higher-orderKartik K. Agaram2016-06-127-44/+44
| | | | | | This required the fix of 3051 to first-class recipe support, and will next enable us to keep the cursor from moving in response to resize events.
* 3039 - bug fix in edit/Kartik K. Agaram2016-06-092-0/+43
| | | | Thanks Caleb Couch for finding this.
* 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
* 3025 - fix a minor annoyance in edit/Kartik K. Agaram2016-05-291-3/+157
| | | | | When I floor the down-arrow too much, don't scroll unnecessarily off the bottom of the screen. But *do* scroll if there's errors to show.
* 2990Kartik K. Agaram2016-05-201-17/+17
| | | | | | | | | | 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..
* 2983 - migrate buttons over to sandbox/Kartik K. Agaram2016-05-193-30/+3
|
* 2982Kartik K. Agaram2016-05-191-6/+6
|
* 2981 - sandbox buttons implemented in edit/Kartik K. Agaram2016-05-194-119/+373
|
* 2980Kartik K. Agaram2016-05-191-0/+3
|
* 2979Kartik K. Agaram2016-05-195-0/+0
|
* 2978 - support new 'edit' button in edit/Kartik K. Agaram2016-05-193-26/+101
|
* 2977 - draw new sandbox menu in edit/Kartik K. Agaram2016-05-197-376/+401
| | | | | | | | | | | | | Doesn't work as advertised yet. This is just the render piece, and fixing all the tests. I've been careful to try to break tests for edit once I implement the button. Delete I can't ensure will break afterwards. Remember to test clicking on multiple places on the menu. Managing the screens is starting to grow onerous; maybe we need something called normalize which clears some things. But the sandbox menu can be on arbitrary lines..
* 2976Kartik K. Agaram2016-05-191-4/+18
|
* 2975Kartik K. Agaram2016-05-194-10/+11
| | | | 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-113-59/+48
| | | | | | 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.
* 2890Kartik K. Agaram2016-05-021-1/+1
|
* 2864 - replace all address:shared with just addressKartik K. Agaram2016-04-2411-1333/+1333
| | | | | | | 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-123/+127
|
* 2853 - purge get-address from edit/ appKartik K. Agaram2016-04-2211-470/+563
| | | | Phew!
* 2852Kartik K. Agaram2016-04-211-1/+2
|
* 2851Kartik K. Agaram2016-04-211-109/+109
|
* 2830 - bring back deleted test from 2829Kartik K. Agaram2016-04-101-2/+0
| | | | Issue 1 in 2829 is now fixed.
* 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).
* 2782 - directly use string literals everywhereKartik K. Agaram2016-03-144-20/+10
|
* 2777 - pass literal strings into functionsKartik K. Agaram2016-03-131-9/+10
|
* 2735 - define recipes using 'def'Kartik K. Agaram2016-03-0811-170/+170
| | | | | | | | | | | | 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.
* 2716 - more holes in immutability checksKartik K. Agaram2016-02-262-4/+4
| | | | | We're still not done. Layer 60 doesn't yet handle variables in surrounding spaces. There's probably other issues..
* 2707Kartik K. Agaram2016-02-253-14/+0
|
* 2705 - eradicate 'warning' from appsKartik K. Agaram2016-02-251-49/+49
|
* 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-5/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* 2610 - warn when recipes don't use default-spaceKartik K. Agaram2016-01-272-9/+19
| | | | Somehow this never transferred over from the Arc version until now.
* 2608 - fix-up tests in sandbox/ appKartik K. Agaram2016-01-274-39/+16
| | | | | | | | | | 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.
* 2604 - clearing line was sometimes hiding cursorKartik K. Agaram2016-01-251-1/+1
| | | | Caused by 2591.
* 2602Kartik K. Agaram2016-01-241-1/+1
|
* 2598 - bugfix: scrolling after editKartik K. Agaram2016-01-231-0/+72
|
* 2595 - bugfix: update state when restoring sandboxesKartik K. Agaram2016-01-231-0/+3
|
* 2594 - bugfixes: managing state when deletingKartik K. Agaram2016-01-233-93/+306
| | | | This required completely redesigning scrolling.
* 2593 - bugfix: editing a sandbox resets scrollKartik K. Agaram2016-01-221-0/+54
|
* 2592 - bugfix: sandbox title bar managementKartik K. Agaram2016-01-221-1/+85
|
* 2591Kartik K. Agaram2016-01-221-1/+7
|
* 2590 - support scrolling through sandboxesKartik K. Agaram2016-01-227-13/+387
|