From: Nic <nferrier@tapsellferrier.co.uk>
To: Scott Otterson <scotto@u.washington.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: fancier and less fancy export
Date: Mon, 08 May 2006 18:07:02 +0100 [thread overview]
Message-ID: <873bfkjvih.fsf@nicferrier.tapsellferrier.co.uk> (raw)
In-Reply-To: <445F752C.20909@u.washington.edu> (Scott Otterson's message of "Mon, 08 May 2006 09:43:24 -0700")
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?
I think the problem is we're all just trying out org-mode and working
out what we think it's good for and stretching it in new ways.
To some people it seems it's a plain organizational outliner.
To other people it seems it's a document construction outliner.
To many people it looks like it might be a blogging tool.
All these different things need different export.
Having said that, if I have time to clean up the XOXO output I think
that might consolidate some things because it will be simple clean
HTML which people can parse and transform in other ways.
Nic Ferrier
next prev parent reply other threads:[~2006-05-08 17:14 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 [this message]
2006-05-08 19:33 ` David O'Toole
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=873bfkjvih.fsf@nicferrier.tapsellferrier.co.uk \
--to=nferrier@tapsellferrier.co.uk \
--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).