From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: New Citation syntax on the master branch? Date: Sun, 17 May 2015 10:18:36 +0200 Message-ID: <87wq078vmr.fsf@nicolasgoaziou.fr> References: <871tioj456.fsf@nicolasgoaziou.fr> <554F0848.3030508@gmail.com> <87h9rgn3jv.fsf@nicolasgoaziou.fr> <5558E723.20800@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52659) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yttl3-0007EC-CA for emacs-orgmode@gnu.org; Sun, 17 May 2015 04:17:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yttl2-0002el-HA for emacs-orgmode@gnu.org; Sun, 17 May 2015 04:17:13 -0400 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:51483) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yttl2-0002eT-B1 for emacs-orgmode@gnu.org; Sun, 17 May 2015 04:17:12 -0400 In-Reply-To: <5558E723.20800@gmail.com> (Vaidheeswaran C.'s message of "Mon, 18 May 2015 00:38:19 +0530") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Vaidheeswaran C Cc: emacs-orgmode@gnu.org Vaidheeswaran C writes: > 1. "New citation syntax" is concerned with ORG SYNTAX > > 2. oc.el is concerned with EDITING org files. > > 3. ox-jabref.el (and others) is concerned with DOCUMENT CREATION. True. > It seems like your plan is to put 1, 2 & 3 ALL TOGETHER in > trunk. i.e., ALL or NONE. Correct. Org syntax is expected to be supported out of the box. > How about making (1) a configurable option -- disabled by default -- > and moving it to trunk? I don't want syntax to be configurable. > I believe the answer depends MORE on how "stable" you think the new > citation syntax is (in so far as it is implemented) and LESS on > whether the whole ecosystem is in place. We can add oc-jabref (not ox-jabref, which is reserved for export back-ends) in a branch and have some users test it. This is the only way to know if the syntax is sufficient. WDYT? Regards,