about summary refs log tree commit diff stats
path: root/edit
Commit message (Collapse)AuthorAgeFilesLines
* 2247 - type-check products of non-primitive recipesKartik K. Agaram2015-10-053-14/+14
| | | | | | | | We still can't check ingredient types, and even this is still a run-time check. We'll need to start tracking recipe signatures at some point. I've had to introduce a hack called /skiptypecheck. Time to get generics working.
* 2234 - check type of get's productKartik K. Agaram2015-10-021-9/+9
| | | | Already I'm finding type errors in the programming environment.
* 2227 - offset-checking for containersKartik K. Agaram2015-10-011-7/+23
|
* 2226 - standardize warning formatKartik K. Agaram2015-10-011-5/+5
| | | | | | | | Always show recipe name where error occurred. But don't show internal 'interactive' name for sandboxes, that's just confusing. What started out as warnings are now ossifying into errors that halt all execution. Is this how things went with C and Unix as well?
* 2218 - check types in instructions much earlierKartik K. Agaram2015-09-301-1/+1
| | | | | | | | | Front-loads it a bit more than I'd like, but the payoff is that other recipes will now be able to describe the type checks right next to their operation. I'm also introducing a new use of /raw with literals to indicate unsafe typecasts.
* 2216Kartik K. Agaram2015-09-292-1/+13
|
* 2206 - fix missing ingredientsKartik K. Agaram2015-09-261-2/+2
| | | | | How the heck was this working until now? There must be redundant moves. And was I clobbering test data?
* 2183 - environment + external editor using tmuxKartik K. Agaram2015-09-125-18/+10
| | | | Thanks Jack and Caleb Couch for the idea.
* 2182Kartik K. Agaram2015-09-122-3/+1
|
* 2180 - render the trace even if there's warningsKartik K. Agaram2015-09-102-1/+53
|
* 2179 - undo bugfixKartik K. Agaram2015-09-102-1/+22
|
* 2177Kartik K. Agaram2015-09-071-0/+0
|
* 2176Kartik K. Agaram2015-09-061-0/+32
|
* 2173 - 'main' for 'mu edit' running layers 1 and 2Kartik K. Agaram2015-09-061-1/+42
| | | | | | Layer 2 provides an almost fully functioning interactive editor: $ ./mu edit/00[12]* -- abcdef
* 2172 - 'main' for 'mu edit' running just layer 1Kartik K. Agaram2015-09-062-1/+14
| | | | | | | | | Takes the text to render inside the editor on the commandline: $ ./mu edit/001-editor.mu -- abcdef Layer 1 has no interactivity. Just shows the text you pass in on the commandline, wrapping as you would expect. Press any key to exit.
* 2167Kartik K. Agaram2015-09-052-4/+18
|
* 2166Kartik K. Agaram2015-09-053-168/+221
|
* 2164Kartik K. Agaram2015-09-051-2/+1
|
* 2163Kartik K. Agaram2015-09-053-17/+19
| | | | | | | | `render-string` (and `render-code-string`; ugh) should start a new line after, not before, like everybody else. I've been meaning to fix this for a long time, but now I have to, to move the warnings fields out of early layers.
* 2162Kartik K. Agaram2015-09-051-16/+2
|
* 2161Kartik K. Agaram2015-09-051-8/+8
| | | | | Starting on making the basic programming environment oblivious to warnings. That should come later.
* 2160Kartik K. Agaram2015-09-054-0/+0
|
* 2159Kartik K. Agaram2015-09-052-139/+139
|
* 2157 - edit/ now contains real layersKartik K. Agaram2015-09-054-48/+74
| | | | | | | | | To run just until say layer 6, say this: $ ./mu test edit/00[0-6]* The layers are not perfect yet; there might be a few things (like the warning fields) that need to move to a later layer.
* 2156 - split edit.mu into multiple filesKartik K. Agaram2015-09-0512-0/+8903
Now you can bring up the programming environment by saying: $ mu edit The files under edit aren't yet *layers*, though, they have a few dependencies that we need to clean up.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-02 02:52:24 +0000