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!