emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@gnu.org>
To: Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: ox-html: add option to restore old src block behaviour?
Date: Tue, 11 Feb 2020 16:40:10 +0100	[thread overview]
Message-ID: <87sgjhqgit.fsf@gnu.org> (raw)
In-Reply-To: <CAN_Dec9j7aXxGTBkkC30+Qi2EvkoECtfAEMeVG0xf+ZfHeviug@mail.gmail.com> (Matt Price's message of "Thu, 19 Sep 2019 12:33:20 -0400")

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

-- 
 Bastien

next prev parent reply	other threads:[~2020-02-11 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 16:33 ox-html: add option to restore old src block behaviour? Matt Price
2020-02-11 15:40 ` Bastien [this message]
2020-02-14 17:42   ` Jens Lechtenboerger
2020-02-14 20:35     ` Bastien

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=87sgjhqgit.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=moptop99@gmail.com \
    /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

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