From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: tumashu <tumashu@163.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
"Simonyi András" <andras.simonyi@gmail.com>,
"John Kitchin" <jkitchin@andrew.cmu.edu>
Subject: Re: Should wip-cite branch be merged to master?
Date: Sat, 21 Apr 2018 09:26:27 +0200 [thread overview]
Message-ID: <871sf9f2ak.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <29b94436.a1e.162e54aa7c1.Coremail.tumashu@163.com> (tumashu@163.com's message of "Sat, 21 Apr 2018 07:01:37 +0800 (CST)")
Hello,
tumashu <tumashu@163.com> writes:
> There is a package which support wip-cite: https://github.com/andras-simonyi/citeproc-org, should wip-cite branch
> be merged to master now?
Merging wip-cite branch with master, and integration of citeproc-org
into Org core, could be discussed with the author of the library, and,
of course, with anyone interested in using the @cite syntax. For
example, I need to know if that syntax, along with citeproc-org, covers
enough use-cases for citations, if it brings more value than using,
e.g., Org Ref, which already exists, how it could be improved, etc.
I also remember that Christian Moe suggested an alternate syntax for
citations. He might want to point out what is missing from @cite syntax
and if he still prefers his idea.
I have the feeling that it is a bit early for Org 9.2. Anyway, I'm
Cc'ing András and John for their opinion about it. I'd love to hear from
everyone involved in the last round of discussion about the subject,
too.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-04-21 7:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 23:01 Should wip-cite branch be merged to master? tumashu
2018-04-21 7:26 ` Nicolas Goaziou [this message]
2018-04-21 8:43 ` Christian Moe
2018-04-22 18:17 ` András Simonyi
2018-04-23 19:42 ` John Kitchin
2018-04-25 19:19 ` Richard Lawrence
2018-04-26 23:34 ` Bastien
2018-04-27 21:07 ` András Simonyi
2018-04-27 23:34 ` Nicolas Goaziou
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=871sf9f2ak.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=andras.simonyi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=tumashu@163.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).