Citar 1.0, citar-org-roam, Doom biblio update

> Emacs package to quickly find and act on bibliographic references, and edit org, markdown, and latex academic documents. Just an FYI that we've tagged v1.0, which is us concluding that [Citar](https://github.com/emacs-citar/citar) is basically feature-complete, and we're comfortable with the API and keeping it more stable (sorry for the recent breaking changes!). Along with some major recent internal (in particular cache) and API changes, we've separated the embark-related code into a new package and minor-mode: citar-embark. I highly recommend it. Note: we do have a [known performance issue](https://github.com/emacs-citar/citar/issues/659) apparent with large files that change frequently. The fix for this will mostly happen in [parsebib](https://github.com/joostkremers/parsebib/pull/25). Also, I've updated the Doom biblio module to incorporate these changes, and updated all of its packages. This remains the easiest path to have a working citar-oriented system; just turn on the biblio and vertico modules, and set some paths. The note API in 1.0 in turn enables a small integration extension: [citar-org-roam](https://github.com/emacs-citar/citar-org-roam). This is partly a demo and test of the new API, but should also be useful for users, and developers that might want to build on it. This still needs a bit of work before I submit it to MELPA; PRs welcome. Any questions?

For lazy people… Citar is an ”Emacs package to quickly find and act on bibliographic references, and edit org, markdown, and latex academic documents.”

I don't think that qualifies as being lazy - not on the part of the *readers* anyway. I think it's reasonable to expect clues in the post to what a little-known package does and why you might care, without having to follow links to find out if you have any interest in it. At least the homepage from the first link has a short description. Quite a lot of projects don't even manage that much. Quite a few commercial products even.

It's a fair point. I guess I was relying on the reddit preview (though it's only on mobile, I just realized; I've updated the main post to include it), which does include that description, and aiming this at people already familiar with the package.

Thank you so much for the org-roam support. I was looking for that so I don't miss org-ref!

Thank you so much, love the package so far ❤️. A definite improvement would be the managing of non-bibliographic tags (such as images and equation), that org-ref has but it's basically undocumented

That's something I don't think belongs in a bibliographic package. I prefer focused packages that can be easily integrated. Along those lines, I've experimented a bit with what a small package to handle cross-references might look like in [https://github.com/bdarcus/oxr](https://github.com/bdarcus/oxr) (really features like this belong in org itself), and though I guess he hasn't yet formally announced it, [org-glossary](https://github.com/tecosaur/org-glossary) is a pretty awesome (and much more comprehensive) approach to glossaries, indexes, etc.

Thanks, I'll have a look at it! 😃 (P.s., the integration of Citar with Vertico is a kind surprise)

I love Vertico :-) But, like Vertico (and other related recent packages), Citar just uses the `completing-read` API for completion, which is what provides the integration.

Hi, I've been using `consult-bibtex` with extra embark actions for opening the pdf with xournal++ and okular. Is there an easy way to add new action to open pdf with specific programs? Last time I tried I did not manage to do it.

>Is there an easy way to add new action to open pdf with specific programs? Yes; see the `citar-file-open-functions` defcustom. We recently added that to provide greater flexibility.

Thanks!

Didn’t know about this package before, and Reddit doesn’t show previews for me. Added this to my list of packages that might be useful if I have to publish something.

Hi there,Been using a loving citar for a while now. One quick question. How should I go about adding `#+filetags` automatically when I create a node? Previously I was using to :after advice on `citar-org-format-note-default,` but I don't think that works any longer.

Write your own `create` function, perhaps based on the default one in `citar-org-roam`?

I think that's the goal. I am currently looking through the nested function calls for \`citar-create-note\`. I will post back if I figure out where to add some custom code. I am currently just a little lost in call stack.

Just to update this subthread, we figured out an [easier solution](https://github.com/emacs-citar/citar/issues/711#issuecomment-1304907495): modify the `citar-org-roam-note-title-template` to include that additional content.

That was me :) Didn't mean to bombard you like that. Thanks again for your time and for kindly helping me find a solution that works! As a final followup, do you how I could have `org-roam-note-title-template` get its contents from a file? I am basically using it to create a page layout with different headings and properties, and it feels rather strange to write \``"${author} - ${title}\n#+filetags: :literature: \n* TODOs\n:PROPERTIES:\n:CATEGORY: ${author}\n:END:\n* Notes\n* Takeaways\n* Practices\n* Quotes\n* Thoughts"`\` in my config. I think I am looking for something like `insert-file-contents` but I'm not sure. I'd just like to be able to maintain a separate template file. Thank you!

Yes, I know it was you. I just posted that for the record, in case someone else comes across it later. I don't follow your question. What "contents", from which "file"? You mean you want the template in a separate file? If yes, I don't really know, but assume it's easy, and that `insert-file-contents` sounds promising.

That’s just what I mean, yes. I was initially unsuccessful with`insert-file-contents` but I did not spend more than a couple minutes trying. Thanks again 🙏🏽