Roshan Shariff

An alternative way to accomplish this is to allow the entries in `embark-keymap-alist` to be functions returning keymaps rather than just symbols whose value is a keymap. Maybe that function...

> But in terms of overall complexity it may come close or even exceed such a functionality which builds keymaps dynamically. Yeah, I don't think it'll be common to build...

Sure, I'll work to separate them out into separate PRs when I have some time. Perhaps the logical breakdown would be: (1) applying faces to the header line; (2) fallback...

Ah, I see we have the [unescape functionality](https://github.com/emacs-citar/citar/blob/24a800be6494cd0c3eac3068a43c4ffcf13d08ea/citar-file.el#L120) in `citar-file--parser-triplet` but not in `citar-file--parser-default`. I'll write up a PR to handle unescaping for both parsers. Thanks for investigating, @CVanmarcke!

I'm not sure Zotero can do anything else. They have to escape at least closing braces (for BibTeX fields) and separator characters (`;`), and then also escape the backslashes used...

I'm looking deeper into the file field parsing as part of the new cache design (#634). I've looked at the file fields produced by different programs: * Zotero with Better...

I like the idea of making the default parser more robust, but requiring users to add more `citar-file-parser-functions` to handle oddball formats.

I think `citar-capf` is going to need some more extensive changes. Currently it just saves the active bibliographies whenever `citar-capf` is loaded and then never updates them. But we also...

@mclerc, I'll have to look into what's causing this, since in my testing a bibliography file of that size took much less time. Would you be willing to share your...

Sorry, I was out of the loop for a bit. Thanks @aikrahguzar for digging into this more! That would explain why I couldn't initially reproduce the slowdown; my `parsebib` was...