Hello,
Trying to export a table with alignment tags, e.g.
#+caption: left, center and right aligned columns
| | | |
| a |b |c |
| aa | | |
In, for example, HTML or ODT output, the columns are aligned according
to the tags in the first
Hello,
Trying to export a table with alignment tags, e.g.
#+caption: left-, centre- and right aligned columns
| | | |
| a | b | c |
| aa | | |
In, for example, HTML or ODT output, the columns are aligned according
to the tags in the fir
On 30/11/2021 15:09, Bruce D'Arcus wrote:
Did pandoc get support for org-cite?
There's been basically zero activity on this issue I created awhile back:
https://github.com/jgm/pandoc/issues/7329
AFAIK pandoc still doesn't support the official Org Mode syntax.
ox-pandoc relies on the fact th
Hello,
ox-pandoc is an exporter for Org Mode that uses pandoc
(https://pandoc.org/) to export to a very wide variety of text markup
(e.g. markdown variants), document (ODT, docx) and presentation (e.g.
html, .pdf) formats. It is available via MELPA and at:
https://github.com/emacsorphanage/ox
Hello,
I have recently forked [1] and tidied up ox-pandoc with some fixes for
incompatibilities that had arisen with newer versions of pandoc. I'm talking to
MELPA people about getting this distributed.
Briefly, ox-pandoc exports an .org file to a temporary .org (so that e.g. Babel
code is res
Hi Aaron
First of all, no issue arises with :output-dir alone. It can be
specified as a global header arg without issue.
Yes, now I check again that's true. Thank you for clearing that up.
I designed :file-ext as a direct replacement for :file. That is, instead
of the above, one would spec
On 25/05/18 01:13, Nicolas Goaziou wrote:
Hello,
Alex Fenton writes:
As far I understand it, |:output-dir| and |:file-ext| that were
intended to be used in the global document header, applying to all
blocks.
However, it seems to mean that all blocks regardless of their :results
args then
Hi,
As far I understand it, |:output-dir| and |:file-ext| that were intended
to be used in the global document header, applying to all blocks.
However, it seems to mean that all blocks regardless of their :results
args then emit a file, and put their output as a [file:] link. It's not
clear
Hello,
On 08/11/16 18:49, Nicolas Goaziou wrote:
Per above, you could use latexmk "-C" option and move both ".tex" and
".pdf" file to appropriate directories.
I wasn't aware of the "-C" option, it looks like it could - with some
settings - blow away the intermediate files that latexmk uses to
Hello,
On 05/11/16 23:54, Nicolas Goaziou wrote:
Honestly, I'm surprised it worked. I'm also surprised it could be
related to `default-directory' set-up, since links are created during
Org -> LaTeX conversion, whereas `org-compile-file' handles LaTeX ->
PDF. What is that "simple publishing set-u
Firstly, congratulations and thanks to all the contributors to the new
release.
One thing that has unfortunately stopped working is my setup for
exporting to pdf, putting all the intermediary (.tex, .aux, .bbl, etc)
and output files in a different directory to the source .org files. My
setup
On 27/04/16 21:41, John Kitchin wrote:
you might also checkout helm-bibtex. A recent note indicated "Support
for pre- and postnotes for pandoc-citeproc citations."
Thanks, I already use helm-bibtex together with org-ref so will have a look.
this exports out of the org-ref box to:
blah blah bla
Hi Richard
On 27/04/16 16:09, Richard Lawrence wrote:
As far as Elisp implementations go, I know of no specific parser for
Pandoc citation syntax. But there is support for a Pandoc-like syntax
(discussed in the threads you read) in the wip-cite branch of Org's
repository.
https://github.com/
Hello,
I see that there were several extensive and fruitful discussions on this
list last year on citation syntax. There seemed to be a reasonable
degree of consensus that pandoc-style citation syntax was at the least a
good model.
I'd like to know if there are any implementations out there
14 matches
Mail list logo
