From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: org-latex-classes with functions, incomplete doc Date: Sun, 10 Feb 2013 22:52:11 +0100 Message-ID: <87liavet10.fsf@gmail.com> References: <87txpkrvzi.fsf@sophokles.streitblatt.de> <87bobsf68g.fsf@gmail.com> <87zjzcqcq8.fsf@sophokles.streitblatt.de> <877gmgf2ts.fsf@gmail.com> <87halkq9kq.fsf@sophokles.streitblatt.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38761) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4ep4-0002jJ-Be for emacs-orgmode@gnu.org; Sun, 10 Feb 2013 16:52:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U4ep2-00053U-W1 for emacs-orgmode@gnu.org; Sun, 10 Feb 2013 16:52:30 -0500 Received: from mail-wi0-f178.google.com ([209.85.212.178]:38904) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4ep2-00053K-Ok for emacs-orgmode@gnu.org; Sun, 10 Feb 2013 16:52:28 -0500 Received: by mail-wi0-f178.google.com with SMTP id o1so2522477wic.5 for ; Sun, 10 Feb 2013 13:52:27 -0800 (PST) In-Reply-To: <87halkq9kq.fsf@sophokles.streitblatt.de> (Florian Beck's message of "Sun, 10 Feb 2013 19:59:17 +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: Florian Beck Cc: Florian Beck , emacs-orgmode@gnu.org Florian Beck writes: > Nicolas Goaziou writes: > >>> (toc-title (if (plist-get info :toc-title) >>> (org-element-property :toc-title headline))) >> >> There's no :toc-title property in the communication channel. The >> exhaustive list of its properties is written in ox.el, at "The >> Communication Channel" section. > > Obviouly, I defined it, otherwise it wouldn't work. > > :options-alist ((:toc-title "TOC_TITLE" nil nil t) ... ) > >>> As you can see, the solution is much more convoluted. >> >> Because you're not using the proper tool. If you just want to modify the >> string returned by the `latex' back-end, use a filter. You will have >> access to the transcoded headline (in LaTeX format, as a string) and the >> communication channel. > > But not to the element properties, which is what I need. > >> There are already many ways to alter output from a back-end. It's just >> a matter of using the right tool. > > So, which is it? I'm a bit confused right now. I now get what you intend to do (or so I think). I didn't implement this feature in ox-latex.el, mainly because a proper implementation needs to be done at the ox.el level. Anyway, we're back to step one: if you want to handle headlines differently (i.e. by adding your own properties), you need to fork `latex' back-end, as explained before. If you encounter problems, you can post back here. Regards, -- Nicolas Goaziou