You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Connector between Org-roam, BibTeX-completion, and Org-ref
whereas the documentation calls ORB PDF Scrapper an
Emacs interface to anystyle, an open-source software based on powerful machine-learning algorithms. It requires anystyle-cli, which can be installed with [sudo] gem install anystyle-cli
PDF Scrapper is an extra-feature, it has additional requirements and its documentation takes almost half of the space in the README. I belive it could safely be split into its own package.
This would provide clarity for just configuring ORB (as the user is required to read 1.984 words less) and also allow the PDF Scrapper to shine on its own.
Nevertheless, I also see some dangers:
It breaks the current ORB flow
The new package doesn't work together with ORB (or requires extra-steps to configure)
The new package does heavily require ORB (can't be used as stand-alone)
Development stops on either (as there are two packages to maintain)
The text was updated successfully, but these errors were encountered:
Good points! This will be the least priority, but conceptually, it is a stand-alone package. I believe the dangers can be mitigated by proper engineering. Currently, PDF Scrapper is indeed heavily dependent on ORB.
As mentioned in #140 (comment).
org-roam-bibtex
calls itself awhereas the documentation calls
ORB PDF Scrapper
anPDF Scrapper is an extra-feature, it has additional requirements and its documentation takes almost half of the space in the README. I belive it could safely be split into its own package.
This would provide clarity for just configuring ORB (as the user is required to read 1.984 words less) and also allow the PDF Scrapper to shine on its own.
Nevertheless, I also see some dangers:
The text was updated successfully, but these errors were encountered: