Daniel Mendler

@tmalsburg Okay, I see. I expected from the name bibtex-completion that it provides basic completion support and I saw completing-read calls in the code base - therefore I made this...

@mtreca My intention was not to take this away from you. I only wanted to provide some details regarding the implementation of Selectrum, Marginalia and Embark. Please continue with your...

> I'm sure that the infrastructure in bibtex-completion could be used also for other types of completion frameworks with different UI assumptions but I think it would probably be non-trivial...

@bdarcus Selectrify turns the bibtex functions into proper commands which is needed for Embark. See my comment above https://github.com/tmalsburg/helm-bibtex/issues/353#issuecomment-766856371. But maybe the name should rather be embarkify ;) Instead of...

@bdarcus Yes something like this, but there is a typo in this embark-bibtex function. It should just use plain `completing-read`. About the embarkify actions, would it make sense to write...

> These functions only perform actions on entries when you've already selected an entry. So they do not have any searching and selecting capabilities themselves. Yes. But if interactive specifications...

@tmalsburg > bitbex you can apply an action to multiple entries in one go, you can apply multiple actions on one entry, and you can apply multiple actions to multiple...

CC @oantolin, who is the author of the Embark package. Note that I am only the coauthor of Marginalia and Consult, so maybe I cannot convey the motivation for Embark...

I agree that it is the best approach to first make this work separately as the first step! And yes, changing the API of the action functions would only make...

> The current version works, but is synchronous completely. It should be possible to add some degree of asynchronicity using timers. There's also the async package, but I'm not sure...