From: Nicolas Goaziou <email@example.com>
To: Emmanuel Charpentier <firstname.lastname@example.org>
Cc: emacs-orgmode <email@example.com>
Subject: Re: [wip-cite-new] Where is the development branch ?
Date: Sat, 26 Jun 2021 10:35:06 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Emmanuel Charpentier's message of "Sat, 26 Jun 2021 09:50:16 +0200")
Emmanuel Charpentier <firstname.lastname@example.org> writes:
> I wanted to test the (new|future) citation abilities of =Org= ; I
> tested what is available in =citeproc-org= with the =org-ref} syntax
> the latter supports.
> However, I also wanted to test what is available with the "new" syntax
> planned for introduction in =Org=.
> According to
> , this is only available on the =wip-cite= development branch.>
> However, my freshly updated git clone
> (of https://code.orgmode.org/bzg/org-mode.git ) doesn't have such a
The branch is "wip-cite-new".
> Where should I get this code ?
For example, here:
> Related question : is there an ETA of these new abilities in =Org= ?
I would appreciate some alpha-testing first, but I would say the code is
already good enough for inclusion at this point. I.e., there are
a couple of points open for discussion, but no blocker.
Please let me know how it goes!
next prev parent reply other threads:[~2021-06-26 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 7:50 [wip-cite-new] Where is the development branch ? Emmanuel Charpentier
2021-06-26 8:35 ` Nicolas Goaziou [this message]
2021-06-26 11:39 ` Emmanuel Charpentier
2021-06-28 11:06 ` Eric S Fraga
2021-06-28 12:09 ` Bruce D'Arcus
2021-06-28 12:22 ` Eric S Fraga
2021-06-28 12:26 ` Bruce D'Arcus
2021-06-28 12:56 ` Eric S Fraga
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 \
* 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).