From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: Re: #+ATTR_MY-ASCII: in derived backend? Date: Sun, 22 Sep 2013 15:01:06 +0200 Message-ID: <87vc1tau3x.fsf@gmail.com> References: <87fvsxcjmo.fsf@gmail.com> <87pps1119u.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57842) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VNjI2-0007he-ME for emacs-orgmode@gnu.org; Sun, 22 Sep 2013 09:01:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VNjHs-0003b7-Q7 for emacs-orgmode@gnu.org; Sun, 22 Sep 2013 09:01:30 -0400 Received: from plane.gmane.org ([80.91.229.3]:54831) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VNjHs-0003b1-Jh for emacs-orgmode@gnu.org; Sun, 22 Sep 2013 09:01:20 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VNjHq-0002lF-Om for emacs-orgmode@gnu.org; Sun, 22 Sep 2013 15:01:18 +0200 Received: from e178054182.adsl.alicedsl.de ([85.178.54.182]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Sep 2013 15:01:18 +0200 Received: from tjolitz by e178054182.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Sep 2013 15:01:18 +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 Nicolas Goaziou writes: Hello, > Thorsten Jolitz writes: > >> do derived backends set their attributes always via the >> >> ,-------------- >> | +ATTR_BACKEND: >> `-------------- >> >> construct of the parent backend and don't have their own >> >> ,-------------- >> | +ATTR_MY-BACKEND: >> `-------------- >> >> construct? > > You can use any name you want for attributes > > #+attr_my-special-name > > and then retrieve it with > > (org-export-read-attribute :attr_my-special-name element) I've seen this in ox backends, but since I sometimes simply use the parse-tree as produced by `org-element-parse-buffer', I wonder why something like ,------------------------------------------------ | #+CAPTION: My minimal table | #+ATTR_HTML: :border 2 :rules all :frame border | | col1 | col2 | | |------+------| | | val1 | val2 | `------------------------------------------------ actually is included in the tables property list ,-------------------------------------------------------------------------- | (table (begin 205... attr_html (":border 2 ... :frame border") ...) ) `-------------------------------------------------------------------------- although the exporter is never called - only org-element? PS I would like to have that too - how is that achieved? -- cheers, Thorsten