From: Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: New Citation syntax on the master branch?
Date: Mon, 18 May 2015 02:16:02 +0530 [thread overview]
Message-ID: <5558FE0A.7050508@gmail.com> (raw)
In-Reply-To: <87wq078vmr.fsf@nicolasgoaziou.fr>
On Sunday 17 May 2015 01:48 PM, Nicolas Goaziou wrote:
>> How about making (1) a configurable option -- disabled by default --
>> > and moving it to trunk?
> I don't want syntax to be configurable.
Ok.
>> > 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?
I will rename the module as you suggest. I would also like to polish
a few more things. Unlike other contrib modules, I want this module
to be changed only by FSF-approved authors so that I can put it on GNU
ELPA.
(My future assignment is through, so the route is clear.)
----------------------------------------------------------------
While we are on this...
I would like to submit some patches to ox-odt.el. I have plenty of
local changes (that were made on a older version of trunk).
As part of preparation for submitting my changes to Org repo,
1. I have reverted patches applied to the trunk since my change.
2. Applied my patches to (1).
3. Re-play (1) on top of 3.
Since my dis-appearance couple of months ago, there have been more
changes to ox-odt.el (which I need to replay again).
Here is a snapshot of my workarea:
http://repo.or.cz/w/org-mode/org-cv.git/shortlog. Step (1) above
corresponds to this
commit.
(http://repo.or.cz/w/org-mode/org-cv.git/commit/739ddc3b27a5a2f0b05b576f671069c868835a21)
a) I haven't updated the ODT nodes of Info manual. I would prefer to
update the manual AFTER the merge of elisp code.
b) Bugs if any introduced by my merge are going to be minor and IMHO,
they could be taken up AFTER the merge.
I hope the above arrangement for merging my changes is agreeable to
the maintainers. (Let me know what you think)
This message is more of a heads-up. I will let you know once I am
done with (3). Meanwhile, I would encourage the current ODT exporter
users to try out my new private repo and report any issues.
next prev parent reply other threads:[~2015-05-17 8:44 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
2015-05-17 20:46 ` Vaidheeswaran C [this message]
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=5558FE0A.7050508@gmail.com \
--to=vaidheeswaran.chinnaraju@gmail.com \
--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).