From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Day Subject: Re: org reserved and special words in drawers Date: Sat, 29 Dec 2012 10:53:35 +1100 Message-ID: References: <1352210038.36570.YahooMailNeo@web29801.mail.ird.yahoo.com> <87625i8yoa.fsf@gmail.com> <1352221405.73627.YahooMailNeo@web29802.mail.ird.yahoo.com> <87pq3q7iny.fsf@gmail.com> <5750CCC1-3900-4FDC-8525-A51B7D85958C@gmail.com> <87a9t4te28.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:42035) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TojkH-0003o2-Oi for emacs-orgmode@gnu.org; Fri, 28 Dec 2012 18:53:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TojkG-0002ei-Ju for emacs-orgmode@gnu.org; Fri, 28 Dec 2012 18:53:45 -0500 Received: from mail-pb0-f51.google.com ([209.85.160.51]:58162) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TojkG-0002eX-Dw for emacs-orgmode@gnu.org; Fri, 28 Dec 2012 18:53:44 -0500 Received: by mail-pb0-f51.google.com with SMTP id ro12so6139957pbb.24 for ; Fri, 28 Dec 2012 15:53:43 -0800 (PST) In-Reply-To: <87a9t4te28.fsf@bzg.ath.cx> (Bastien's message of "Mon, 24 Dec 2012 02:49:03 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: Org-mode > Bastien writes: >> In other words, we could then /apply/ org-mode >> on a document rather than transforming a document into an org >> document. > What we may think about is a "Org readable exchange format (oref?)", > which would take the output of Nicolas' parser, export it in Org-mode > using some specific properties like "TAGS:" "TODO:" etc. 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? > > > 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? 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?