variable was introduced, or its default value was changed, in
> version 8.3 of the Org package.
>
>
> Value: ((path "https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.0/
> MathJax.js?config=TeX-AMS_HTML")
> (scale "100")
> (align "center")
> (font "TeX")
> (linebreaks "false")
> (autonumber "AMS")
> (indent "0em")
> (multlinewidth "85%")
> (tagindent ".8em")
> (tagside "right"))
>
> -- End ---
>
>
> Best wishes,
>
> Colin.
>
> --
> --
> Colin Baxter
> m43...@yandex.com
> GnuPG fingerprint: 68A8 799C 0230 16E7 BF68 2A27 BBFA 2492 91F5 41C8
>
>
--
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655*
it down right now)
if you don't do the settings via (org-html-mathjax-options) you get
orgmode.org's hosting of mathjax.js via HTTP. It would seem wiser to either
host this under HTTPS so that the loading of mixed-content is not blocked
when using HTTPS or change that to also using the cdn.
-adam
the
terms of service. Perhaps that should be a discussion for another thread,
though.
-aja
--
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655*
0001-Fixing-link-to-mathjax-cdn-as-cdn.mathjax.org-is-shu.patch
Description: Binary data
Thanks for the comments... very helpful! This is a perfect example of when
living on the bleeding edge of a library and searching for solutions can
come into conflict. I'll stick to looking at the docs built off the git
repo.
On Fri, Jul 22, 2016 at 5:15 PM, Nick Dokos wrote:
> A
ut dated:
http://orgmode.org/manual/Quoting-HTML-tags.html
Is there a push cycle to keep the online documents up to date with the
source documentation? Or is that controlled differently?
--
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655*
the
documentation to reflect it?
--
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655*
now with
#+BEGIN_EXPORT html
#+END_HTML
If so, is there a way to make compilation backwards compatible. I have a
lot of old org files that would be a pain to update. Further, all the
documentation on the org site is also out of date.
--
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science
eness.
I'll look into the :property issue: I think that'd properly work for my
needs.
--
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655*
might be suboptimal given that
not every block is referenced later.
I would still like to be able to add my own name tags, but understand why
this might have been changed to avoid to blocks having the same label.
--
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655*
tag around the src code that will get
exported?
Thanks!
adam
--
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655*
Robert Klein roklein.de> writes:
>
> Hi
>
> Aviv wrote:
>
> > Hi!
> >
> > I just upgraded to org 8.3 and am stuck with an export issue.
> >
> > When I try to export a file with just "#+begin_src" and " "#+end_src" a
Hi!
I just upgraded to org 8.3 and am stuck with an export issue.
When I try to export a file with just "#+begin_src" and " "#+end_src" as the
only lines, I get the error
"user-error: No language for src block: (unnamed)".
It seems like it is calling org-babel-exp-process-buffer -- but there
wn o:fox jumps over the o:lazy_dog.
And `[[o:foo bar][foo bar]]` is even
more verbose to type and edit (though it reads fine in org modde).
FYI, I was asked to crosspost this from stackoverflow at
http://stackoverflow.com/q/21085720/1137803
(I waited several weeks with no answer; I hope that is appropriate)
Regards
- Aviv
13 matches
Mail list logo
