From: David O'Toole <dto@gnu.org>
To: Scott Otterson <scotto@u.washington.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: fancier and less fancy export
Date: Mon, 08 May 2006 15:33:37 -0400 [thread overview]
Message-ID: <m3irog71m6.fsf@gnu.org> (raw)
In-Reply-To: <445F752C.20909@u.washington.edu> (Scott Otterson's message of "Mon, 08 May 2006 09:43:24 -0700")
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 <scotto@u.washington.edu> 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
dto@gnu.org
next prev parent reply other threads:[~2006-05-08 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 16:43 fancier and less fancy export Scott Otterson
2006-05-08 17:07 ` Nic
2006-05-08 19:33 ` David O'Toole [this message]
2006-05-08 21:00 ` Carsten Dominik
2006-05-08 21:13 ` Nic
2006-05-12 7:57 ` Carsten Dominik
2006-05-12 17:08 ` Scott Otterson
2006-05-12 22:03 ` Carsten Dominik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3irog71m6.fsf@gnu.org \
--to=dto@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=scotto@u.washington.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).