-
Notifications
You must be signed in to change notification settings - Fork 54
Configuration
Bibtex-completion automatically reloads your library if the bib files change.
Bibtex-actions does not, in part because of the complexity, and in part to give users more flexibility (see this discussion for more).
If you want to add this, you can simply add this to your config:
(file-notify-add-watch bibtex-completion-bibliography
'(change)
(lambda (event) (bibtex-actionss--reload-candidates-cache)))
If you want to expand this to doing the same for PDFs in your PDF directory, you can add something like this (also, see that issue for why this is difficult to include in bibtex-completion) to your config (untested ATM, and contingent on merging PR 71):
(file-notify-add-watch bibtex-completion-library-path
'(change)
(lambda (event) (bibtex-actionss--reload-candidates-cache)))
... and for notes, say in the context of an org-roam-bibtex setup:
(file-notify-add-watch bibtex-completion-note-path
'(change)
(lambda (event) (bibtex-actionss--reload-candidates-cache)))
(setq bibtex-actions-display-template
'((t . "${=has-pdf=:1} ${=has-note=:1} ${author:24} ${title:64} ${year:4}")))
TODO
TODO
Bind the keymap to embark-act
like so:
(add-to-list 'embark-keymap-alist '(bibtex . bibtex-actions-map))
You have, again, options.
You can setup the default prompter per the embark README.
This commit also adds an option to use prefix completion.
This variable will configure which-key to sort the bindings so the bibtex-action ones are grouped first.
(setq which-key-sort-order 'which-key-description-order)
For marking candidates in the embark-collect
buffer.
TODO Still need code to bind this to embark.
This allows you to bypass the embark-act
command and invoke actions directly within a collect buffer.