emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Henrik Frisk <frisk.h@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: org-cite and org-ref-cite
Date: Sun, 27 Feb 2022 10:38:37 +0100	[thread overview]
Message-ID: <CAO0LSb6cKnHw0694LMjmQw4_JFz4caqr8trkjbu=Tp3gSOTpBw@mail.gmail.com> (raw)
In-Reply-To: <CAJ51ETqPfaQvGkxh6LgRQH661t_ZCVGEqGrfOz8Pic6ejC3iUw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 752 bytes --]

Den lör 26 feb. 2022 kl 16:11 skrev John Kitchin <jkitchin@andrew.cmu.edu>:

> I would not recommend org-ref-cite (
> https://github.com/jkitchin/org-ref-cite). It was an early approach to
> trying to integrate org-ref with oc-cite. As far as I know, it worked fine
> for that, and was pretty complete for citations, but I have abandoned this
> approach and archived the repo. If anyone would like to take over this repo
> I would be happy to transfer it.
> If you are looking for something above and beyond the default oc-cite
> capabilities, https://github.com/bdarcus/citar is probably a better
> choice than org-ref-cite as it is actively developed.
I see. Didn't realize that. I will look into citar then, thanks!


[-- Attachment #2: Type: text/html, Size: 1285 bytes --]

  reply	other threads:[~2022-02-27  9:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25  7:50 org-cite and org-ref-cite Henrik Frisk
2022-02-25  8:27 ` Nicolas Goaziou
2022-02-25 12:56 ` Eric S Fraga
2022-02-26 13:40   ` Henrik Frisk
2022-02-26 15:11     ` John Kitchin
2022-02-27  9:38       ` Henrik Frisk [this message]
2022-03-03  8:58         ` Eric S Fraga

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:

  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='CAO0LSb6cKnHw0694LMjmQw4_JFz4caqr8trkjbu=Tp3gSOTpBw@mail.gmail.com' \
    --to=frisk.h@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \


* 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


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).