From: Christian Moe <mail@christianmoe.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [ANN] org-bibtex.el --- convert between Org headings and bibtex entries
Date: Wed, 20 Apr 2011 11:26:56 +0200 [thread overview]
Message-ID: <4DAEA6E0.7040103@christianmoe.com> (raw)
In-Reply-To: <87y6357q81.fsf@gmail.com>
Cool! Thanks for this. I understand the Fireforg project provides part
of this functionality (integrated with Zotero), but this free-standing
tool looks helpful. Three quick comments:
- I tried to just put this on my load path and require it, but there
seems to be a name conflict with the existing org-bibtex.el, which
provides for BibTeX links.
- Trying to create a book type entry, I get prompted only for
`:editor', not for `:author'.
- Fireforg namespaces the property names with a `BIB_', e.g.
`:BIB_author:', and some people might find that useful as an option.
- I'd find it helpful with a user option for org-bibtex-fleshout to
prompt for optional fields as well.
Yours,
Christian
On 4/20/11 1:52 AM, Eric Schulte wrote:
> Hi,
>
> 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
>
> Cheers -- Eric
>
next prev parent reply other threads:[~2011-04-20 9:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 23:52 [ANN] org-bibtex.el --- convert between Org headings and bibtex entries Eric Schulte
2011-04-20 1:01 ` Jeff Horn
2011-04-20 1:13 ` Eric Schulte
2011-04-20 7:54 ` Thomas S. Dye
2011-04-20 13:25 ` Matt Lundin
2011-04-20 14:29 ` Matt Lundin
2011-04-20 19:59 ` Eric Schulte
2011-04-20 19:00 ` Eric Schulte
2011-04-21 16:36 ` Thomas S. Dye
2011-04-21 21:06 ` Eric Schulte
2011-04-23 16:23 ` Thomas S. Dye
2011-04-23 22:59 ` Alan E. Davis
2011-04-24 0:40 ` Matt Lundin
2011-04-24 14:21 ` Eric Schulte
2011-04-24 16:53 ` Christian Moe
2011-04-25 13:19 ` Matt Lundin
2011-04-25 13:34 ` Eric Schulte
2011-04-25 15:15 ` Matt Lundin
2011-04-27 22:16 ` Eric Schulte
2011-04-24 0:52 ` Eric Schulte
2011-04-24 4:49 ` Alan E. Davis
2011-04-24 14:29 ` Eric Schulte
2011-04-24 20:40 ` Alan E. Davis
2011-04-25 13:31 ` Eric Schulte
2011-04-20 9:26 ` Christian Moe [this message]
2011-04-20 20:15 ` Eric Schulte
2011-04-20 12:10 ` Matt Lundin
2011-04-20 20:16 ` Eric Schulte
2011-04-22 14:05 ` [PATCH] " Eric Schulte
2011-04-22 15:45 ` Matt Lundin
2011-04-23 0:03 ` Matt Lundin
2011-04-23 14:07 ` Eric Schulte
2011-04-23 22:46 ` Matt Lundin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DAEA6E0.7040103@christianmoe.com \
--to=mail@christianmoe.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).