Quoting Michael Olson <[EMAIL PROTECTED]>: > What would be the advantage of using this over > `muse-after-project-publish-hook'? Muse currently has both that and > also `muse-after-publish-hook', which activates after the publishing of > each file. The good think about muse-after-project-publish-hook is that > the hook functions know which project is being published.
So how would I go about to run a custom function by one of the muse hooks *only* when publishing a planner project (in fact, any planner project, in case I have more than one), not when publishing some other unrelated muse project? My understanding of muse publishing is admittedly somewhat limited, but if this is doable, then there is no need for a planner publishing hook. >> + (muse-project-publish nil) > > Better would be: > > (call-interactively 'muse-project-publish) True indeed. My bad. best regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de _______________________________________________ Planner-el-discuss mailing list [email protected] https://mail.gna.org/listinfo/planner-el-discuss
