emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Sebastien Vauban
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: [bug] Org-verbatim and org-code not converted into HTML tags
Date: Fri, 18 Apr 2014 13:39:40 +0200	[thread overview]
Message-ID: <8738haj283.fsf@bzg.ath.cx> (raw)
In-Reply-To: <86ioqx1jhd.fsf@somewhere.org> (Sebastien Vauban's message of "Sat, 29 Mar 2014 09:45:18 +0100")

Hi Sébastien,

Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>

> Though, there are extra diffs in my HTML output, about the style of the
> org-block delimiter lines: they've lost their "under/over-line" feature,
> and colors are not the same anymore.

not sure how this would relate to the bug you reported and that
Nicolas fixed in this thread.

Can you bisect to spot the first bad commit, and tell exactly
what's bad here from an emacs -Q point of view?



  reply	other threads:[~2014-04-18 11:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 15:24 [bug] Org-verbatim and org-code not converted into HTML tags Sebastien Vauban
2014-03-28 16:31 ` Nicolas Goaziou
2014-03-29  8:45   ` Sebastien Vauban
2014-04-18 11:39     ` Bastien [this message]
2014-05-02 12:51       ` Sebastien Vauban

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=8738haj283.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org \


* 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


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