From: Edgar Lux <edgarlux@mailfence.com>
To: emacs-orgmode@gnu.org
Subject: Re: Patch for \usepackage[ ... natbib = true ...]{...biblatex} with org-cite
Date: Sun, 22 Jan 2023 20:47:07 +0100 (CET) [thread overview]
Message-ID: <519613720.1048241.1674416827126@fidget.co-bxl> (raw)
In-Reply-To: <CAOWRwxDs2=c0G1tVAE3mRrDRb1wZDvrgQEWPYqt7o0QgC76Z7w@mail.gmail.com>
January 22, 2023 at 12:36:32 PM CET "András Simonyi" <andras.simonyi@gmail.com> wrote:Dear All,
> There is also the customizable variable `org-cite-biblatex-options' to
> pass additional options,
That is very useful, indeed (I didn't know how to use it). Hopefully the e-mail which I just sent helps with the documentation.
> which could be used with #bind+ if document-specific options are needed.
Just in case, I think that you meant #+bind: . However, it didn't work for me (I'm blaming myself). I added this in line 16 of my 324-lines file
#+bind: org-cite-biblatex-options "opt=true"
but the =opt=true= value is not shown next to =\usepackage{biblatex}= when I export. I do have =org-export-allow-bind-keywords= set to =t=
> best wishes,
> András
you too!
--
Sent with https://mailfence.com
Secure and private email
next prev parent reply other threads:[~2023-01-22 19:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 21:31 Patch for \usepackage[ ... natbib = true ...]{...biblatex} with org-cite Edgar Lux
2023-01-20 10:59 ` Ihor Radchenko
2023-01-20 16:57 ` Edgar Lux
2023-01-21 8:37 ` Ihor Radchenko
2023-01-21 20:25 ` Edgar Lux
2023-01-22 11:15 ` Ihor Radchenko
2023-01-22 11:36 ` András Simonyi
2023-01-22 19:47 ` Edgar Lux [this message]
2023-01-23 10:43 ` Ihor Radchenko
2023-01-22 19:19 ` Edgar Lux
2023-01-23 11:06 ` Ihor Radchenko
2023-01-23 20:58 ` Edgar Lux
2023-01-24 10:54 ` [BUG] #+cite_export: ... bibstyle citestyle cannot be universally used as global defaults (was: Patch for \usepackage[ ... natbib = true ...]{...biblatex} with org-cite) Ihor Radchenko
2023-02-03 9:33 ` Edgar Lux
2023-02-04 11:31 ` Ihor Radchenko
2023-02-04 23:14 ` Edgar Lux
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=519613720.1048241.1674416827126@fidget.co-bxl \
--to=edgarlux@mailfence.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).