Fix bug with <contents> and multiple <include> tags
commit94f5007433e4f31c4f7d99042376cfeab0173be9
authorMichael Olson <mwolson@gnu.org>
Tue, 5 Jun 2007 01:00:12 +0000 (5 01:00 +0000)
committerMichael Olson <mwolson@gnu.org>
Tue, 5 Jun 2007 01:00:12 +0000 (5 01:00 +0000)
treec6d13c19e99bda2ad6b6a9ed4e83e5bd49292ad3
parent0ed0c40d87fdec45e71222aaf84161fc6cf18cc3
Fix bug with <contents> and multiple <include> tags

2007-06-04  Michael Olson  <mwolson@gnu.org>

* lisp/muse-html.el (muse-html-insert-contents): Add
documentation.  Handle case where heading is read-only, but has
muse-contents property.  Remove the muse-contents property for any
heading we come across so as to avoid double-including an item in
an outer table of contents.
(muse-html-denote-headings): New function that denotes whether a
heading is not read-only by adding the muse-contents property to
it.
(muse-html-munge-buffer): If we are not to generate contents,
still denote headings, in case some outer layer wants to generate
contents for our headings.  This should fix a bug with table of
contents and the <include> tag.  Thanks to thorne for the report.

* lisp/muse-publish.el (muse-publish-markup-region): Let-bind
muse-publish-generate-contents and set it to nil.  This should
do the right thing when using <include> tags.
git-archimport-id: mwolson@gnu.org--2006/muse--main--1.0--patch-334
ChangeLog
lisp/muse-html.el
lisp/muse-publish.el