Michael Olson <[EMAIL PROTECTED]> writes: > I've now implemented <include> and <markup> tags in Muse. The > documentation for both is included below. > > <include>: Include the named file at the current location during > publishing. > > <include file=\"...\">
Should be: <include file="..."> > Files are marked up according to the Muse publishing rules. If > you want no markup to be performed, either add > <example>..</example> inside the source file or use the > following invocation. > > <include file=\"...\" markup=\"nil\"> <include file="..." markup="nil"> > The `markup' attribute controls how this section is marked up. If > non-nil, it should be the name of a function to call after > inserting the file with the buffer narrowed to the section > inserted. Note that no further marking-up will be performed on > this region. > > <markup>: Run an Emacs Lisp function on the region delimted by this > tag. > > <markup function=\"...\"> <markup function="..."> -- Michael Olson -- FSF Associate Member #652 -- http://www.mwolson.org/ Interests: Emacs Lisp, text markup, protocols -- Jabber: mwolson_at_hcoop.net /` |\ | | | IRC: mwolson on freenode.net: #hcoop, #muse, #PurdueLUG |_] | \| |_| Project involvement: Emacs, Muse, Planner, ERC, EMMS
pgpH4v4L702Fv.pgp
Description: PGP signature
_______________________________________________ emacs-wiki-discuss mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/emacs-wiki-discuss
