From: "Bruce D'Arcus" <firstname.lastname@example.org>
To: "Thomas S. Dye" <email@example.com>
Cc: org-mode-email <firstname.lastname@example.org>,
John Kitchin <email@example.com>
Subject: Re: should a BIBLIOGRAPHY keyword supercede org-cite-global-bibliography?
Date: Mon, 19 Jul 2021 21:42:38 -0400 [thread overview]
Message-ID: <CAF-FPGMKXMF7tVXebuGmYU5RTNH-E2pxrbH=nZLBNb-T=SsDCg@mail.gmail.com> (raw)
As Emmenuel pointed out, we missed that Nicolas already thought of
this, and you can do this:
With that, there's no problem, and lots of flexibility.
On Mon, Jul 19, 2021 at 8:53 PM Thomas S. Dye <firstname.lastname@example.org> wrote:
> I used to have a global bibliography that my employees all used.
> Every project also had a local bibliography for citations that
> didn't appear in the global bibliography. At the end of a
> project, after the editor had cleaned up the local bibliography,
> I'd merge it with the global bibliography using a utility called
> Vikas Rawal <email@example.com> writes:
> >> It seems like that should not be the case, i.e. if you define
> >> BIBLIOGRAPHY
> >> keywords it means you do not want to use the ones
> >> in org-cite-global-bibliography. Is there a scenario where the
> >> union of those
> >> makes sense?
> > I second this. The local bibliographies should supercede the
> > global.
> > Vikas
> Thomas S. Dye
next prev parent reply other threads:[~2021-07-20 1:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 16:07 should a BIBLIOGRAPHY keyword supercede org-cite-global-bibliography? John Kitchin
2021-07-19 16:18 ` Bruce D'Arcus
2021-07-20 0:01 ` Vikas Rawal
2021-07-20 0:52 ` Thomas S. Dye
2021-07-20 1:42 ` Bruce D'Arcus [this message]
2021-07-20 8:03 ` Eric S Fraga
2021-07-19 17:29 CHARPENTIER Emmanuel via General discussions about Org-mode.
2021-07-19 17:40 ` Bruce D'Arcus
2021-07-19 17:54 ` John Kitchin
2021-07-19 18:06 ` Bruce D'Arcus
2021-07-19 18:07 ` CHARPENTIER Emmanuel via General discussions about Org-mode.
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).