On May 11, 2018, at 7:21 PM, Will Parsons <varro@nodomain.invalid> wrote: > > How could I come across this solution on my own?
Most of what it does is described here, which is well worth a read if you haven’t done so already: https://fossil-scm.org/index.html/doc/trunk/www/embeddeddoc.wiki And if you have read it, it’s probably worth a re-read. :) Fossil’s embedded documentation feature has some subtleties that typically take several passes to discover, such as the ckout feature. This mimetype= query parameter override should be documented on that page, too, but currently is not. > does it have something to do with the > implementation of Fossil itself? Yes. Much of what you know about web technologies does not apply directly to Fossil because it isn’t reusing some existing web server; blog articles and such focused on Apache and nginx often won’t apply to Fossil. Aside from this mailing list and the docs, I’ve found the Fossil source code helpful many times. It’s reasonably straightforward code. I’m pretty sure my knowledge of the way Fossil handles filename extension mappings to MIME types comes from reading the code, not from reading the docs, for example. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
