From: Bastien <bzg@altern.org>
To: "T.F. Torrey" <tftorrey@tftorrey.com>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: BIND org-html-style-include-*
Date: Fri, 15 Feb 2013 22:21:21 +0100 [thread overview]
Message-ID: <87d2w19stq.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87liapi8r2.fsf@lapcat.tftorrey.com> (T. F. Torrey's message of "Fri, 15 Feb 2013 14:10:09 -0700")
Hi Terry,
tftorrey@tftorrey.com (T.F. Torrey) writes:
> However, the new HTML exporter includes the MathJax JavaScript every
> time, and I don't see any variable to set to suppress it.
This is not the case anymore since commit 4d7f4d87.
> Recent posts by Bastien suggest that maybe it is supposed to be included
> only if LaTeX is used in the buffer, but I'm not sure he was talking
> about this issue.
I hope I was -- the MathJax config will now be included if your HTML
page contains LaTeX snippets to display. It will not be included
otherwise.
> With the new exporter on my Org, even the most minimal Org file exported
> to HTML includes MathJax. My Org version is 7.9.3e-1032-g791a8d. The
> most recent pulls fail testing (which people must already know).
You are behind a few commits, please update.
> (By the way, though it may be too late to change them now, the variables
> would be better named "org-html-include-style-default" and
> "org-html-include-scripts-default" and possibly
> "org-html-include-scripts-mathjax". The HTML exporter has many things
> that might be included in the output, and having the variables all
> starting with "org-html-include-" would make them easier for everyone to
> find, understand, and modify.)
I somewhat agree. But C-h v org-html-include TAB expands and display
all variables here, so maybe not such an issue. It is not too late to
change the names of the variables, but I'd rather stick to these names
because it lowers the effort when switching from 7.9 to 8.0.
> (Similarly, as someone else wrote, #+HTML_STYLE would be much better
> named #+HTML_HEAD, given that style is just one of the many things this
> directive might put into the head element of the html.)
For this one I agree completely. I will make this change.
--
Bastien
next prev parent reply other threads:[~2013-02-15 21:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 10:16 BIND org-html-style-include-* T.F. Torrey
2013-02-12 19:27 ` Nicolas Goaziou
2013-02-12 21:19 ` T.F. Torrey
2013-02-15 12:29 ` Nicolas Goaziou
2013-02-15 14:12 ` Bastien
2013-02-15 14:18 ` Nicolas Goaziou
2013-02-15 14:53 ` Bastien
2013-02-15 15:13 ` Nicolas Goaziou
2013-02-15 15:42 ` Bastien
2013-02-15 21:10 ` T.F. Torrey
2013-02-15 21:12 ` Sebastien Vauban
2013-02-15 21:21 ` Bastien [this message]
2013-02-15 21:35 ` Bastien
2013-02-15 23:22 ` T.F. Torrey
2013-02-18 17:07 ` 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=87d2w19stq.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=tftorrey@tftorrey.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
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).