From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: Re: [patch] two bugs: one with comments and with exporting inline tasks
Date: Fri, 05 Nov 2010 12:50:27 +0000 [thread overview]
Message-ID: <87zktoue7g.fsf@pinto.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <87aalpc79f.wl%n.goaziou@gmail.com> (Nicolas Goaziou's message of "Thu, 04 Nov 2010 18:45:32 +0100")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> 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{<<headline text>>}: <<body text>>}\marginpar{\fbox{\thefootnote}}
>>> #+end_src
>>>
>>> i.e. where <<headline text>> would be replaced by "TODO figure out
>>> why this doesn't work" and <<body text>> 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@</span>")
> (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
This sounds perfect!
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 23.2.1
: using Org-mode version 7.02trans (release_7.3.26.g4d02)
prev parent reply other threads:[~2010-11-05 12:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 10:46 [bug] two bugs: one with comments and with exporting inline tasks Eric S Fraga
2010-11-02 19:27 ` Nicolas Goaziou
2010-11-02 20:51 ` Eric S Fraga
2010-11-02 23:11 ` Eric S Fraga
2010-11-04 7:41 ` Nicolas Goaziou
2010-11-04 7:51 ` [patch] " Nicolas Goaziou
2010-11-04 8:01 ` Nicolas Goaziou
2010-11-04 10:24 ` Eric S Fraga
2010-11-04 14:05 ` Nicolas Goaziou
2010-11-04 14:21 ` Eric S Fraga
2010-11-04 14:42 ` Nicolas Goaziou
2010-11-04 15:22 ` Eric S Fraga
2010-11-04 15:28 ` Nicolas Goaziou
2010-11-04 16:17 ` Eric S Fraga
2010-11-04 16:32 ` Sébastien Vauban
2010-11-04 17:45 ` Nicolas Goaziou
2010-11-05 8:01 ` Sébastien Vauban
2010-11-05 8:58 ` Sébastien Vauban
2010-11-05 12:50 ` Eric S Fraga
2010-11-05 12:50 ` Eric S Fraga [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zktoue7g.fsf@pinto.chemeng.ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=wxhgmqzgwmuf@spammotel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).