From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Cc: Alessandro Bertulli <alessandro.bertulli96@gmail.com>
Subject: Re: Org-cite/Citar cannot recognize neither biblatex nor natbib
Date: Fri, 13 May 2022 07:03:09 -0400 [thread overview]
Message-ID: <CAF-FPGMGHFmzJzYnJAKWeRdQwm2nAYd8kxMnGJLSpqTJgso_aw@mail.gmail.com> (raw)
In-Reply-To: <87k0apem9b.fsf@ucl.ac.uk>
On Fri, May 13, 2022 at 6:54 AM Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
> On Friday, 13 May 2022 at 11:55, Alessandro Bertulli wrote:
> >> Check out org-latex-pdf-process maybe?
> >
> > I don't know the library so in depth, but I'll try, thank you!
>
> I have the following in my init file:
>
> (setq org-latex-pdf-process '("pdflatex -output-directory %o %f"
> "bibtex %b"
> "pdflatex -output-directory %o %f"
> "pdflatex -output-directory %o %f"))
>
> which tells org to run pdflatex, then bibtex, and then pdflatex twice
> more to ensure that all references are satisfied.
I thought org now by default, if available, uses latexmk, which should
take care of all this?
At least, it does for me.
Bruce
next prev parent reply other threads:[~2022-05-13 11:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 9:55 Org-cite/Citar cannot recognize neither biblatex nor natbib Alessandro Bertulli
2022-05-13 10:54 ` Eric S Fraga
2022-05-13 11:03 ` Bruce D'Arcus [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-13 17:20 Alessandro Bertulli
2024-02-13 12:01 ` Ihor Radchenko
2022-05-13 13:32 Alessandro Bertulli
2022-05-13 13:48 ` Bruce D'Arcus
2022-05-13 14:07 ` Ihor Radchenko
2022-05-13 15:42 ` Eric S Fraga
2022-05-13 13:15 Alessandro Bertulli
2022-05-13 13:20 ` Bruce D'Arcus
2022-05-13 10:01 Alessandro Bertulli
2022-05-12 18:31 Alessandro Bertulli
2022-05-12 18:38 ` Bruce D'Arcus
2022-05-13 6:45 ` Eric S Fraga
2022-05-12 14:48 Alessandro Bertulli
2022-05-12 14:54 ` Bruce D'Arcus
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=CAF-FPGMGHFmzJzYnJAKWeRdQwm2nAYd8kxMnGJLSpqTJgso_aw@mail.gmail.com \
--to=bdarcus@gmail.com \
--cc=alessandro.bertulli96@gmail.com \
--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).