From: Matt Price <moptop99@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] ox-html: add option to restore old src block behaviour?
Date: Wed, 2 Oct 2019 20:16:11 -0400 [thread overview]
Message-ID: <CAN_Dec9Y+mHmm67OEUzUDABBuc79qnYDdeTJy59+vz7=2=msNA@mail.gmail.com> (raw)
In-Reply-To: <87h8553kwm.fsf@informationelle-selbstbestimmung-im-internet.de>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
So I'm pretty interested in this: what to others thi k?
On Sat., Sep. 21, 2019, 8:16 a.m. Jens Lechtenboerger, <
jens.lechtenboerger@fsfe.org> wrote:
> On 2019-09-19, Matt Price wrote:
>
> > 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.
> > [...]
>
> The attached patch adds a new variable org-html-wrap-src-lines to
> control whether code tags should be added or not.
>
> I’m not sure whether :package-version 9.3 is correct. Also, I set
> the value to t, which does not change the current functionality.
> However, for backwards compatibility (up to version 9.2.6), a value
> of nil would be preferable. Any thoughts?
>
> Best wishes
> Jens
>
>
[-- Attachment #2: Type: text/html, Size: 1578 bytes --]
next prev parent reply other threads:[~2019-10-03 0:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 12:15 [PATCH] ox-html: add option to restore old src block behaviour? Jens Lechtenboerger
2019-10-03 0:16 ` Matt Price [this message]
2019-10-08 9:31 ` Nicolas Goaziou
2019-10-08 18:40 ` Jens Lechtenboerger
2019-10-13 7:30 ` Nicolas Goaziou
2019-10-13 12:16 ` Jens Lechtenboerger
2019-10-16 17:06 ` Nicolas Goaziou
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='CAN_Dec9Y+mHmm67OEUzUDABBuc79qnYDdeTJy59+vz7=2=msNA@mail.gmail.com' \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.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).