Closed bdarcus closed 2 years ago
John says of org-ref-cite
:
I rewrote the hydra code which should address this. You can use `defhydra+' to extend a hydra.
FYI, I reverted the comment commit here, so it's just removing the hard dependency on org-ref.
Org-ref v3 removes the ivy and helm dependencies, so it less problematic to require in orb.
I'll close this then.
I don't think this pr should be closed.
We should based on the fact that if we can use this package without org-ref
, then org-ref
is not a hard dependency of org-roam-biblatex
, and should be moved to the soft dependencies (maybe add citar
as well) and let the user to choose which package to use.
There are some jobs to be done to make all the functions work with citar
, eg. orb-note-actions
, but in my use cases, it just works good enough, as I mainly use the orb-edit-note
.
I don't think this pr should be closed.
Yeah, I guess I agree :-)
In related news, I removed the bibtex-completion dependency from citar in the past few days.
This has been fixed in 948ff0922237f78070ab4c9062a4376f00dfa0a5.
I decided to open this as a draft PR. It includes two commits ATM; to:
org-ref
inpackage-requires with
org-mode "9.5"` (though maybe better to just remove it?)I was thinking could be a basis of discussion, and I could drop the second commit if you wanted to remove the
org-ref
requirement in the meantime.Follow processors?
The most interesting question is WTD about a possible follow processor, which is the UI that would integrate with
org-open-at-point
.EDIT: actually, there are two questions; whether to do one (or more), and for what targets? I was assuming citations here, but could also be note links or some such.
For sure you could do an ORB one.
But I wonder if we could find a way to have your action extension capability available in other obvious follow processors:
bibtex-actions
has one forembark-act
org-ref-cite
has a hydrahelm-bibtex
, I believe using helm actionsFor 1, I have an embark "target-finder" for org-cite citations and citation-references, so I am pretty sure all that is required is to write your own keymap and register that with embark.
That should expose the commands in
embark-act
, along with any other commands registered with thatoc-citation
category.For 2, see https://github.com/jkitchin/org-ref-cite/issues/4.