I found a bug today that planner does not correctly handle notes containing sub section headers, such as the following:
,---- | .#2 Some other Note | | ** Section 2 | | Test 2 | | .#1 Some Note | | ** Section 1 | | Test 1 `---- The problem is that the planner section processing looks for the next section of the next level or, not finding that, the end of file, and makes _everything_ from there on to the next section header part of the previous section, which will in this case include the marker for the next note, ".#1 Some Note." When publishing to HTML, this creates a closing </div> in the very wrong place. To me, this is blossoming into a very difficult bug to close, because it seems to require changing quite a bit of how planner-publish.el currently works. So, I'm asking if anyone has suggestions on how planner-publish.el should work? One simple solution is to simple end all sub-section processing in planner-publish. Does anyone use this? planner.el provides functions to narrow to section, inherently assuming any muse level-1 header is a use section, but it doesn't consider other headers at all. I prefer that way of thinking about it, but it's not documented, and I maybe we should have planner take control of all header processing. What do you think? Thanks, -- David D. Smith
pgp0BSHcx6RNc.pgp
Description: PGP signature
_______________________________________________ Planner-el-discuss mailing list [email protected] https://mail.gna.org/listinfo/planner-el-discuss
