From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Comment on Org Export Reference Date: Fri, 06 Mar 2015 18:23:14 +0100 Message-ID: <87pp8m82gt.fsf@nicolasgoaziou.fr> References: <14bedd41838.27cd.0bb60a3c7e492ea180363c67eb170725@qq.com> <14bee4be430.27cd.0bb60a3c7e492ea180363c67eb170725@qq.com> <877fuutfb8.fsf@wmi.amu.edu.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35616) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YTvws-0006Td-Jg for emacs-orgmode@gnu.org; Fri, 06 Mar 2015 12:22:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YTvwo-0004OG-QS for emacs-orgmode@gnu.org; Fri, 06 Mar 2015 12:22:06 -0500 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:60644) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YTvwo-0004O8-Ky for emacs-orgmode@gnu.org; Fri, 06 Mar 2015 12:22:02 -0500 In-Reply-To: <877fuutfb8.fsf@wmi.amu.edu.pl> (Marcin Borkowski's message of "Fri, 06 Mar 2015 14:40:11 +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: Marcin Borkowski Cc: emacs-orgmode@gnu.org Marcin Borkowski writes: > What I find especially missing is: documenting the underlying data > structures (and overall architecture =E2=80=93 in fact, I was thinking to= day > about writing a blog post about the main entry points to the exporter, > but this will probably have to wait a week or two), and a way to debug > it. While generating a data structure for an element is easy > (org-element-at-point), the `info' parameter is rather mysterious for me > (yet). I guess I'll have to run a few exporter functions through edebug > or something... `info' contents are almost completely explained in the reference documentation ("The Communication Channel" section). Missing properties are those used as a cache in various functions (e.g. :resolve-fuzzy-link-cache for `org-export-resolve-fuzzy-link'). Regards,