| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 2095 | Kartik K. Agaram | 2015-08-28 | 1 | -4/+0 |
| | | | | | | | | | | | | | Finally terminate the experiment of keeping debug prints around. I'm also going to give up on maintaining counts. What we really need is two kinds of tracing: a) For tests, just the domain-specific facts, organized by labels. b) For debugging, just transient dumps to stdout. b) only works if stdout is clean by default. Hmm, I think this means 'stash' should be the transient kind of trace. | ||||
| * | 1945 | Kartik K. Agaram | 2015-08-06 | 1 | -19/+68 |
| | | | | | | | Turns out it is indeed useful to insert code at multiple duplicate labels within a single (long) recipe. Like handle-keyboard-event in edit.mu. | ||||
| * | 1939 - allow nested tangling | Kartik K. Agaram | 2015-08-05 | 1 | -30/+49 |
| | | | | | However, you can't have duplicate labels within a single recipe. | ||||
| * | 1938 - warn on unused before/after fragments | Kartik K. Agaram | 2015-08-05 | 1 | -0/+27 |
| | | |||||
| * | 1870 | Kartik K. Agaram | 2015-07-28 | 1 | -0/+198 |