From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Bruce D'Arcus" <bdarcus@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: re-scanning bibliography for org-cite
Date: Wed, 03 Nov 2021 17:21:36 +0100 [thread overview]
Message-ID: <877ddptdkf.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAF-FPGOLfL0L_niPrxdQFoN7C-AT1QewdUekFVyNi4CujumEOQ@mail.gmail.com> (Bruce D'Arcus's message of "Thu, 21 Oct 2021 11:30:38 -0400")
Hello,
"Bruce D'Arcus" <bdarcus@gmail.com> writes:
> On Thu, Oct 21, 2021 at 10:12 AM Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>>
>> Dear all,
>>
>> simple question: how can I get org-cite to rescan my bibliography (.bib)
>> file when it changes? When I'm writing a paper, as I'm doing now, I add
>> entries to my bibliography as I write but org-cite is not aware of any
>> new entries.
>
> Do you mean for org-cite-insert?
>
> Which insert processor?
>
> If it's bibtex-actions, you have to configure the filenotify support
> mentioned on the README.
>
> I'm not sure how the oc-basic one handles this.
oc-basic relies on a cache. The cache key contains a hash of the
contents of the bib file. So whenever the bib file is modified, the
cache is invalidated, and oc-basic parses again the file.
IOW, rescanning happens automatically in oc-basic.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2021-11-03 16:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 14:11 re-scanning bibliography for org-cite Eric S Fraga
2021-10-21 14:51 ` Uwe Brauer
2021-10-21 15:02 ` Eric S Fraga
2021-10-21 15:30 ` Bruce D'Arcus
2021-11-03 16:21 ` Nicolas Goaziou [this message]
2021-11-03 16:34 ` Bruce D'Arcus
2022-05-24 12:30 ` Eric S Fraga
2022-05-26 5:00 ` Ihor Radchenko
2022-05-26 9:39 ` Eric S Fraga
2022-05-26 10:24 ` Ihor Radchenko
2022-05-26 10:46 ` Eric S Fraga
2022-05-26 11:32 ` Timothy
2022-05-26 11:58 ` Ihor Radchenko
2022-06-09 12:23 ` Fraga, Eric
2022-06-09 14:34 ` Bruce D'Arcus
2022-06-09 16:00 ` Fraga, Eric
2022-06-09 16:51 ` Bruce D'Arcus
2022-07-04 16:45 ` 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=877ddptdkf.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=bdarcus@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).