| Comment: | web: repository nav shows counts and current section
Counts tell a reader where a store's content is — pikchr is 245 forum threads and one ticket, tk is 5,809 tickets and one post. The index memoizes them per fold; on tk they cost ~110ms cold and 3ms after. Also: the current section is marked, empty sections are dimmed but stay linked, the repository outranks the forge name in the header, and timestamps render relative with the exact value in the title. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
3a330c95600c8a6777af4582fd0e01d7 |
| User & Date: | dmestas on 2026-08-17 18:49:56.540 |
| Other Links: | manifest | tags |
|
2026-08-17
| ||
| 18:57 |
api: pick README markup by extension, not by assumption
A bare README was rendered as markdown 'by convention'. libspatialite's is an autotools plain-text file whose commands carry the root prompt #, so markdown read '# sudo make install' as a heading and turned the build instructions into a dozen h2s. Extension decides now, and anything unrecognized falls through to escaped with its line breaks intact — fossil's rule in wiki_render_by_mimetype. Also recognizes README.wiki.check-in: 1499d5aa5a user: dmestas tags: trunk | |
| 18:49 |
web: repository nav shows counts and current section
Counts tell a reader where a store's content is — pikchr is 245 forum threads and one ticket, tk is 5,809 tickets and one post. The index memoizes them per fold; on tk they cost ~110ms cold and 3ms after. Also: the current section is marked, empty sections are dimmed but stay linked, the repository outranks the forge name in the header, and timestamps render relative with the exact value in the title. check-in: 3a330c9560 user: dmestas tags: trunk | |
| 18:03 | docs: fleet admin and mirroring in running.md check-in: e79c732ee4 user: dmestas tags: trunk | |