New answers tagged

0

I think you might be looking for something like this: (defvar se-wrap-executable "C:/Program Files/Wraparound/Wrap/wrap.exe" "Wrap is an open source command line tool that is able to convert Fountain and Wrap files into a correctly formatted screen- or stageplay as an HTML or a PDF. See `https://github.com/Wraparound/wrap'") (defvar ...


0

Okay so I solved the issue with some insight that if the command was failing to produce /tmp/orgtexlUjxgz.xdv then there must be a /tmp/orgtexlUjxgz.log with detail about the issue. And, sure enough, looking at /tmp/orgtexlUjxgz.log I realised that I was missing a package and resolving that fixed the org-toggle-latex-fragment.


1

For HTML, you can add CSS to hide borders completely. By default, I get a border width of 2 and a rules setting of group. You can override these like this: * foo #+ATTR_HTML: :border 0 :rules none | a | b | |---+---| | 1 | 2 | | 3 | 4 | For LaTeX/PDF, by default I get just an \hline corresponding to the hline that I have in the table separating the header ...


1

In order to use #+LATEX_CLASS: homework you must have added an entry to the variable org-latex-classes - otherwise you would have gotten an Unknown LaTeX class 'homework' error. Presumably you have already done this since you don't get that error. To add things to the LaTeX preamble (the part before \begin{document} you need to use #+LATEX_HEADER. E.g. to ...


0

Despite doing M-x list-packages -> U -> x, org hadn't been updated (probably because it was not installed through melpa). After upgrading org the error disappeared.


2

I would continue using the macro. You can use markup inside the macro that expands differently for HTML export than it does for PDF export. For example, as a first approximation, this will allow you to get the dates in the HTML output, although they are not nicely formatted - but it's a beginning: #+MACRO: date @@latex: \hfill\normalfont{\small $1} @@ @@...


0

EDIT/ The #+BIND: keyword needs to be turned on as well: (setq org-export-allow-bind-keywords t) I had set that variable and forgotten about it, but the default is nil I think (primarily to protect you from yourself I guess). The doc string for the variable says: Non-nil means BIND keywords can define local variable values. This is a potential ...


2

As @rpluim mentions in a comment, setting org-export-with-sub-superscripts to nil would disable the special handling of ^ and _ for subscripts and superscripts. There is one more variable that is relevant (when org-export-with-sub-superscripts is t) and that is org-use-sub-superscripts which can be set to t or nil - or it can be set to the value {}. I find ...


Top 50 recent answers are included