emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [Bug] MCE for HTML test of export
Date: Sat, 19 Mar 2011 12:05:26 +0100	[thread overview]
Message-ID: <80lj0bpdzd.fsf@somewhere.org> (raw)
In-Reply-To: <87d3lp8ypt.fsf@gmail.com>

Hi Nicolas,

Nicolas wrote:
> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> Regarding this problem only, it must be an interaction then with my
>> following setting for the inline task in HTML:
>> #+begin_src emacs-lisp
>>           ;; templates for inline tasks in various exporters
>>           (setq org-inlinetask-export-templates
>>                 '((html "<pre class=\"inlinetask\"><b>%s%s</b><br>%s</pre>"
>>                         '((unless (eq todo "")
>>                             (format "<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))
>>                   (ascii "     -- %s%s%s"
>>                          '((unless (eq todo "")
>>                              (format "%s%s " todo priority))
>>                            heading
>>                            (unless (eq content "")
>>                              (format "\n         ¦ %s"
>>                                      (mapconcat 'identity
>>                                                 (org-split-string content "\n")
>>                                                 "\n         ¦ ")))))))
>> #+end_src
> Indeed, it came from your templates. To prevent this, I made sure, with the
> following patch, that CONTENT is always enclosed by newline characters.
> Would you mind testing it before I apply it ?

Perfect. Works like a charm. Please do apply it...

> Also, you may have a look at default templates, as your HTML variant is
> slightly wrong (wrt <br> tag).

I'm not sure to understand what's "wrong". You mean the fact I added manually
a <br> tag after the title?

If yes, it was to have the "title" line (task subject, with TODO keyword) on
its own line, followed by the rest of the entry on subsquent paragraphs.

But, indeed (after testing it), it seems I am not (anymore?) forced to insert
that. Was it this you were talking about?

Thanks for the comment, anyway... and for the patch!

Best regards,

Sébastien Vauban

  reply	other threads:[~2011-03-19 11:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 16:09 Sébastien Vauban
2011-03-15 17:43 ` Nicolas
2011-03-15 22:08   ` Sébastien Vauban
2011-03-17 17:05     ` Nicolas
2011-03-19 11:05       ` Sébastien Vauban [this message]
2011-03-19 17:25         ` Nicolas
2011-03-19 17:48           ` Aankhen

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:

  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=80lj0bpdzd.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    --subject='Re: [Bug] MCE for HTML test of export' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).