I plan on continuing to write and support org-publish.el and its extensions. Because it was designed to be format-agnostic at both input and output stages (via plugin functions), I think it has a good chance of working with the XOXO stuff and other extensions people want to make. Furthermore, it currently publishes all my files, whether they're e-scripts, elisp code, or .org files.
>From what I understand, it is not a trivial matter to get Muse publishing other markup formats than the one it was designed around. It's something of an overhaul for the next major version, not a few tweaks. Since muse until recently lacked support for nested bullet lists (which always drove me nuts) I am not holding my breath waiting for Muse to fully support Org files, upload attachments, and format other types of files, the way org-publish does. :-) Whereas, I think org-publish.el is already a "unified" org-mode exporting system. I've never had such an easy time authoring an entire website as when using org.el and org-publish.el, and I can speak from several years experience with planner, emacswiki, and muse. Org-publish.el does not currently support things like LaTeX output, but I have volunteered to work on it. Scott Otterson <[EMAIL PROTECTED]> writes: > Also, a general question: There's been discussion of adapting > muse-mode so that org-mode can eventually make use of its many export > capabilities. At that same time, we've got very interesting xoxo > export capability and the nice new code written by David O'Toole. > This is great stuff but to a new user, these multiple and somewhat > overlapping choices are bound to be confusing. Will all this good > code eventually get merged into a unified org-mode exporting system? -- Dave O'Toole [EMAIL PROTECTED] _______________________________________________ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
