search

jkitchin / org-ref

org-mode modules for citations, cross-references, bibliographies in org-mode and useful bibtex tools to go with it.
GNU General Public License v3.0
1.37k stars 243 forks source link

(re)loading and setting bibliography takes too long #967

Open novusshu opened 2 years ago

novusshu commented 2 years ago

Now I updated to Version 3. Every time I open an org file with bibliography, the "(re)loading bibliography" takes at least 10-15 seconds, while in the past it was only 2-3 seconds. I tried with the code provided in this issue https://github.com/jkitchin/org-ref/issues/928, but it didn't help much.

More, the bibliography: and biliographystyle: lines (for setting the bib file and style) are almost impossible to edit. It takes another 10-15 seconds if I want to kill or add a single letter and this is excruciating! Has anyone experienced the same issue and is there a fix?

Thank you very much!!!

jkitchin commented 2 years ago

Can you run M-x org-ref in that org-file and put the output here?

I don't see any thing that extreme on those lines. There is some room to improve it though. I pushed a small improvement on bibliographystyles that should only be slow on the first edit, but after that should be faster.

novusshu commented 2 years ago

Below is the output as you instructed: funcall-interactively: Wrong type argument: listp, #<marker at 20520 in main.org

The strange thing is my problem seemed gone as of now (no lag whatsoever, and I don't even see a "(re)loading bibliography" message even in a new file), but I haven't updated any package yet. The only thing changed is the updated .bib file (I use Zotero to auto-update it).

jkitchin commented 2 years ago

hm. that is pretty odd, I don't see an error like that on my end. Do you get that error in every org file or just this one?

novusshu commented 2 years ago

Yeah it's quite strange. The org-ref report can be generated normally in an org file that does not have the bibliography or bibliographystyle lines. Any file with these lines can only result in the same error and an empty report with a "bad files" entry.