Hi Eric, "Eric Schulte" <schulte.e...@gmail.com> writes:
> Matt Lundin <m...@imapmail.org> writes: > >> "Eric Schulte" <schulte.e...@gmail.com> writes: >> >>> In an attempt to organize my reading notes, I've written the following >>> tool which allows both for exporting Org-mode headlines with bibtex >>> meta-data to bibtex entries, and for reading existing bibtex entries >>> into Org-mode headings. >>> >>> One nice feature of these functions is the ability to check that all >>> required fields are present in a given headline based on the bibtex type >>> (e.g., :article, :inproceedings), and prompt for missing fields. >>> >>> See the top of the elisp file for more usage information. >>> https://github.com/eschulte/org-bibtex/blob/master/org-bibtex.el >> >> Thanks for announcing this! One note: I believe the name conflicts with >> a core org-module (org-bibtex.el), which is used to store and open >> bibtex links. >> > > As one possible solution to this name conflict, I've folded my > org-bibtex.el into the existing org-bibtex.el in the Org-mode core. The > attached patch performs this integration adding the functionality in my > version of org-bibtex.el into the Org-mode core. > > Does this seem like an appropriate addition? +1 (or maybe +.75 -- see below) I think this could finally tempt me to move all my bibliographical data into org-mode files. (I've been keeping all my data in a central bibtex file and using reftex to generate links to citations.) My only reservation: modules such as org-bibtex.el, org-gnus.el, org-wl.el. (i.e., modules that contain the name of another emacs package) are conventionally reserved for hyperlinks. I have no idea whether this is a fixed convention, but we might want to ask Bastien or Carsten. I know the linking features would be untouched by the addition of this new functionality, but I wonder whether org <-> bibtex conversion occupies a distinct space. I can see now how the variables org-bibtex-types and org-bibtex-fields are a major improvement over bibtex-entry-field-alist, which contains a whole bunch of redundant field descriptions. This will make it much easier to configure my bibtex setup. Best, Matt
