I don't have a super specific suggestion ATM, but will just make the following observation:
John Kitchin and I have been working on respective processors, and they are modular enough that: 1) one can mix-and-match across projects 2) one can customize within each follow processor; for org-ref-cite, you can extend its hydra-based follow UI using hydra+, and for bibtex-actions you can write and use your own keymap to tell embark which commands to use for it's menu. Upshot: a function that takes a key (or list of keys, as with bibtex-completion, which is what I use behind-the-scenes) is the starting point for a basic single action follow processor. But it should be easily incorporated into more feature-full UIs. On Mon, Aug 9, 2021 at 6:45 AM Joost Kremers <joostkrem...@fastmail.fm> wrote: > > Hi Thomas & others, > > On Sat, Aug 07 2021, Thomas S. Dye wrote: > > Aloha Joost, > > > > Following some pointers from Eric and Bruce I have this in my > > configuration and it seems to work fine, though I haven't had a chance > > to use it very much. > > Thanks for figuring that out. :-) Once I get to implementing support, I'll use > it as a starting point. There should also be a way to open the correct file > automatically, without the user having to select it. > > > > -- > Joost Kremers > Life has its moments
