about summary refs log tree commit diff stats
path: root/edit
Commit message (Collapse)AuthorAgeFilesLines
* 4266 - space for alloc-id in heap allocationsKartik Agaram2018-06-241-10/+12
| | | | This has taken me almost 6 weeks :(
* 4262 - literal 'null'Kartik Agaram2018-06-1710-38/+38
|
* 4261 - start using literals for 'true' and 'false'Kartik Agaram2018-06-179-94/+107
| | | | | | | | | They uncovered one bug: in edit/003-shortcuts.mu <scroll-down> was returning 0 for an address in one place where I thought it was returning 0 for a boolean. Now we've eliminated this bad interaction between tangling and punning literals.
* 4258 - undo 4257Kartik Agaram2018-06-153-39/+10
|
* 4257 - abortive attempt at safe fat pointersKartik Agaram2018-06-153-10/+39
| | | | | | | | | | | | | | | | I've been working on this slowly over several weeks, but it's too hard to support 0 as the null value for addresses. I constantly have to add exceptions for scalar value corresponding to an address type (now occupying 2 locations). The final straw is the test for 'reload': x:num <- reload text 'reload' returns an address. But there's no way to know that for arbitrary instructions. New plan: let's put this off for a bit and first create support for literals. Then use 'null' instead of '0' for addresses everywhere. Then it'll be easy to just change what 'null' means.
* 4208Kartik K. Agaram2018-02-171-6/+42
| | | | | | edit/ app: Fix a bug introduced in commit 3954 (June 2017) Turns out commit 4206 wasn't really necessary to fix this, after all.
* 4207Kartik K. Agaram2018-02-151-1/+0
|
* 4206 - edit/ app: consistent cursor positioningKartik K. Agaram2018-02-154-9/+3
|
* 4205Kartik K. Agaram2018-02-151-45/+45
|
* 4169Kartik K. Agaram2017-12-301-7/+5
|
* 4134 - 'input' = 'ingredient'Kartik K. Agaram2017-12-0312-92/+92
|
* 3984 - bugfix: display errors when scrolling recipe sideKartik K. Agaram2017-08-251-0/+38
| | | | This regression was (also) introduced by commit 3902 in June.
* 3982 - bugfix: clear old recipe errors on F4Kartik K. Agaram2017-08-222-0/+60
| | | | | | This regression was introduced by commit 3902 in June. Making this commit clean took the last 4 commits of reorganizing.
* 3981Kartik K. Agaram2017-08-222-7/+4
| | | | | It's always been ugly that I referred to a later layer/feature in a label name.
* 3980Kartik K. Agaram2017-08-226-68/+68
|
* 3979Kartik K. Agaram2017-08-221-4/+4
|
* 3978Kartik K. Agaram2017-08-221-13/+18
|
* 3977Kartik K. Agaram2017-08-221-1/+1
|
* 3962Kartik K. Agaram2017-06-271-6/+13
| | | | | Yet another regression, this time cascading from commit 3953. My scenario wasn't actually testing what I thought it was testing.
* 3960Kartik K. Agaram2017-06-251-14/+38
| | | | | Don't refresh entire sandbox side when toggling the expected result for a single sandbox.
* 3959Kartik K. Agaram2017-06-251-2/+13
| | | | | | | Don't unnecessarily write sandboxes to disk on F4. This seems to save almost 20% time when processing a large lesson directory with 36 sandboxes.
* 3958Kartik K. Agaram2017-06-252-13/+19
| | | | | | | | Improvement on fix 3957: rather than put a band-aid over a slow operation, eliminate the slowdown entirely. In this case it turns out we're unnecessarily saving files to disk when they could never be modified. Are we doing this on F4 as well?!
* 3957Kartik K. Agaram2017-06-251-0/+2
| | | | | Marking sandbox responses as expected can take a long time if there are many sandboxes. Indicate when a click is being worked on.
* 3955Kartik K. Agaram2017-06-252-36/+32
| | | | | Move a scenario which is after commit 3954 applicable to both editors, not just the recipe side.
* 3954Kartik K. Agaram2017-06-253-110/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | As a blanket rule, down-arrow now stops scrolling once the bottom margin comes on screen. Now that we have page-wise scrolling with ctrl-f/b and line-wise scrolling with ctrl-s/x, we don't need to conflate scroll positioning with the arrow keys. And as a result, early students no longer have to struggle with accidentally scrolling part of the sandbox off the screen when there's tons of empty space available. `move-to-next-line` is still super messy and will need further rethinking, but this commit simplifies the codebase as a whole by eliminating a couple of historical accidents: a) We only introduced scrolling past the bottom of the screen to allow more sandboxes to come into view before we had scrolling for the sandbox side. b) We undid scrolling past the bottom in just the recipe side to allow errors to come into view. Since these historical details are now irrelevant, we no longer need separate logic for the recipe and sandbox sides, and we don't need to keep track of the recipe-bottom separate from the bottom margin of arbitrary editors.
* 3953Kartik K. Agaram2017-06-241-24/+51
| | | | | | | | | Redo cursor-down to fix a bug. This should be the final bug I find as part of my audit of everywhere we compare characters to newlines in layer 3 of the edit/ app. Pretty messy implementation, but we'll clean it up now.
* 3952Kartik K. Agaram2017-06-241-11/+10
|
* 3950Kartik K. Agaram2017-06-241-2/+43
| | | | | | Fix a regression caused by commit 3919. Thanks Juan Crispin Hernandez for running into this.
* 3946Kartik K. Agaram2017-06-231-3/+3
| | | | Fix the failing scenario of commit 3944.
* 3944Kartik K. Agaram2017-06-231-1/+25
| | | | | | | Reintroduce the failing test of commit 3938. It has two problems: a) it's failing, and b) it's not failing the same way as with a real screen.
* 3943Kartik K. Agaram2017-06-234-45/+0
| | | | Undo commit 3938 and almost everything after. Let's do this right.
* 3942Kartik K. Agaram2017-06-234-18/+18
| | | | | | | | No, my conclusion in the previous commit was wrong. When you print a character on the right margin, the cursor coordinates always wrap around to the left margin on the next row. It's just that if you're at the bottom of the screen, scrolling gives the impression that the row didn't change.
* 3941Kartik K. Agaram2017-06-234-13/+29
| | | | | | | | | | | | | | | | | Even though the bug of commit 3938 is now fixed, I'm still trying to track down why the failure looked different on the fake screen than on the real one. Snapshot as I try to track down the difference. One key lesson is that the approach of commit 3860 -- updating the cursor before rather than after printing each character -- turns out to be untenable. A sequence of `print` followed by `cursor-position` needs to behave the same as the real screen. But it's still not clear how the real screen. When you get to the end of a line the cursor position wraps after print to the left margin (column 0) on the next row. When you get to the bottom right the cursor position wraps to the *bottom left* margin. How the heck does it know to scroll on the next print, then? Is there some hidden state in the terminal?
* 3940Kartik K. Agaram2017-06-221-1/+1
|
* 3939Kartik K. Agaram2017-06-222-3/+9
|
* 3938Kartik K. Agaram2017-06-221-2/+32
| | | | | | | Fix an out-of-bounds write to the screen when sandboxes aligned just right. Thanks Ella Couch for reporting this issue.
* 3935Kartik K. Agaram2017-06-223-3/+3
|
* 3928Kartik K. Agaram2017-06-191-4/+5
|
* 3926Kartik K. Agaram2017-06-191-2/+57
| | | | | | Bugfix: when you hit `enter`, the cursor-row does not increment in *one* special situation: when the line wraps and the cursor is right at the start of one of the wrapped lines.
* 3925Kartik K. Agaram2017-06-191-0/+292
| | | | Bugfix: adjust row when hitting ctrl-u on wrapped lines.
* 3924Kartik K. Agaram2017-06-181-1/+1
|
* 3923Kartik K. Agaram2017-06-181-15/+91
| | | | | Bugfix: ctrl-a leaves things consistent in the presence of wrapped lines.
* 3922Kartik K. Agaram2017-06-172-7/+4
|
* 3921Kartik K. Agaram2017-06-162-4/+6
|
* 3919Kartik K. Agaram2017-06-162-5/+89
| | | | Bugfix: up-arrow in combination with wrapped lines.
* 3918Kartik K. Agaram2017-06-161-3/+47
| | | | Bugfix: handle wrapped lines when moving to end of line.
* 3916 - minimal prints when commenting linesKartik K. Agaram2017-06-161-11/+139
|
* 3915Kartik K. Agaram2017-06-161-4/+2
|
* 3914Kartik K. Agaram2017-06-161-8/+8
| | | | Remember that `before-previous-line` deals with wrapped screen lines.
* 3913Kartik K. Agaram2017-06-151-2/+45
| | | | Bugfix in ctrl-u.