From: John Kitchin <jkitchin@andrew.cmu.edu>
To: "Clément B." <clement@inventati.org>
Cc: julian@hafro.is, emacs-orgmode <emacs-orgmode@gnu.org>,
Leonard Randall <leonard.a.randall@gmail.com>,
Ken Mankoff <mankoff@gmail.com>, "Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: State of the art in citations
Date: Sun, 27 Apr 2014 15:20:15 -0400 [thread overview]
Message-ID: <CAJ51ETrdObn7v3LN_FLTAcRXeKMWyiTF23zAV+JVPtDbhtnh-A@mail.gmail.com> (raw)
In-Reply-To: <87fvkyogm4.fsf@gaillac.origami>
[-- Attachment #1: Type: text/plain, Size: 3987 bytes --]
It seems there are a lot of variants of citation handling out there! I will
add to the list my own variants here:
https://github.com/jkitchin/jmax/blob/master/jorg-bib.el. My citation needs
are simple, I basically only use \cite{key1,key2} in LaTeX. And I only use
bibtex, because I have not gotten around to anything else, bibtex works
fine if your needs are simple (like mine).
There is certainly duplication of some things, but the following are
features in mine that I am not aware of anywhere else.
1. Integration with reftex. You type C-c ] and select keys from reftex and
insert a cite link. If you type it again on a citation, the new entries are
appended to the end. This current conversation inspired me to implement
this!
2. Clickable cite links. If you have a citation link like
cite:key1,key2,key3 you can click on key1 and open the bibliography file to
key1, and you can click on key2 and have it open at key 2. This link would
export in latex as \cite{key1,key2,key3}. Other cite formats, e.g. citep,
citep*, etc... are defined too, but are relatively untested. You can also
use completion to enter a bibtex key.
3. citation tooltips. If clicking is too disruptive, you can run a command
and get a tooltip of the citation under point. If clicking is too tiring,
you can turn on an idle timer that shows a tooltip if the cursor is on a
citation.
4. clickable label links. clicking checks the buffer for another label by
the same name.
5. Clickable ref links. Clicking on the ref:label takes you to the label,
and provides C-c & to get back to that point. You can also use completion
to get a list of labels in the buffer to make a ref to.
6. A bibliographystyle and bibliography link. The bibliography link opens
the bibtex file that was clicked on.
7. Code to make a clickable list of figures and tables.
8. Code to extract the bibtex entries cited in an org-file to a text block
at the end of the org-file
9. variables to point to a notes file and pdf directory, and functions to
jump to your notes and the pdf file from a bibtex entry.
10. a function to build a complete pdf bibliography from your bibtex file.
This is handy for checking the entries are spelled correctly, etc...
11. A little function and python script to upload a bibtex entry to
citeulike.
I have not tried to do much with anything but LaTeX, so these links are not
likely to be that good for html or odt I suspect.
Anyway, there are some very interesting ideas in this code, and I am using
it on a pretty regular basis. Maybe some of you would also find them
interesting/helpful. I look forward to see this continue developing!
John
-----------------------------------
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Sun, Apr 27, 2014 at 12:57 PM, Clément B. <clement@inventati.org> wrote:
>
> > It appears to work for multicite for me. Or at least well enough. If I
> > select multiple entries, I get this:
> >
> > [[ref:Author1:YYYY,Author2:YYYY,Author3:YYYY][()]]
> >
> > I can then easily insert the text I want into the (). It exports
> > properly to LaTeX as \cite{Author1:YYYY,Author2:YYYY,Author3:YYYY}.
> >
> > Maybe most people multi-cite more than me, but I think it is only a bit
> > of extra work to add what I want in the () and then it exports properly
> > to LaTeX and, using the references-via-LaTeX, to ODT/HTML too!
> >
> > -k.
>
> The problem is that you can't link to a bibtex entry,
> [[ref:Author1:YYYY,Author2:YYYY]] is not picked up by org search
> function of `org-open-file`. And even if it was, it couldn't link
> to several entries at once. So to preserve the ability to jump
> quickly to a reference, I quite like the export filter approach,
> which I was unaware of (thank you Thomas! ).
>
>
> Clément
>
>
[-- Attachment #2: Type: text/html, Size: 4815 bytes --]
next prev parent reply other threads:[~2014-04-27 19:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 16:56 State of the art in citations 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 [this message]
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
-- 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 18:26 Clément B.
2014-04-28 1:53 ` Richard Lawrence
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ51ETrdObn7v3LN_FLTAcRXeKMWyiTF23zAV+JVPtDbhtnh-A@mail.gmail.com \
--to=jkitchin@andrew.cmu.edu \
--cc=clement@inventati.org \
--cc=emacs-orgmode@gnu.org \
--cc=julian@hafro.is \
--cc=leonard.a.randall@gmail.com \
--cc=mankoff@gmail.com \
--cc=tsd@tsdye.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.