From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Re: [patch] two bugs: one with comments and with exporting inline tasks Date: Thu, 04 Nov 2010 18:45:32 +0100 Message-ID: <87aalpc79f.wl%n.goaziou@gmail.com> References: <87iq0gknpg.fsf@pinto.chemeng.ucl.ac.uk> <87pqunv83v.wl%n.goaziou@gmail.com> <87iq0fla93.fsf@ucl.ac.uk> <8739rjl3s6.fsf@ucl.ac.uk> <87mxppcz8r.wl%n.goaziou@gmail.com> <87lj59cyrz.wl%n.goaziou@gmail.com> <87k4ktcyax.wl%n.goaziou@gmail.com> <878w19gzdq.fsf@ucl.ac.uk> <87iq0dchfm.wl%n.goaziou@gmail.com> <87wrotgoer.fsf@ucl.ac.uk> <87hbfxcfq2.wl%n.goaziou@gmail.com> <878w19azbv.fsf@ucl.ac.uk> <87eib1cdm4.wl%n.goaziou@gmail.com> <87vd4d9i7r.fsf@ucl.ac.uk> <80y6993vao.fsf@mundaneum.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Return-path: Received: from [140.186.70.92] (port=60378 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PE3sV-0002rT-4c for emacs-orgmode@gnu.org; Thu, 04 Nov 2010 13:45:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PE3sT-0000PZ-FK for emacs-orgmode@gnu.org; Thu, 04 Nov 2010 13:45:34 -0400 Received: from mail-ww0-f49.google.com ([74.125.82.49]:43883) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PE3sT-0000PV-B0 for emacs-orgmode@gnu.org; Thu, 04 Nov 2010 13:45:33 -0400 Received: by wwe15 with SMTP id 15so2342597wwe.30 for ; Thu, 04 Nov 2010 10:45:32 -0700 (PDT) In-Reply-To: <80y6993vao.fsf@mundaneum.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?UTF-8?B?U8OpYmFzdGllbg==?= Vauban Cc: emacs-orgmode@gnu.org Hello, >>>>> Sébastien Vauban writes: > Eric S Fraga wrote: >> In terms of what to actually do with inline tasks on export, what I >> would love to see would be to have an inline task converted to a >> footnote with a marginpar note, along the lines of: >> >> #+begin_src latex >> \footnote{\textbf{<>}: <>}\marginpar{\fbox{\thefootnote}} >> #+end_src >> >> i.e. where <> would be replaced by "TODO figure out >> why this doesn't work" and <> by all the text between >> the ****** lines. This is roughly the type of construct I use when >> I annotate latex documents directly. What do you think? > ... that we need this. What about creating a customizable alist, namely org-inlinetask-export-templates, containing exporters paired with format strings? For example, it could contain : '((html . "<@span class=\"%s %s\" %s@") (latex . "\\footnote{\\textbf{%s %s}: %s}\\marginpar{\\fbox{\\thefootnote}}")) where first %s is TODO, second %s is heading, and third one is content. Default values would be whatever is used right now. Any comments? Regards, -- Nicolas