Cool deal, thanks. Something else I just discovered:

The first level 1 heading in a document replaces its title. So if you were using the <title>Augmented page title</title> feature of embedded docs, just do:

# Augmented page title

I don't know if that's just the first level 1 heading or the first heading of any kind, but thought I'd document it here for anyone wanting to use this feature. Must be the first item in the document.


On 12/09/2012 08:36 PM, Joe Mistachkin wrote:
Nolan Darilek wrote:
This isn't entirely helpful. When exactly is a document of type
text/x-markdown? When it has a .md extension? .markdown? .mdwn? Is there
some other setting that controls this?

The markdown extensions are "mkd" and "markdown".

It might be more helpful to change this verbiage to the exact steps
necessary to enable Markdown processing, rather than this vague
statement about content-types. Or, at least, add something stating when
a document is determined to have this content-type.

The exact steps are to enable the setting, checkin a markdown document (with
an "mkd" or "markdown" extension), and then view the checked in document
using the appropriate embedded documenation URL, e.g.:

        http://example.com/doc/trunk/www/index.markdown

Alternatively, the document can be viewed prior to being checked in by using
the special "ckout" name in the URL (i.e. after using "fossil ui"), e.g.:

        http://127.0.0.1:8080/doc/ckout/www/index.markdown

Also, there are a bunch of variants in MD syntax. Is there a link to
what is supported in the embedded engine? Is it just vanilla, or any
extensions for tables/TOCs/etc.?

I'm not sure about this.  Perhaps Natacha can shed some light on it?

--
Joe Mistachkin

_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to