From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id EA0CMcf7hGGdQgEAgWs5BA (envelope-from ) for ; Fri, 05 Nov 2021 10:39:19 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id QP6yLMf7hGGKfAAAB5/wlQ (envelope-from ) for ; Fri, 05 Nov 2021 09:39: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 0E3D8C207 for ; Fri, 5 Nov 2021 10:39:19 +0100 (CET) Received: from localhost ([::1]:51042 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mivgq-00016b-R5 for larch@yhetil.org; Fri, 05 Nov 2021 05:39:16 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:40014) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mivgP-000164-9C for emacs-orgmode@gnu.org; Fri, 05 Nov 2021 05:38:49 -0400 Received: from mout-p-201.mailbox.org ([80.241.56.171]:14150) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_CHACHA20_POLY1305:256) (Exim 4.90_1) (envelope-from ) id 1mivgL-0002Ha-La for emacs-orgmode@gnu.org; Fri, 05 Nov 2021 05:38:48 -0400 Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:105:465:1:2:0]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-201.mailbox.org (Postfix) with ESMTPS id 4HlwS11KqHzQjXt for ; Fri, 5 Nov 2021 10:38:41 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=guelker.eu; s=MBO0001; t=1636105118; h=from:from: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: in-reply-to:in-reply-to:references:references; bh=gLPMWfdKU9OVl2FJcvTkCrkuSCNEpPR61Ht9CiyubdU=; b=WL9JAdY9aJX4Wp1oYp5zkoP0mmV3O8QP263u7qo50ZKUhzYS3gEl60J9mhld7de4YdZHeA 7q3u+t27V2ffpSbueQk5VJ0UH35SkDTut1F1WPKht0QXZEO6vOS1+SzCOpO0X79UHFI18D DBEnLAhs0wL9Fj9gKsfW67RnMiR+kyJY7HTfWL46OkcyCgckhzDWFRiChic++REIMYe1hw RqwbyHfs93OPwk2tcQoOr2o3XEkzVWZD4CnYp0rNK2t4ge6/t7cT6ovFyM7eUV54inatLB NDVCwgLVOaYhyiCTRdXSBxdVWtZZ8DM1sjXyIbrkcfbkauaCFIqnykCcDdE7zA== References: <923e51a09367741650c05692009e00ae913a28d3.camel@free.fr> <87bl31tdn7.fsf@nicolasgoaziou.fr> <11cf2687ca5444b9cd8e8d0250e20946b387d7cf.camel@free.fr> <87bl2zsh17.fsf@nicolasgoaziou.fr> From: M. =?utf-8?B?4oCYcXVpbnR1c+KAmSBHw7xsa2Vy?= To: emacs-orgmode@gnu.org Subject: Re: [PATCH] c-csl : accept relative CSL filenames In-reply-to: <87bl2zsh17.fsf@nicolasgoaziou.fr> Mail-Followup-To: emacs-orgmode@gnu.org Date: Fri, 05 Nov 2021 10:38:32 +0100 Message-ID: <87r1bv2b8n.fsf@atlantis> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 970571844 Received-SPF: pass client-ip=80.241.56.171; envelope-from=post+orgmodeml@guelker.eu; helo=mout-p-201.mailbox.org X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 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, RCVD_IN_DNSWL_LOW=-0.7, 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: List-Help: List-Subscribe: , 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=1636105159; 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: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=gLPMWfdKU9OVl2FJcvTkCrkuSCNEpPR61Ht9CiyubdU=; b=fRpgkVvx2us0/AF/YNpgY1biB8DvNqxhtsaUYFKtYcJqJ0xNZlFMHkd+nPxwdBEOqeGZGW cS+DPoOXSOiQ6TSMshYjCGIFuamBegjdDbfO4M+ioqpI5IRcQ7hBGhHJ7K0tkcxoXQaq0o 7A8ET3WweBwagAwWkDYfgyOq6g3SyQZZbE4yLA/osjs22yYztEAhWxUMyLjj3YpUB1l1pk TBIJS+Qwwzc7bEYAFJrDZsjkFfInmRpezYhJXOhZrx0DlWq9mrVZpi/ZRxhVyyuTf7NzVE G74MuXNT1NlvZwP1BWNDWwM6FqEvcB49DuSclh/hW4zExUFYypOeEQGOupLI+A== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1636105159; a=rsa-sha256; cv=none; b=UJ3Rf8v44UIxFLN2CsK8izsk3vegNfxCTireDx/Q5H6xz3HJP3MMePCfcD/sgBDzNYGW29 VwYiVRF3ZL5fGp2fdQIRxhwqKQgeVUDXr4xQpr13TZQwW8tMmcUA8DPNwGm3G4qLqrFYNw 3bRAeVGGZOacJCRQeFAYnPiTEhI6gATDgQdm+Qx42dv3hwsvc1TkPFQ4ncN5glo2/8zEml KMiRPIYciuoXHfMB0pc0sCfRa2Ti+WqL6EoYHZV7vRR+iDjRaqAckjUtQSrDOVCus7G38O UcxQUyEPYbxYFIUYRCX4sxqVdAOylZDDSTHlD6z9XZXOYsj6Jk0keBCDf3ljuw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=guelker.eu header.s=MBO0001 header.b=WL9JAdY9; dmarc=none; 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.12 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=guelker.eu header.s=MBO0001 header.b=WL9JAdY9; dmarc=none; 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: 0E3D8C207 X-Spam-Score: -2.12 X-Migadu-Scanner: scn0.migadu.com X-TUID: dW5dbpwSC2Tp Am Donnerstag, dem 04. November 2021 schrieb Nicolas Goaziou: > I think there are two ways forward when a relative file name is used: > > 1. First check `org-cite-csl-styles-dir' and, if it is nil, expand > against `default-directory'; > > 2. Drop `org-cite-csl-styles-dir' and always expand against > `default-directory'. > > What do oc-csl users think about it? On the risk that I do not entirely understand the dispute: I would like to specify relative CSL files. Currently I work on a commentary which has its own, specific citation guide lines, that is, I need a custom specific CSL style just for this project. Naturally I store this CSL file along the .org file in the same directory. I can specify its file name as an absolute file name (which is what I do currently), but it would be easier and immune to moving the folder around on my PC if it could be a relative name. It would also help in creating minimal working examples for bug reports, which currently require org maintainers to adapt the path to the CSL file specified. That would probably mean option 1. Option 2 seems extreme; while I have not yet accumulated a reasonable collection of CSL files for the German law journals, I suppose it will happen at some point, in which case it will come in handy. Still, for the sake of archiving the .org files in a working state, I may still want to be able to store the CSL file along with the .org file. After all, the CSL file may be modified later on and then it may not be possible to re-export the .org file. Having both the CSL file and the .org file together (in one repository, for instance) may seem preferable to me. It however is all too new to me to make a final judgment on this question. What about a third option: If `org-cite-csl-styles-dir' is not nil, check if it resolves to an existing file; if no such file exists, expand against `default-directory'. If `org-cite-csl-styles-dir' is nil, expand against `default-directory'. -quintus --=20 Dipl.-Jur. M. G=C3=BClker | https://mg.guelker.eu | PGP: Siehe Webseite Passau, Deutschland | kontakt@guelker.eu | O<