From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Subject: Re: State of the art in citations
Date: Sun, 27 Apr 2014 18:53:29 -0700 [thread overview]
Message-ID: <87lhuqqkx2.fsf@berkeley.edu> (raw)
In-Reply-To: 87oazondzo.fsf@gaillac.origami
Hi Clément and all,
Clément B. <clement@autistici.org> writes:
> As for citations, I find that the most flexible way is to define
> my own link types, that allows control on both org formatting and
> export...
Replacing my inline \cite commands with custom link types is something
I've been meaning to do for a while. Thanks for the implementation
ideas!
I have a setup that for some people may complement the one Clément
describes. Rather than dealing with .bib files and RefTeX, I represent
my bibliography in Org, and use org-bibtex to (re-)generate a .bib file
as needed. Here's how it works, in brief; I described it more fully at:
http://article.gmane.org/gmane.emacs.orgmode/79016/
1) I store each reading as a TODO headline using a capture template. I
use the post-capture hook to call org-bibtex-create-in-current-entry as
appropriate. This allows me to keep notes, links, deadlines
etc. associated with each reading in Org, as well as the bibliographic
data.
2) I have a function that uses org-map-entries to walk over the
headlines for my readings and export them to a .bib file. This
regenerates my .bib file on an as-needed basis; the real bibliographic
database is stored in Org. (I call this function from a Makefile, but
it could just as easily be used from within the Org export process.)
The next step, which I haven't yet implemented but which would connect
this setup to one like Clément described, would be to add behavior to
the custom link types so that *following* the link would jump to the
associated TODO entry for the reading, rather than the entry in the .bib
file. This should be straightforward, since org-bibtex uses the
CUSTOM_ID property to store the cite key. And jumping to my own notes
about a reference (which might further link to the original text),
rather than to a .bib file, is usually what I want.
--
Best,
Richard
next prev parent reply other threads:[~2014-04-28 1:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 18:26 State of the art in citations Clément B.
2014-04-28 1:53 ` Richard Lawrence [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-27 14:53 Clément B.
2014-04-27 15:26 ` Ken Mankoff
2014-04-27 16:05 ` Clément B.
2014-04-27 16:10 ` Ken Mankoff
2014-04-26 16:56 Clément B.
2014-04-27 13:08 ` Leonard Randall
2014-04-27 14:14 ` Clément B.
2014-04-27 14:41 ` Ken Mankoff
2014-04-27 16:01 ` Thomas S. Dye
2014-04-27 16:16 ` Ken Mankoff
2014-04-27 16:57 ` Clément B.
2014-04-27 19:20 ` John Kitchin
2014-04-27 21:30 ` Clément B.
2014-04-28 13:57 ` Julian M. Burgos
2014-04-28 13:56 ` Julian M. Burgos
2014-04-29 9:30 ` Vikas Rawal Lists
2014-04-29 15:36 ` Richard Lawrence
2014-04-29 9:30 ` Vikas Rawal Lists
2014-04-25 12:11 Julian M. Burgos
2014-04-25 15:42 ` Grant Rettke
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=87lhuqqkx2.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.edu \
--cc=emacs-orgmode@gnu.org \
/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).