From: John Kitchin <jkitchin@andrew.cmu.edu>
To: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: org-ref update
Date: Mon, 16 Mar 2015 20:20:49 -0400 [thread overview]
Message-ID: <m2k2yg1nku.fsf@andrew.cmu.edu> (raw)
Hi all,
The org-ref code is finally all in emacs-lisp! This should make it much
easier to install, and is another step closer to getting org-ref into
MELPA.
The code can be found at https://github.com/jkitchin/org-ref
There are some relatively new features in org-ref if you have not been
following the bleed edge:
- New colored org-ref links to differentiate them from other
org-links. Citations are greenish, refs and labels are maroonish.
- Context messages about links. With your cursor on a cite, ref or label
link you will get a context message, e.g. a formatted citation, some
context about the label a ref refers to, or a count of the labels in
the mini-buffer.
- There is now an org-ref menu in the Org menu.
- There is a new org-ref-help function that opens an org-file of org-ref
documentation.
- Pretty thorough integration of helm throughout org-ref, and some
integration of hydra.
- A few utility libraries: doi-utils, isbn, wos, pubmed, arxiv,
jmax-bibtex, sci-id, x2bib. Not all these are new, but if you didn't
know about them, check them out.
- Cask integration. This mostly provides access to testing and
dependencies right now. org-ref is also now tested continuously at
https://travis-ci.org/jkitchin/org-ref (although, there are no tests of
substance yet, it at least checks that you can load it ;).
Read more at:
http://kitchingroup.cheme.cmu.edu/blog/2015/03/16/Update-on-org-ref-it-is-now-all-emacs-lisp/
--
Professor John Kitchin
Department of Chemical Engineering
Carnegie Mellon University
@johnkitchin
http://kitchingroup.cheme.cmu.edu
reply other threads:[~2015-03-17 0:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m2k2yg1nku.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.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).