Mike Gerwitz
8ce8b5a7f7
The article I'm working on makes (very) heavy use of the `details` HTML element, and nests them. Making sense of the article without indentation is difficult and torturous. This has complicated the prefmt script enough that it really ought to be extracted into something else. I'm admittedly disappointed that I've had to do this much work with it, because it completely sacrifies any hope of portability. Oh well, that's not even a design goal, though it'd be nice to be able to have the preview of Markdown files make sense in e.g. Forejo. I figured I'd have the least numbre of problems with nesting if I strip whitespace prefixes based on the current level of nesting. To avoid surprises, I enforce expectations statically---it will not compile without proper nesting. To reduce the potential blast radius, I'm doing this only for `details` for now; it'll expand later on. I did diff the output of older articles to make sure they were unaffected. |
||
|---|---|---|
| _raw/about | ||
| build-aux | ||
| conf | ||
| docs/gh | ||
| fonts | ||
| images | ||
| papers | ||
| post | ||
| src | ||
| submodule | ||
| tools | ||
| .gitignore | ||
| .gitmodules | ||
| .mailmap | ||
| COPYING | ||
| COPYING.CCBYSA | ||
| COPYING.GPLv3 | ||
| Makefile | ||
| README | ||
| THANKS | ||
| bootstrap | ||
| style.css | ||
README
The miscellaneous thoughts and ramblings of a free software hacker. https://mikegerwitz.com/