From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: Org entries from tables Date: Wed, 03 Jul 2013 17:52:21 +0800 Message-ID: <87d2r0j7hm.fsf@ericabrahamsen.net> References: <87a9m459so.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53884) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UuJjY-0008Pw-De for emacs-orgmode@gnu.org; Wed, 03 Jul 2013 05:52:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UuJjW-0001FQ-9C for emacs-orgmode@gnu.org; Wed, 03 Jul 2013 05:52:20 -0400 Received: from plane.gmane.org ([80.91.229.3]:45322) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UuJjW-0001F3-2n for emacs-orgmode@gnu.org; Wed, 03 Jul 2013 05:52:18 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UuJjT-0001Mg-Kt for emacs-orgmode@gnu.org; Wed, 03 Jul 2013 11:52:15 +0200 Received: from 50.56.99.223 ([50.56.99.223]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 03 Jul 2013 11:52:15 +0200 Received: from eric by 50.56.99.223 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 03 Jul 2013 11:52:15 +0200 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: emacs-orgmode@gnu.org Bastien writes: > Hi Baptiste, > > Baptiste writes: > >> Is there a way back (or the other way), that is, create org entries with >> associated properties from a table. > > Not to my knowledge (and that of the Org FAQ, FWIW...) > > Sorry! If you were very, very adventurous, however, you could make a babel block that read rows from a table, marshaled the data into an org-element parse tree (maybe use `org-element-at-point' on an example heading to see what the parse tree should look like), and then use `org-element-interpret-data' to write the tree(s) as text in org syntax. Probably a lot of work...