From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [bug] Org-verbatim and org-code not converted into HTML tags
Date: Fri, 02 May 2014 14:51:09 +0200 [thread overview]
Message-ID: <86k3a4fio2.fsf@somewhere.org> (raw)
In-Reply-To: 8738haj283.fsf@bzg.ath.cx
Hi Bastien,
Bastien wrote:
> Sebastien Vauban writes:
>
>> 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.
>
> Can you bisect to spot the first bad commit, and tell exactly
> what's bad here from an emacs -Q point of view?
It took me a while to understand what was going on. But I did.
See http://screencast.com/t/1peLgaZ7.
The "styling" bug is present in all latest Emacs versions, and relates
to the Emacs bug #16440 ("Some colors of the theme aren't respected in
latest Emacs"):
╭──── From: Eli Zaretskii
│
│ This seems to be the consequence of the change described in NEWS like
│ this:
│
│ *** Face specs set via Custom themes now replace the `defface' spec
│ rather than inheriting from it (as do face specs set via Customize).
│
│ Org uses org-copy-face to define the faces that you show in your
│ screencast, and org-copy-face assumes the face it inherits from
│ already exists. But loading a theme now doesn't create the faces, it
│ only prepares the data for when the face will be created. So :inherit
│ in org-copy-face doesn't do what you expect.
│
│ I guess either some change is needed in how themes are handled, or
│ org-copy-face needs to change to follow suit. (CC to Bastien for
│ that.)
╰────
See http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16440 for the whole
thread.
Best regards,
Seb
--
Sebastien Vauban
prev parent reply other threads:[~2014-05-02 12:51 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
2014-05-02 12:51 ` Sebastien Vauban [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=86k3a4fio2.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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).