Hi,

Michael Olson wrote:
> 
> Michael Welle <[EMAIL PROTECTED]> writes:
> 
> > Hi,
> >
> > Michael Welle wrote:
> >> 
> >> Hi,
> >> 
> >> after some investigation I discovered the following: The endless loop
> >> may be caused by planner-publish-markup-note in the planner-publish
> >> module. If I change the closing '</note>' in the inserted text block
> >> into a '</not>' for example all my planner pages are converted to
> >> html. Really strange. As a drawback the generated html isn't correct,
> >> because a sequence like <note> is transformed into
> >> &lt;note&gt; (which is correct for text, but <note> is an html
> >> entity). Perhaps someone with more knowledge in lisp and planner mode
> >> may enlighten me. 
> > no answer in several weeks. Could anyone reproduce the behaviour? Hm,
> > why is planner-publish-markup-note used to dump planner pages to
> > xhtml? Shouldn't that operation only be called by an xml dump?
> 
> I haven't been able to reproduce this -- I use Planner at work to
> publish day pages, and haven't seen the issue.
strange. I have started my XEmacs with the -vanilla switch and used
only the minimum (I hope) config to start planner-mode.


> Are you explicitly adding the <note> tag to a Plan page?  Can I see a
> sample Plan page?
Nop, no <note> tag. I use this to create an empty notes section in my
planner pages:
(setq planner-day-page-template "* Tasks\n\n\n* Diary\n\n\n* Notes\n")

To populate the section I use remember mode. I have appended an
example page. It is my first planner page with a note and it triggers
the behaviour. 

Michael

PS: I see "timestamp delimiter not found" messages in the mode line
    when generating xhtml pages. Perhaps they are related to the
    problem? 


Attachment: 2006.01.17.muse
Description: Binary data

biff4emacsen - A biff-like tool for (X)Emacs
http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html



_______________________________________________
Planner-el-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/planner-el-discuss

Reply via email to