From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox-html: add option to restore old src block behaviour?
Date: Tue, 08 Oct 2019 11:31:41 +0200 [thread overview]
Message-ID: <87eezneg76.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87h8553kwm.fsf@informationelle-selbstbestimmung-im-internet.de> (Jens Lechtenboerger's message of "Sat, 21 Sep 2019 14:15:37 +0200")
Hello,
Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> writes:
> The attached patch adds a new variable org-html-wrap-src-lines to
> control whether code tags should be added or not.
Thank you.
However, the patch is not right. Exporters do not use defcustoms
directly. Instead, you register them within :options-alist in the the
back-end definition, e.g., under :html-wrap-src-lines and then call
(plist-get info :html-wrap-src-lines) in the function. This allows to
control these options during publishing.
Also, this would need an entry in the manual, if only in the "options
for the exporters" subsection.
> I’m not sure whether :package-version 9.3 is correct.
It is correct. You can also use :safe t.
> 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?
I agree with the nil default value.
> +(defcustom org-html-wrap-src-lines t
> + "If t, wrap individual lines of source blocks in \"code\" elements.
When non-nil, wrap...
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-10-08 9:31 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
2019-10-08 9:31 ` Nicolas Goaziou [this message]
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=87eezneg76.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--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).