about summary refs log tree commit diff stats
path: root/edit/003-shortcuts.mu
Commit message (Collapse)AuthorAgeFilesLines
* 4134 - 'input' = 'ingredient'Kartik K. Agaram2017-12-031-23/+23
|
* 3980Kartik K. Agaram2017-08-221-42/+42
|
* 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.
* 3955Kartik K. Agaram2017-06-251-0/+32
| | | | | Move a scenario which is after commit 3954 applicable to both editors, not just the recipe side.
* 3954Kartik K. Agaram2017-06-251-47/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* 3925Kartik K. Agaram2017-06-191-0/+292
| | | | Bugfix: adjust row when hitting ctrl-u on wrapped lines.
* 3923Kartik K. Agaram2017-06-181-15/+91
| | | | | Bugfix: ctrl-a leaves things consistent in the presence of wrapped lines.
* 3922Kartik K. Agaram2017-06-171-4/+2
|
* 3919Kartik K. Agaram2017-06-161-4/+88
| | | | 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.
* 3911Kartik K. Agaram2017-06-151-19/+3
|
* 3903 - minimal render when pressing 'tab'Kartik K. Agaram2017-06-091-15/+39
| | | | Turns out all I had to do was reset `go-render?` to false.
* 3894 - comment/uncomment lines in edit appKartik K. Agaram2017-05-291-3/+111
|
* 3892Kartik K. Agaram2017-05-291-4/+4
| | | | Fix a keyboard shortcut conflict in commit 3884.
* 3891Kartik K. Agaram2017-05-291-10/+10
|
* 3885Kartik K. Agaram2017-05-281-0/+21
|
* 3884 - per-line scroll in edit/ appKartik K. Agaram2017-05-281-0/+61
|
* 3869Kartik K. Agaram2017-05-191-35/+98
| | | | Clean up a few superficial things in Caleb's commit.
* 3868 - make ctrl-k and ctrl-u fasterCaleb Couch2017-05-201-2/+131
|
* 3745Kartik K. Agaram2017-02-071-0/+3299
| | | | | | | Stop trying to create a new layer showing how we minimize prints. Stephen's suggestion is to create a data structure that encapsulates instructions to `insert-at-cursor` for either just printing a character to screen or rendering everything. Let's try that at some point.
* 3738 - start on new edit/ layer: minimizing printsKartik K. Agaram2017-02-041-3299/+0
|
* 3706Kartik K. Agaram2016-12-111-2/+2
|
* 3700Kartik K. Agaram2016-11-281-79/+49
| | | | | | Reorder products of some functions in the edit/ and sandbox/ apps. My recent realization: always return 'real' products before ones that just indicate an ingredient is mutable.
* 3699Kartik K. Agaram2016-11-281-1/+1
| | | | | Delete some obsolete /same-as-ingredient attributes. We should always let Mu deduce those at this point.
* 3696Kartik K. Agaram2016-11-271-71/+90
| | | | | | Decouple editor initialization from rendering to screen. This hugely simplifies the header of 'new-editor' and makes clear that it was only using the screen for rendering.
* 3552Kartik K. Agaram2016-10-221-1/+1
| | | | | | | | | | | | | | | | | | Stop requiring jump instructions to explicitly provide a ':label' type for jump targets. This has been a source of repeated confusion for my students: a) They'd add the ':label' to the label definition rather than the jump target (label use) b) They'd spend time thinking about whether the initial '+' prefix was part of the label name. In the process I cleaned up a couple of things: - the space of names is more cleanly partitioned into labels and non-labels (clarifying that '_' and '-' are non-label prefixes) - you can't use label names as regular variables anymore - you can infer the type of a label just from its name
* 3489Kartik K. Agaram2016-10-081-46/+46
| | | | | | | | | | 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-061-46/+46
| | | | | Switch around some unicode characters in the edit/ app so that it renders more cleanly in html (with monospace fonts).
* 3445Kartik K. Agaram2016-10-061-174/+174
| | | | | | | 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-281-343/+405
| | | | | | | | | | | | | 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.
* 3396Kartik K. Agaram2016-09-171-285/+285
|
* 3391 - type abbreviations everywhereKartik K. Agaram2016-09-171-503/+503
| | | | | | | | | 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.
* 3337 - first use of type abbreviations: textKartik K. Agaram2016-09-121-142/+142
| | | | | In the process I've uncover a couple of situations we don't support type abbreviations yet. They're next.
* 2864 - replace all address:shared with just addressKartik K. Agaram2016-04-241-418/+418
| | | | | | | 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-231-17/+17
|
* 2853 - purge get-address from edit/ appKartik K. Agaram2016-04-221-114/+147
| | | | Phew!
* 2735 - define recipes using 'def'Kartik K. Agaram2016-03-081-63/+63
| | | | | | | | | | | | 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.
* 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.)
* 2622 - bugfix: left-arrowKartik K. Agaram2016-01-311-3/+78
| | | | Moving back to wrapped line was overflowing the right margin.
* 2576 - distinguish allocated addresses from othersKartik K. Agaram2016-01-191-405/+405
| | | | | | | | | | | | | | | | This is the one major refinement on the C programming model I'm planning to introduce in mu. Instead of Rust's menagerie of pointer types and static checking, I want to introduce just one new type, and use it to perform ref-counting at runtime. So far all we're doing is updating new's interface. The actual ref-counting implementation is next. One implication: I might sometimes need duplicate implementations for a recipe with allocated vs vanilla addresses of the same type. So far it seems I can get away with just always passing in allocated addresses; the situations when you want to pass an unallocated address to a recipe should be few and far between.
* 2548 - teach 'print' to print integersKartik K. Agaram2015-12-281-2/+4
| | | | | | | | | | Still can't print non-integer numbers, so this is a bit hacky. The big consequence is that you can't print literal characters anymore because of our rules about how we pick which variant to statically dispatch to. You have to save to a character variable first. Maybe I can add an annotation to literals..
* layer 3 of edit/ now workingKartik K. Agaram2015-12-151-6/+8
| | | | | Now I complain before running if a call somewhere doesn't line up with its ingredients, or if no specialization can be made to match it.
* 2468 - overload print-character as just 'print'Kartik K. Agaram2015-11-211-4/+4
|