| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
More improvements to cross-linking example programs. Include their own
functions as well in the tags for each program, even as you share the
core .mu files everywhere.
|
| | |
|
| |
|
|
| |
Make hyperlinks less salient in the rendered html since there's so many of them.
|
| |
|
|
|
|
|
|
| |
Fix cross-links in html for the edit/ app.
I originally thought I'd need to provide a commandline flag like --rel-path or
something. But we need to support different relative paths in a single html
file. So the solution instead is appropriately engineering the tags file.
|
| | |
|
| |
|
|
|
| |
Turns out we don't need to explicitly add anchors for each line. Vim's TOhtml
has magic for that out of the box.
|
| |
|
|
|
|
| |
Each line number also gets an anchor name, but I'm not hyperlinking them for now
because I don't want to encourage bookmarking these links just yet. They aren't
permalinks because every revision may change what's at any given line number.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Be more disciplined about tagging 2 different concepts in the codebase:
a) Use the phrase "later layers" to highlight places where a layer
doesn't have the simplest possible self-contained implementation.
b) Use the word "hook" to point out functions that exist purely to
provide waypoints for extension by future layers.
Since both these only make sense in the pre-tangled representation of
the codebase, using '//:' and '#:' comments to get them stripped out of
tangled output.
(Though '#:' comments still make it to tangled output at the moment.
Let's see if we use it enough to be worth supporting. Scenarios are
pretty unreadable in tangled output anyway.)
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Bugfix: writing to a new file in a non-empty fake file system.
The one time I try to get a little clever, it bites me in the ass.
That'll teach me..
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Delete some obsolete /same-as-ingredient attributes. We should always
let Mu deduce those at this point.
|
| |
|
|
|
|
| |
Decouple programming environment initialization from rendering. This
helps make clear that we only need the width from screen during
initialization.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Fix CI, broken by commit 3691.
|
| | |
|
| |
|
|
|
|
| |
If we're automatically passing ingredients to 'append' through 'to-text'
if its first ingredient is text, we don't need to pass that first
ingredient itself through 'to-text'.
|
| |
|
|
| |
Expand 'assert' to handle non-literal texts.
|
| |
|
|
|
| |
Attempting to write to a file in a non-existent directory silently
writes to a black hole in Unix. Make that explicit.
|
| | |
|
| |
|
|
|
|
|
| |
Move my todos over the past couple of years into the codebase now that
it might be going dormant.
Surprising how few todos left undone!
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Trying to find examples where a layer includes complexity just so later
layers can hook into it. Resolve_stack is the one big one I've found
that isn't just a simple function-call indirection that may later get
more complex.
Conclusion of a conversation with Stephen Malina: Such examples should
make one very nervous, because this sort of creep is how we end up with
over-engineered abstractions (http://www.joelonsoftware.com/articles/fog0000000018.html).
We need to step very carefully anytime we make the outsider reader's
comprehension task harder..
|
| | |
|
| |
|
|
|
| |
Clean up the flow of "mu --trace" followed by "mu browse-trace
interactive".
|
| |
|
|
| |
Couple of fixes to example programs.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Thanks Jack Couch for accidentally leading me to this bug.
|
| |
|
|
| |
Follow-up to commit 3516.
|
| | |
|
| |
|
|
| |
Umpteenth bugfix to ensure we show the number of failed scenarios.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|