about summary refs log tree commit diff stats
path: root/sandbox/012-editor-undo.mu
Commit message (Collapse)AuthorAgeFilesLines
* 4134 - 'input' = 'ingredient'Kartik K. Agaram2017-12-031-1/+1
|
* 3980Kartik K. Agaram2017-08-221-14/+14
|
* 3879Kartik K. Agaram2017-05-261-3/+3
|
* 3700Kartik K. Agaram2016-11-281-2/+2
| | | | | | 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-3/+2
| | | | | Delete some obsolete /same-as-ingredient attributes. We should always let Mu deduce those at this point.
* 3698Kartik K. Agaram2016-11-271-24/+24
| | | | | | | | Update sandbox/ with recent changes to edit/ (commit 3695 onwards). [Incidentally, this is the first commit to be made while running on OpenBSD. Simulated and host systems are going to blur together from now on.]
* 3552Kartik K. Agaram2016-10-221-4/+4
| | | | | | | | | | | | | | | | | | 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-59/+59
| | | | | | | | | | 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-59/+59
| | | | | 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-107/+107
| | | | | | | 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-245/+258
| | | | | | | | | | | | | 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-223/+223
|
* 3391 - type abbreviations everywhereKartik K. Agaram2016-09-171-359/+359
| | | | | | | | | 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-48/+48
| | | | | In the process I've uncover a couple of situations we don't support type abbreviations yet. They're next.
* 2983 - migrate buttons over to sandbox/Kartik K. Agaram2016-05-191-0/+1895