emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Rustom Mody" <rustompmody@gmail.com>
To: emacs-orgmode@gnu.org
Subject: HOWTO export document to wiki text?
Date: Mon, 19 Jan 2009 12:35:25 +0530	[thread overview]
Message-ID: <f46c52560901182305g4c834a3bxf86fd9434c3b72fe@mail.gmail.com> (raw)

Uwe Koloska <uwe <at> koloro.de> writes:

> there is this very nice export to text feature and the superb HTML export.
> And if there is no such feature yet, where do I have to start to implement it?

+1 for me.

I need at least two more exporters, maybe more -- they may be of
different level of generality/use to other org users.
If I can get a handle on it I'll try my hand.

As I understand (and Eric points out) org-exp.el is the central place
to start looking, but I gather that there is also another more
data-oriented approach experimentally supported by some Bastien code.
I remember Carsten talking about it some 2-3 months back that
something like this (entire org mode buffer as a lisp (property) list
or something to that effect) but that its not (yet then) integrated
into the rest of org.

So tips/pointers on this will be welcome.


             reply	other threads:[~2009-01-19  7:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19  7:05 Rustom Mody [this message]
2009-01-19 15:32 ` HOWTO export document to wiki text? Carsten Dominik
     [not found] <E1LOku5-0004vu-DT@box188.bluehost.com>
2009-01-19 15:40 ` Robert Goldman
  -- strict thread matches above, loose matches on Subject: below --
2009-01-17 21:03 Uwe Koloska
2009-01-18 18:26 ` Matthew Lundin
2009-01-19  7:42   ` Ian Barton
2009-01-19 15:03     ` Matthew Lundin
2009-01-19 15:27       ` Sebastian Rose
2009-01-19 19:30       ` Ian Barton
2009-01-18 18:27 ` Eric Schulte
2009-01-19 16:23 ` Christian Egli

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:

  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=f46c52560901182305g4c834a3bxf86fd9434c3b72fe@mail.gmail.com \
    --to=rustompmody@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).