Bruce D'Arcus

> OTOH, within the context of citar, it'd be logical to use the citar cache, so could also remain a citar module too. Right, but your activate processor already supports...

@andras-simonyi > Well, I was thinking of factoring this functionality out into a module somehow, A module for what? `oc-csl`? > but another alternative would be indeed to say that...

Just putting this [note](https://github.com/emacs-citar/citar/pull/651#issuecomment-1200772700) from Roshan here: > I did some preliminary investigation ... and on my (fairly old) computer I don't see the problem right away (loads that bibliography...

That might make sense @aikrahguzar. @joostkremers added that on June 16, so actually before we merged the cache update. Does that timing fit your experience @mclearc? Still, that doesn't explain...

I suppose one simple thing we could do is a shadow variable, that we use to let-bind the parsebib `defvar`, so we can: 1. Maybe restrict this to just a...

> given the resource-intensiveness, which I didn't think about before, it may actually make sense to make it an inclusion list. @bdarcus what do you think? I think probably yes...

FWIW, I've removed this from the 1.0 milestone, since I don't think this should hold us up from tagging 1.0. It seems most of the code changes will happen on...

The scenario where @mclearc was experiencing pain was when a very large file changes frequently, which will probably never exactly be fast (I still think we need #653 for that)....

> I think trying to do it on the fly is unlikely to work since we can't do is lazily just for the entries that are on the screen. FWIW,...

@minad > 3\. The bib is usually not modified that often and calling Citar functions may also not be the first thing you do, so preloading should work? Yes, unless...