Daniel Mendler

Great work! :+1: > Since embark is no entirely optional, I renamed the module and function prefixes to bibtex-actions My suggestion would be bibtex-completion. :laughing: (But everything should be working...

Well, did you use **bibtex** here? ~~~ elisp (add-to-list 'embark-keymap-alist '(bibtex . embark-bibtex-map)) ~~~ In the comment above by @mtreca he used **bib**, but the completion category specified in the...

Did you setup Embark properly with which-key? Embark uses which-key as menu. But you can also use a completing-read prompter. Please take a look at the Embark README.

Just FYI for the full setup I am using Selectrum(Icomplete-vertical) + Marginalia + Embark + Orderless(Prescient) + Which-key + Consult. In parens the alternatives. I am not sure if I...

For quick experiments regarding this PR just use emacs -Q + Embark(for actions) + Which-Key(for visual menu). And maybe set the completion styles to substring.

@mtreca > bibtex-actions (the name should be changed), which functions similarly to ivy-bibtex and helm-bibtex provided embark is enabled for bibtex actions. > Individual bibtex actions, which call completing-read on...

> The specific commands wouldn't be changing with the removal of the single entry point; right? They would not change. All I am saying is the following: I have a...

The next logical steps could be the following: 1. Add the interactive spec directly to all of the bibtex-completion actions. ~~~ elisp (interactive (list (cdr (assoc (bibtex-actions--read) (bibtex-actions--get-candidates))))) ~~~ I...

Let's see what @mtreca and @tmalsburg think about it. Maybe there is one thing which would be required to make this fair to helm and ivy users. The `bibtex--completions-read` function...

> In the rare occasions where I would need to call a bibtex-actions command that is not bound, do you think it makes more sense to call it from one...