emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: New Citation syntax on the master branch?
Date: Sun, 17 May 2015 10:18:36 +0200	[thread overview]
Message-ID: <87wq078vmr.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <5558E723.20800@gmail.com> (Vaidheeswaran C.'s message of "Mon, 18 May 2015 00:38:19 +0530")

Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com> 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,

  reply	other threads:[~2015-05-17  8:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-10  7:00 New Citation syntax on the master branch? Vaidheeswaran C
2015-05-10  7:14 ` Nicolas Goaziou
2015-05-10  7:27   ` Vaidheeswaran C
2015-05-13 11:02     ` Nicolas Goaziou
2015-05-17 19:08       ` Vaidheeswaran C
2015-05-17  8:18         ` Nicolas Goaziou [this message]
2015-05-17 20:46           ` Vaidheeswaran C
2015-05-17  9:37             ` Rasmus
2015-05-20  6:23               ` Bastien

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=87wq078vmr.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=vaidheeswaran.chinnaraju@gmail.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).