From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@gnu.org>
Subject: Re: ox-html: add option to restore old src block behaviour?
Date: Tue, 11 Feb 2020 16:40:10 +0100
Message-ID: <87sgjhqgit.fsf@gnu.org>
References: <CAN_Dec9j7aXxGTBkkC30+Qi2EvkoECtfAEMeVG0xf+ZfHeviug@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:45457)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <bzg@gnu.org>) id 1j1Xe3-0001Br-Nw
 for emacs-orgmode@gnu.org; Tue, 11 Feb 2020 10:40:16 -0500
In-Reply-To: <CAN_Dec9j7aXxGTBkkC30+Qi2EvkoECtfAEMeVG0xf+ZfHeviug@mail.gmail.com>
 (Matt Price's message of "Thu, 19 Sep 2019 12:33:20 -0400")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org
Sender: "Emacs-orgmode"
 <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org>
To: Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>

Hi Matt,

Matt Price <moptop99@gmail.com> writes:

> However, at least one very common syntax highlighter, https://
> highlinghtjs.org, expects just a single <code> tag, as do other
> common CSS frameworks. These often leave odd borders or background
> color disruptions which somewhat distort the view of the code.
> There's also a funny conflict with `org-re-reveal`, which expects the
> old behaviour (see https://gitlab.com/oer/org-re-reveal/issues/27).=C2=A0
> It would in principal be possible to fix these issues directly in
> CSS, but it might be much more practical to have an option -- a
> defvar or a file/headline-settable property -- that restores the old
> behaviour when desired.=C2=A0 If this would be welcome, I could do it. I
> know org already has a bewildering number of options,though,and the
> code change would be oddly a number of times as large as the
> substantive change of that commit, os thought I'd check first.

Yes, an option makes sense here -- can you provide one that allows to
restore the old behavior (and avoid all those <code>...</code> lines)?

Thanks in advance!

--=20
 Bastien