From: Andreas Reuleaux <andreas@a-rx.info>
To: emacs-orgmode@gnu.org
Subject: Re: org-ref code
Date: Wed, 14 May 2014 21:08:30 +0100 [thread overview]
Message-ID: <874n0skts1.fsf@a-rx.info> (raw)
In-Reply-To: 87oaz09m5v.fsf@skimble.plus.com
Well, I know how to write shell scripts,
and have something similar encoded in a shake file
(haskell make replacement), for that matter,
but prefer to have xelatex not called 5 times
during every little development step.
Anyway thanks a lot.
My point here really was, that org-ref and
the latex chains are separate and can be
separately tested.
-Andreas
Sharon Kimble <boudiccas@skimble.plus.com> writes:
> Andreas Reuleaux <andreas@a-rx.info> writes:
>
>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>>
>>
>>> How do I specify the bibstyle for org-ref?
>>
>>
>> I am not sure if I understand your question correctly
>> and John certainly has more insight here, but I have in
>> my org document
>>
>> #+LaTeX_HEADER: \include{ltxhdr}
>>
>> and within that ltxhdr.tex I have among other config settings
>>
>> \usepackage[backend=bibtex,style=authoryear]{biblatex}
>> \addbibresource{refs.bib}
>>
>> I could have written several lines of
>>
>> #+LaTeX_HEADER: \usepackage[backend=bibtex,style=authoryear]{biblatex}
>> #+LaTeX_HEADER: \addbibresource{refs.bib}
>>
>> instead.
>>
>> There is no specific bibstyle of org-ref (correct, John?), that's the
>> job of latex, you will be happy if:
>>
>> * your org mode has clickable citations links,
>>
>> * let's you insert citations in a comfortably manner
>>
>> * you can jump between refs and labels etc.
>>
>> * all of those citations get exported to their latex
>> equivalents
>>
>> If for some reason your citations get exported to latex, say
>> cite:foo to \cite{foo}, but still don't appear in your
>> final pdf, than you have to tweek your latex settings,
>> obviously. - Maybe forgot to call bibtex(8) on your document?
>>
>> I run these:
>> * an emacs batch script, tex.el to get the document.tex
>> from document.org
>> * xelatex -8bit -shell-escape document.tex
>> * bibtex8 document
>> * xelatex document
>> again, etc.
>>
>> You can check your latex toolchain independently from
>> your org-ref config.
>>
>> HTH,
>> -Andreas
>
> That seems a very long winded way round things! For your information
> this is a batch script that I'm using for generating a PDF in pure
> latex, and all I have to do is to cd to the directory where the
> files are, and then just enter "pdfbuild" in the command-line. It
> does all the rest itself, and you could easily adapt it for your
> circumstances
> #!/bin/bash
> set -e
> #set -x
>
> #variables
> filename="uh2014"
>
> #############
> xelatex $filename
> biber $filename
> biber $filename
> xelatex $filename
> biber $filename
> xelatex $filename
> makeindex $filename
> makeindex $filename
> xelatex $filename
> makeglossaries $filename
> xelatex $filename
> xelatex $filename
>
> It handles and generates the references, the glossary, and the index
> as well as the body of the document.
>
> All you have to do is enter your "foo.tex" where foo is the name of
> your generated tex file, and then let the script take over.
>
> Sharon.
next prev parent reply other threads:[~2014-05-14 20:10 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 20:59 org-ref code John Kitchin
2014-05-01 6:23 ` Eric S Fraga
2014-05-01 10:01 ` Eric S Fraga
2014-05-01 12:21 ` Seb Frank
2014-05-01 14:08 ` Eric S Fraga
2014-05-01 12:36 ` John Kitchin
2014-05-01 12:47 ` John Kitchin
2014-05-01 13:30 ` Eric S Fraga
2014-05-01 17:07 ` John Kitchin
2014-05-10 14:44 ` Eric S Fraga
2014-05-11 18:48 ` John Kitchin
2014-05-12 8:12 ` Andreas Reuleaux
2014-05-13 2:37 ` John Kitchin
2014-05-12 13:36 ` Eric S Fraga
2014-05-12 17:20 ` Andreas Reuleaux
2014-05-12 17:26 ` John Kitchin
2014-05-13 0:03 ` Andreas Reuleaux
2014-05-13 11:00 ` Eric S Fraga
2014-05-13 18:51 ` John Kitchin
2014-05-13 20:01 ` Eric S Fraga
2014-05-13 20:11 ` Eric S Fraga
2014-05-14 0:28 ` John Kitchin
2014-05-14 18:17 ` Eric S Fraga
2014-05-14 19:03 ` Andreas Reuleaux
2014-05-14 19:48 ` Sharon Kimble
2014-05-14 20:08 ` Andreas Reuleaux [this message]
2014-05-14 22:14 ` Eric S Fraga
2014-05-14 20:35 ` John Kitchin
2014-05-15 6:58 ` Eric S Fraga
2014-05-15 8:17 ` Eric S Fraga
2014-05-15 13:05 ` John Kitchin
2014-05-15 13:14 ` Eric S Fraga
2014-05-15 13:30 ` Eric S Fraga
2014-05-15 14:19 ` John Kitchin
2014-05-15 14:31 ` Eric S Fraga
2014-05-15 15:03 ` Eric S Fraga
2014-05-15 13:15 ` John Kitchin
2014-05-14 3:58 ` Andreas Reuleaux
2014-05-14 13:17 ` John Kitchin
2014-05-13 23:33 ` Andreas Reuleaux
2014-05-14 0:38 ` John Kitchin
2014-05-14 3:39 ` Andreas Reuleaux
2014-05-14 13:14 ` John Kitchin
2014-05-14 17:39 ` Andreas Reuleaux
2014-05-18 17:16 ` org-ref for biblatex Andreas Reuleaux
2014-05-18 21:40 ` John Kitchin
2014-05-18 22:38 ` Andreas Reuleaux
2014-05-19 11:38 ` John Kitchin
2014-05-19 12:15 ` Andreas Reuleaux
2014-05-19 17:34 ` Andreas Reuleaux
2014-05-08 8:31 ` org-ref code Vikas Rawal
2014-05-08 13:53 ` John Kitchin
2014-05-15 10:09 ` 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=874n0skts1.fsf@a-rx.info \
--to=andreas@a-rx.info \
--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).