* ox-html: add option to restore old src block behaviour?
@ 2019-09-19 16:33 Matt Price
2020-02-11 15:40 ` Bastien
0 siblings, 1 reply; 4+ messages in thread
From: Matt Price @ 2019-09-19 16:33 UTC (permalink / raw)
To: Org Mode
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
reiterating a question I posted to an old thread that may have gotten lost.
Over the summer, commit ded3d27b1468b878197e5fe55a70c5e13350ea27 by Nik
Clayton was merged to master. It's a one-line change that adds new ~<code>~
tags around each lin of code in html export of source blocks. It's useful
because it allows individual lines to be addressed directly by CSS.
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.
Thanks!
Matt
[-- Attachment #2: Type: text/html, Size: 1477 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ox-html: add option to restore old src block behaviour?
2019-09-19 16:33 ox-html: add option to restore old src block behaviour? Matt Price
@ 2020-02-11 15:40 ` Bastien
2020-02-14 17:42 ` Jens Lechtenboerger
0 siblings, 1 reply; 4+ messages in thread
From: Bastien @ 2020-02-11 15:40 UTC (permalink / raw)
To: Matt Price; +Cc: Org Mode
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ox-html: add option to restore old src block behaviour?
2020-02-11 15:40 ` Bastien
@ 2020-02-14 17:42 ` Jens Lechtenboerger
2020-02-14 20:35 ` Bastien
0 siblings, 1 reply; 4+ messages in thread
From: Jens Lechtenboerger @ 2020-02-14 17:42 UTC (permalink / raw)
To: Bastien; +Cc: Org Mode
On 2020-02-11, at 16:40, Bastien wrote:
> 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)?
Hi Bastien,
that issue has been resolved:
https://lists.gnu.org/archive/html/emacs-orgmode/2019-10/msg00099.html
Best wishes
Jens
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-02-14 20:36 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-19 16:33 ox-html: add option to restore old src block behaviour? Matt Price
2020-02-11 15:40 ` Bastien
2020-02-14 17:42 ` Jens Lechtenboerger
2020-02-14 20:35 ` Bastien
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).