Hi Nicolas,
> Nicolas Goaziou wrote:
>> To maintainers:
>> - to sum it up, if you don't like the idea of templates, or how it is
>> implemented, all commits but the last one are only fixes.
>> - could you delete submissions from 11-04 and 11-06 (but _not_ from
>> 10-26) on the patchwork server, as they are now included in the
>> repo?
>>
>> I'm now waiting for comments from the 3-3.5 persons in the world using
>> inline tasks!
>
> I guess I'm the last 0.5 user of inline tasks ;-)
>
> I really have no time just now, but I promise trying your patch in the next
> coming 2 days. Promised.
OK; this has been DEFERRED a bit, but DONE nonetheless...
I tested the look and feel of the export to HTML and PDF. Works fine.
Works even better (IMHO) with the suggested template:
#+begin_src emacs-lisp
;; templates for inline tasks in various exporters
(setq org-inlinetask-export-templates
'((html "<pre class=\"inlinetask\">%s%s</b><br>%s</pre>"
'((unless (eq todo "")
(format "<b><span class=\"%s %s\">%s%s</span> "
class todo todo priority))
heading content))
(latex "\\todo[inline]{\\textbf{\\textsf{%s %s}}\\linebreak{} %s}"
'((unless (eq todo "")
(format "\\textsc{%s%s}" todo priority))
heading content))
;; [...]
))
#+end_src
The advantage is to get a real different look for the inlined task, so that it
gets your attention as it deserves it.
- Regarding HTML, if you don't replace your list environment by my
proposition, I would at least exchange the position of the blank space.
Better is:
#+begin_src emacs-lisp
(format "<b><span class=\"%s %s\">%s%s</span> "
;; ^ ^
#+end_src
Otherwise, when TODO keywords have background colors, you see the keyword
with one space too much...
- Regarding LaTeX, my suggestion requires the =todonotes= LaTeX package to be
loaded in the header.
Thanks for your work!
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
