| 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.
|
| | |
|
| |
|
|
|
| |
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.)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Improvements to syntax highlighting, particularly for Mu code in C++
files.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|