From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: re-scanning bibliography for org-cite
Date: Tue, 24 May 2022 13:30:05 +0100 [thread overview]
Message-ID: <87ilpvi04y.fsf@ucl.ac.uk> (raw)
In-Reply-To: <877ddptdkf.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Wed, 03 Nov 2021 17:21:36 +0100")
On Wednesday, 3 Nov 2021 at 17:21, Nicolas Goaziou wrote:
> 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.
Hi Nicolas,
sorry to revisit this but I continue to run into the problem of the
bibliography not being rescanned automatically. What is the easiest way
(other than leaving Emacs and restarting) to force it, assuming there is
one? I.e. maybe I can invalidate or clear the cache?
I do not know why rescanning doesn't happen. It usually does but then
sometimes it doesn't without any noticeable difference in the actions I
have taken. Frustrating.
I hate restarting Emacs... ;-)
Thank you,
eric
--
: Eric S Fraga, with org release_9.5.3-511-g8e69ad in Emacs 29.0.50
next prev parent reply other threads:[~2022-05-24 12:37 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
2021-11-03 16:34 ` Bruce D'Arcus
2022-05-24 12:30 ` Eric S Fraga [this message]
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=87ilpvi04y.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).