I use planner-multi which is absolutely awesome. I recently tried to exploit planner-extract-tasks to create pages that collect together actions from other pages. But ran into an interesting problem.
planner-extract-tasks does the majority of its work inside (with-temp-buffer) which confuses the call to (planner-page-name) inside planner-multi's defadvice for planner-task-info-from-string. In this context, (planner-page-name) returns " *temp*" which pollutes the task-info structure with incorrect information, making it hard to have those tasks link back to the pages from which it came. My gut says planner-extract-tasks needs to be redone to not use the temp-buffer approach and instead visit each page directly and leverage planner-narrow to visit the file. Unfortunately this will probably be slower as the current implementation dodges much of the rendering magic that makes planner so pretty. Is my analysis off base? -Eric _______________________________________________ Planner-el-discuss mailing list [email protected] https://mail.gna.org/listinfo/planner-el-discuss
