From: Bastien <bzg@altern.org>
To: Tony Day <tonyday567@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: org reserved and special words in drawers
Date: Sat, 29 Dec 2012 21:00:12 +0100 [thread overview]
Message-ID: <87sj6ofx2r.fsf@bzg.ath.cx> (raw)
In-Reply-To: <m21ue9lon4.fsf@gmail.com> (Tony Day's message of "Sat, 29 Dec 2012 10:53:35 +1100")
Hi Tony,
Tony Day <tonyday567@gmail.com> writes:
> I'm trying to get my head around what a 'readable exchange format' is.
>
> org-export.el already exports as an elisp list:
>
> M-: (setq my-org-buffer-as-elisp (org-element-parse-buffer)) RTE
>
> ... and it's pretty readable :-)
>
> So the basic idea is that you would export from an org file to an org
> file but one with a /different/ and maybe standardized format (highly
> standardized is the oref gist?).
>
> For example, anything that
> is content passes through as text and everything else (org guff) is put
> into a :PROPERTIES: :END: wrapper?
Yes, why not.
If people need an exchange format that is based on .org files but
slightly different, org-export.el can certainly help.
>> Maybe you can start working on a org-e-oref exporter, storying *all*
>> metadata into properties? ... Don't know where it will lead, but who
>> knows?
>
> A mission truly beyond my abilities, but how could I say no to such a
> meta org-mode process :-)
>
> Is the right place to start basically turning (org-element-parse-buffer)
> output back into an org buffer?
I'd say so, but Nicolas might help more here.
> Is this best thought of as another backend? I
> can't quite see why org-e-oref.el and not just org-e-org.el?
I would first ask myself "what is the new org format for?
Is it worth implementing this?"
Best,
--
Bastien
next prev parent reply other threads:[~2012-12-29 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 13:53 BUG ? [new HTML exporter] subtree: newline and slash Giovanni Ridolfi
2012-11-06 16:48 ` Nicolas Goaziou
2012-11-06 17:03 ` Giovanni Ridolfi
2012-11-06 17:20 ` Nicolas Goaziou
2012-11-07 3:33 ` org reserved and special words in drawers tony day
2012-12-24 1:49 ` Bastien
2012-12-28 23:53 ` Tony Day
2012-12-29 20:00 ` Bastien [this message]
2012-12-31 0:19 ` Tony Day
2012-11-07 12:15 ` solved (Re: BUG ? [new HTML exporter] subtree: newline and slash) Giovanni Ridolfi
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=87sj6ofx2r.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=tonyday567@gmail.com \
/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).