From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id aLywArhu5mCZFgEAgWs5BA (envelope-from ) for ; Thu, 08 Jul 2021 05:19:20 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id aNIDOrdu5mB+fQAA1q6Kng (envelope-from ) for ; Thu, 08 Jul 2021 03:19:19 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 2758821013 for ; Thu, 8 Jul 2021 05:19:19 +0200 (CEST) Received: from localhost ([::1]:34990 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m1KZJ-0005PB-Nq for larch@yhetil.org; Wed, 07 Jul 2021 23:19:17 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:59772) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m1KYx-0005P3-EC for emacs-orgmode@gnu.org; Wed, 07 Jul 2021 23:18:55 -0400 Received: from mail-lf1-x12b.google.com ([2a00:1450:4864:20::12b]:38810) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1m1KYv-0008Cw-4h for emacs-orgmode@gnu.org; Wed, 07 Jul 2021 23:18:55 -0400 Received: by mail-lf1-x12b.google.com with SMTP id p16so10585836lfc.5 for ; Wed, 07 Jul 2021 20:18:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kfwd9hooSntDY3YIXSB7VXMmdNfLI3AcgWmTcrO9jE0=; b=N3TZ19ccht8h1q8kmixX4tBOsqBwr4A/AhBPWL0ZXnTrMZwtn3DYaqrv5NaGjk6D2h 3rYhC63/xC8YYRgHKbWfAGvgzhpnCGi5o85XM94ZT89Dbgt/JwtiuYDALssamZcvuNMb nJwAFXyLBmoilGDYGmbgcxa17/qaASr/2CV/ZkCzGJ/0uL7sz9adiqTMKcDXK5N5gaIv JuDh71oE93+61zHe9yJdfMFUQpsfcv7sGDJAYg4Oz9crY+bY+tqbCA0CS+Xm4BmTE2KM Xi9MX3vCQooW/N9yvMhnN7ZreOh6qAkT6GvmZ0vfJ3JX3ZxRWBcVkf974tzUBc6xQvYi WLNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kfwd9hooSntDY3YIXSB7VXMmdNfLI3AcgWmTcrO9jE0=; b=QAoMLune5cr2zhz3So025nybmIW1uQJiJM+L0Lgytg7d9BxE8U+ylUY2cvbzMLXjIx RP/RWSrosZ0p+/RMx5DVgvdrSIqVtgQZWiBlHp2eySdikEwmNdlvmpop9DaWoXmBccCd UFs0CcN0cbJUd8RcM15Qw6uETijbZTVElMUyA7lUAwWGdNlxwbyPXPO2Z+kbaXZSjC2d zPWubYgz9P2dlrrrfGdFPIPbZFOTiyLMbhNi1A0uHOgLIMKFAmbbbziZdrSvihu0Vvon bVKxAZVJ2/PfJtGgQIrzOKlV6IAOioXpg1v1anSCNZg0BMhTsHl7yMGf0faRXVI/r9ND NAqA== X-Gm-Message-State: AOAM531nYOhpGqa/VVIjVUZKxb3mMCvQuoG5g2vdbcvj3jEGnaB1+0D2 RruwoQ5kahSeXFw2bHteSXw9uUn4E6uSVrrNmnM= X-Google-Smtp-Source: ABdhPJxuXZfr6+Tk+zgucB98bDWMpxmddaRKx+gnAgJxUa/6jq76l7hdrNcsQgQyiyrWYlp/Hn9R6PgXPucK+WnDK10= X-Received: by 2002:ac2:4208:: with SMTP id y8mr21478075lfh.27.1625714330439; Wed, 07 Jul 2021 20:18:50 -0700 (PDT) MIME-Version: 1.0 References: <87lf6hr74u.fsf@nicolasgoaziou.fr> <87wnq1tuxs.fsf@tsdye.online> In-Reply-To: <87wnq1tuxs.fsf@tsdye.online> From: Matt Price Date: Wed, 7 Jul 2021 23:18:37 -0400 Message-ID: Subject: Re: [wip-cite-new] Merging tomorrow? To: "Thomas S. Dye" Content-Type: multipart/alternative; boundary="0000000000002c148005c6941d1f" Received-SPF: pass client-ip=2a00:1450:4864:20::12b; envelope-from=moptop99@gmail.com; helo=mail-lf1-x12b.google.com X-Spam_score_int: 2 X-Spam_score: 0.2 X-Spam_bar: / X-Spam_report: (0.2 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, PDS_OTHER_BAD_TLD=1.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Org Mode Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1625714359; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=kfwd9hooSntDY3YIXSB7VXMmdNfLI3AcgWmTcrO9jE0=; b=eh4m3vGNvTPUkwVncCJ0ipHAVsOYlBPiO8ojPEWNciHl9b7qgIYL8O4cmaWN2riSAHClJ8 GkHIr32q0QRjdC/rrfgj6D1W4uxnA5jc3vreCyteRciI8gro9YO8wlw9Rgys3KjFpJ6Kac 3p4vRO9reFwyiXtbGQz++A908/RBUgWxjlqM9zheVnCjeAQEKYNdoBj4z1fQ7RcyM6v/lz d0smcd1ofcCkeEXbXnOhn2RGaGDMrPCFQjEqcN4Dg1APlSAaLjCPJJ0vTErHgM9UuuGGmz 1UGkvvPUfiuXe1nTnaGpxaMUWHXamxg+2ZOO5C+UPYAnyaYglELZGrdIji8jyQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1625714359; a=rsa-sha256; cv=none; b=fXJN1r7EsSPJhZyciitaqQlEj0bgyWBsBzcxNtUeG39tRH7k+K+Hx48j6S2BSbjg9E7aH3 AVaFRFOFkkUwPkcbEQbhF09rUuUYHXtK8gACSc3joKo6FqP1WMEiHVGCEdphUZIPyGPAbs tR2JFz/TCRalAGoPf+Z8S54bL5SM2tLvoRjsQxvkuwsidQGKfFafZ3UAcFZoy7DRbBFQU2 DMMtO80gcrboWUQwaz4A+tm+PIJhSPysC7H1GLwyOHhHY0hvRMkol1Rap3bCbzKDgFgUX3 X4e4z5cmScXJEqvietxYbCwOOJd6Q1IYeXUmlZaJEr8oho30ZYhm/ItqA4nYkw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=N3TZ19cc; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Spam-Score: -2.11 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=N3TZ19cc; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: 2758821013 X-Spam-Score: -2.11 X-Migadu-Scanner: scn0.migadu.com X-TUID: i/Y2vNdwCWS7 --0000000000002c148005c6941d1f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I cannot believe this is finally happening, and I am so stoked and excited about it. I've been using ~wip-cite-new~ in my classes this week, and these new tools are absolutely transformative. Thank you so much for the immense amount of work you put into this. And also to Bruce for championing it, and Andras and Denis and others for their contributions. Really, I feel like there should be a parade. Matt On Wed, Jul 7, 2021 at 10:23 PM Thomas S. Dye wrote: > Aloha Nicolas, > > Good news! I'm looking forward to using this facility. > > Thanks to all the contributors. > > All the best, > Tom > > Nicolas Goaziou writes: > > > Hello, > > > > I think the "wip-cite-new" branch is in good shape now. As > > a consequence, I'd like to merge it tomorrow. > > > > It is documented, but the documentation is scattered across the > > various > > "oc" libraries, and some threads in the mailing list. I'll do a > > summary > > here, from a user point of view. > > > > --8<---------------cut > > here---------------start------------->8--- > > Basically, in order to use it, you need to first set-up a > > bibliography, > > using one or more "bibliography" keywords. on such a > > keyword > > visits the related file. Out of the box, Org supports JSON-CSL > > and > > BibTeX (or biblatex) bibliographies. > > > > Then, citations can be inserted with the following syntax: > > > > [cite/style:common prefix ;prefix @key suffix; ... ; common > > suffix] > > > > Spaces are meaningful except those after the initial colon and > > before > > the closing bracket. > > > > Every part of the syntax is optional, except the brackets, > > "cite" and > > the colon. Also the citation must contain at least a key. So its > > minimal > > form is: > > > > [cite:@key] > > > > The "style" part is detailed below, in the part related to > > export. > > > > Org can insert or edit citations with (and delete > > them with > > ), follow them with , fontify them, and > > export > > them. These four actions (insert, follow, activate, and export) > > are > > called capabilities. Libraries responsible for these > > capabilities are > > called citation processors. > > > > You can select one citation processor for each capability, > > independently > > on the others, through the following variables: > > > > - org-cite-activate-processor > > - org-cite-export-processors > > - org-cite-follow-processor > > - org-cite-insert-processor > > > > Out of the box, Org provides the "basic" (in "oc-basic.el") > > processor > > for all of these tasks. It also boasts processors dedicated for > > export: > > "csl", "natbib" and "biblatex". > > > > During export, output for citations is controlled by their > > style, which > > is an Org label that the export processor may recognize and > > associate to > > a specific display, or fall-back to a default style (called > > "nil"). For > > example, most processors support "noauthor" and "text" styles. > > > > Some styles can accept a variant, with the syntax > > "style/variant". > > Again, it's up to the processor to associate it to a specific > > display. > > Common variants include "bare", "caps" or "full". They also > > accept > > short-hands, like "b", "c" and "f". Please refer to the export > > processors' libraries ("oc-basic.el", "oc-csl.el", =E2=80=A6) for more > > information. > > > > It is possible to define a default style for a whole document > > (with > > "cite_export"), or for all documents (with > > `org-cite-export-processors'). > > > > References are displayed with the "print_bibliography" keyword. > > It is > > possible to add parameters to its value, as some export > > processors could > > make use of them. > > --8<---------------cut > > here---------------end--------------->8--- > > > > Please let me know if there are any objections to the merge. > > > > Regards, > > > -- > Thomas S. Dye > https://tsdye.online/tsdye > > --0000000000002c148005c6941d1f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I cannot believe this is finally happening, and I am = so stoked and excited about it. I've been using ~wip-cite-new~ in my cl= asses this week, and these new tools are absolutely transformative.

Thank you so much for the immense amount of work you= put into this.=C2=A0 And also to Bruce for championing it, and Andras and = Denis and others for their contributions. Really, I feel like there should = be a parade.

Matt

On Wed, Jul 7, 202= 1 at 10:23 PM Thomas S. Dye <tsd@tsdye.online> wrote:
Aloha Nicolas,

Good news! I'm looking forward to using this facility.

Thanks to all the contributors.

All the best,
Tom

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> I think the "wip-cite-new" branch is in good shape now. As > a consequence, I'd like to merge it tomorrow.
>
> It is documented, but the documentation is scattered across the
> various
> "oc" libraries, and some threads in the mailing list. I'= ll do a
> summary
> here, from a user point of view.
>
> --8<---------------cut
> here---------------start------------->8---
> Basically, in order to use it, you need to first set-up a
> bibliography,
> using one or more "bibliography" keywords. <C-c '>= on such a
> keyword
> visits the related file. Out of the box, Org supports JSON-CSL
> and
> BibTeX (or biblatex) bibliographies.
>
> Then, citations can be inserted with the following syntax:
>
>=C2=A0 =C2=A0[cite/style:common prefix ;prefix @key suffix; ... ; commo= n
>=C2=A0 =C2=A0suffix]
>
> Spaces are meaningful except those after the initial colon and
> before
> the closing bracket.
>
> Every part of the syntax is optional, except the brackets,
> "cite" and
> the colon. Also the citation must contain at least a key. So its
> minimal
> form is:
>
>=C2=A0 =C2=A0[cite:@key]
>
> The "style" part is detailed below, in the part related to <= br> > export.
>
> Org can insert or edit citations with <C-c C-x @> (and delete > them with
> <C-u C-c C-x @>), follow them with <C-c C-o>, fontify them= , and
> export
> them. These four actions (insert, follow, activate, and export)
> are
> called capabilities.=C2=A0 Libraries responsible for these
> capabilities are
> called citation processors.
>
> You can select one citation processor for each capability,
> independently
> on the others, through the following variables:
>
> - org-cite-activate-processor
> - org-cite-export-processors
> - org-cite-follow-processor
> - org-cite-insert-processor
>
> Out of the box, Org provides the "basic" (in "oc-basic.= el")
> processor
> for all of these tasks. It also boasts processors dedicated for
> export:
> "csl", "natbib" and "biblatex".
>
> During export, output for citations is controlled by their
> style, which
> is an Org label that the export processor may recognize and
> associate to
> a specific display, or fall-back to a default style (called
> "nil"). For
> example, most processors support "noauthor" and "text&q= uot; styles.
>
> Some styles can accept a variant, with the syntax
> "style/variant".
> Again, it's up to the processor to associate it to a specific
> display.
> Common variants include "bare", "caps" or "fu= ll".=C2=A0 They also
> accept
> short-hands, like "b", "c" and "f".=C2= =A0 Please refer to the export
> processors' libraries ("oc-basic.el", "oc-csl.el&qu= ot;, =E2=80=A6) for more
> information.
>
> It is possible to define a default style for a whole document
> (with
> "cite_export"), or for all documents (with
> `org-cite-export-processors').
>
> References are displayed with the "print_bibliography" keywo= rd.
> It is
> possible to add parameters to its value, as some export
> processors could
> make use of them.
> --8<---------------cut
> here---------------end--------------->8---
>
> Please let me know if there are any objections to the merge.
>
> Regards,


--
Thomas S. Dye
https://tsdye.online/tsdye

--0000000000002c148005c6941d1f--