"Markus Hoenicka" <[EMAIL PROTECTED]> writes: > in order to allow custom processes to be run whenever a planner > project is published, I'd like planner to run a hook right after > publishing. The following patch does the following:
I took a quick look at this.
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.
Did you have a particular scenario in mind?
> +(defun planner-publish-project ()
> + "Publish the project and run a planner-publishing specific hook."
> + (interactive)
> + (muse-project-publish nil)
Better would be:
(call-interactively 'muse-project-publish)
--
Michael Olson -- FSF Associate Member #652 |
http://mwolson.org/ -- Jabber: mwolson_at_hcoop.net | /` |\ | | |
Programmer -- Hobbies: Lisp, HCoop | |_] | \| |_|
Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner |
pgptHLblUfqzn.pgp
Description: PGP signature
_______________________________________________ Planner-el-discuss mailing list [email protected] https://mail.gna.org/listinfo/planner-el-discuss
