From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id AC4CL7ZR92N0agEAbAwnHQ (envelope-from ) for ; Thu, 23 Feb 2023 12:44:54 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id cIH4LrZR92MvwAAA9RJhRA (envelope-from ) for ; Thu, 23 Feb 2023 12:44:54 +0100 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 4FDE832DC1 for ; Thu, 23 Feb 2023 12:44:54 +0100 (CET) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=SGcXGaTJ; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1677152694; a=rsa-sha256; cv=none; b=ASEXZTmEavM9eSFWJUdxA3fNd+LYWPwLkCskjnHiKNPzxxVZ1aBfU5aIlNp91ATQhPLTiV bMsWihCovaYhJd8xOPIqiWyrfLP3/AODyJ2+UpDLhYxkB/VJvbYdDoikrwf7K1kzAsmYAj Ri3PL+gc4TkcuGl8HuwekJYE4JDfmNdjF5ekUpmyrLoTW+BU5P0/IvpYa1XBoDQDNH+qi9 QvvrArOwZEDEa3E+JdOKzrzITwmhLYipIy9vOupjyO1aM8eMDB3GOiZONdFeuL21ggiNl5 DHYY1EYd2ytKllvY7SfK3L1a0XYgjn78C8DpXarjM63RbUYD+uPmxm75+XZwdg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=SGcXGaTJ; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1677152694; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=df+4tCbDQDerSPf3kSfxNXlcY6RAcXVnL2S3ehj1C4g=; b=jw4ac+0Ap/fKVFrTAqmwV14YJ2+TEELgMyAgDXnS1lkSMZfHUNbGA6A4w9eK1LADiVtnoy 6ghqWIaT2SOILpplUYlhGMekNNAItprrC3WwWSeSq3Lu3od3CqDaGEk21aINtcmZ6hvcjn 6Sd5pv7m36CPS2PiWEvAQxsNOxuFHo9WfmN79khix5XIyFlpdbytjXRIar2mELcwUyRw2U k5BMCia95+rj+/DFUfAwoBUE2py/jokggvuKOfYULoWSdvFiZDklvE5mAm8G/o6WYM9nvB M5rBJrETWggWm1HyKRg3hRjfGel84u03eiW5qLnAksQsO3T43aSLgEPCazm6ig== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pVA16-00088a-Vv; Thu, 23 Feb 2023 06:44:05 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pVA15-000886-OD for emacs-orgmode@gnu.org; Thu, 23 Feb 2023 06:44:03 -0500 Received: from mail-ed1-x534.google.com ([2a00:1450:4864:20::534]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pVA13-0005Tl-Rr for emacs-orgmode@gnu.org; Thu, 23 Feb 2023 06:44:03 -0500 Received: by mail-ed1-x534.google.com with SMTP id i34so15726681eda.7 for ; Thu, 23 Feb 2023 03:44:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=df+4tCbDQDerSPf3kSfxNXlcY6RAcXVnL2S3ehj1C4g=; b=SGcXGaTJsz0ayjo7OAIrT+O85/6IrKt0t64yeEMn/fua4L8uYnBVrFKO7vLA3zuhP0 /UY9ZyHkgrSSGu6aLuQ8L4JKfE+oZIqwEzkrqTf6MOa4hdBosVoU5lAE9SDnEcZuf5+M brY9+PKjdumLJ4/f669W22f9C6twDUd/5CY3uEAXnpmnl60XXlWjpmgCoZ0HcVxtntb3 3DoOemDa06F+RZSHbReGsgbfJCw9XeZS59xVqBqEQ5fbrkVYqSPjstnMn6G1WVqU76yz Zhbbx2707p9mXnCl/U9QBoVVa2MO3CARLpAiV69rkZH05GjJTD9YF1fD7vFhkxSeIpVv ECfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=df+4tCbDQDerSPf3kSfxNXlcY6RAcXVnL2S3ehj1C4g=; b=jilkdaxzrnXyd6Bl5iF6Lzg+itvAJKEJV2u4m1+4mm2x+dwDZ/aY9RFe2mI9goIOax 8Po1JJOdgUxOari5wtQJzpRRvvSSfTZE0BHJvvRp/Wqpv/L0o6GzyelZ9R7QG25q76rL RPVCBGjN+w6j6p2izY8Jej03PQXvuI/MrVZTH92H3rPb5FqscPpOHCJ9MJCvLCxhlpVl 7EsqGtIgxYYGzMDjXOnEBoaWKCH45EaOd/LHDK/ufYzgvkpDl8e+9taeENy098H8wdTl czZ381tGAzan1NAsediwyb3VgY9W80/v5507VHRAhDA1R5FsZ2KPez9mLmAlmv9E2Mxa /qRQ== X-Gm-Message-State: AO0yUKWPOJ3Nbt8AcQrcdYmu4aY0w1FWbcZttYTdSULE0XK5bZpNe1Ib MImNzvtOTgqW9zZU6rc2iaytr8y8TQorPmWs6UQ= X-Google-Smtp-Source: AK7set+nwVU+yThks92pk93C0JIlvRz+vqo+8nyOm1CFXHcPz22//6H/zZS+oIMs4um9rX1+5pY/vU34c45J2vAyAbk= X-Received: by 2002:a17:906:79b:b0:87b:db55:4887 with SMTP id l27-20020a170906079b00b0087bdb554887mr8692927ejc.4.1677152639695; Thu, 23 Feb 2023 03:43:59 -0800 (PST) MIME-Version: 1.0 From: Pedro Andres Aranda Gutierrez Date: Thu, 23 Feb 2023 12:43:33 +0100 Message-ID: Subject: Re: Re: [BUG] #+cite_export: ... bibstyle citestyle cannot be universally used as global defaults (was: Patch for \usepackage[ ... natbib = true ...]{...biblatex} with org-cite) To: Ihor Radchenko , Org Mode List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2a00:1450:4864:20::534; envelope-from=paaguti@gmail.com; helo=mail-ed1-x534.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: X-Migadu-Queue-Id: 4FDE832DC1 X-Spam-Score: -10.18 X-Migadu-Spam-Score: -10.18 X-Migadu-Scanner: scn0.migadu.com List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-TUID: Tycr8ITvWeCA Soory for the re-post... Just setting up a new email client On Sun, 5 Feb 2023 00:14:59 +0100 (CET) Edgar wrote: > Dear Ihor, > On Feb 4, 2023 at 12:31 PM, Ihor Radchenko wrote:Ed= gar Lux writes: >> For example, ... the proposed idea is >> a bit awkward: >> >> ... >> #+cite_export: processor[opt1=3Dval1,opt2=3Dval2,...] bibliography-style= [...] >> citation-style[...] >> >> I assumed that there is one "major" bibliography-style/citation-style. >> However, it is not really the case in practice. The styles are combined. > First of all, I quickly glanced at the other citation processors, and the= y seem to have been implemented with a different design in Org. This *may* = have to do with biblatex being more advanced (disclaimer: I'm not saying th= at it actually is, it's a possibility only). > If the idea is that all processors are going to get the same syntax, I th= ink that the implementation may not suit one of them. At that point, it may= be that the filters will have to be adapted to specific processors in cont= rived ways. This of course will be much dependent on the choice of processo= rs chosen to be supported by Org. Some other groups may decide to implement= , for example, the JabRef #+cite_export (this does not imply that JabRef is= a citation processor, it's just a colourful example). >> For example, adding links to bibliography to citations is applied >> regardless of the particular citation command being used. >> >> So, I am not leaning closer to only allowing options being passed to >> "processor", but not to styles. This will at least come closer to >> certain settings being citation package global config applied to >> everything. If we have options applied to specific citation commands, >> they will rather fit into citation-style/sub-style. >> >> #+cite_export: processor[opt1=3Dval1,opt2=3Dval2,...] bibliography-style >> citation-style > If it were me, I would consider just having the options as =3D#+cite_expo= rt: processor :options "anything"=3D. If the bibliography-style is importan= t for the user and processor, may be default values can be provided; and le= t the user read some documentation option which are needed to run her parti= cular processor (provided by them, not necessarily Org). Again, being compl= etely honest, I don't think that you should put a dummy (like me) making th= ese very relevant decisions. Joining the discussion I seem to have missed before (because I was using a less org-ish solution). My scenario: BEAMER and LATEX are my main targets, both with BIBLATEX and biber as backend. Works nicely, and I can include a bibliography at the end of my presentations, which is nice for lectures. I'm more interested in the 'processor' part, because the default bibliography and citation style fit me. However, I think that something like: #+cite_export: processor bibliography-style citation-style :options opt1=3Dval1,opt2=3Dval2,... as a generalised form (for the shortened version with default styles): #+cite_export: processor :options opt1=3Dval1,opt2=3Dval2,... would be expressive enough. Best, /PA --=20 Fragen sind nicht da um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Headaches with a Juju log: unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run a leader-deposed hook here, but we can't yet