From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id IATbI2mQTWMXbAEAbAwnHQ (envelope-from ) for ; Mon, 17 Oct 2022 19:27:05 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id +FzwI2mQTWObhAEA9RJhRA (envelope-from ) for ; Mon, 17 Oct 2022 19:27:05 +0200 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 DF47B12703 for ; Mon, 17 Oct 2022 19:27:04 +0200 (CEST) Received: from localhost ([::1]:60068 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1okTtH-00080W-R4 for larch@yhetil.org; Mon, 17 Oct 2022 13:27:03 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:45350) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1okTsg-0007zl-2Y for emacs-orgmode@gnu.org; Mon, 17 Oct 2022 13:26:26 -0400 Received: from mout-p-201.mailbox.org ([80.241.56.171]:33088) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_CHACHA20_POLY1305:256) (Exim 4.90_1) (envelope-from ) id 1okTse-0001Lg-1D for emacs-orgmode@gnu.org; Mon, 17 Oct 2022 13:26:25 -0400 Received: from smtp1.mailbox.org (smtp1.mailbox.org [IPv6:2001:67c:2050:b231:465::1]) (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 4MrkRk1Pgkz9sTF; Mon, 17 Oct 2022 19:26:10 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=guelker.eu; s=MBO0001; t=1666027570; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Tu5FKXqk1vWR0GWfv8u80gL6K2ySquGalWYpLeWvMKw=; b=vGpt/YGHO+s9C+M52MXKfW7oB2PrdzOHynMBca539IvlgGw5v0J0kiH80Xd6DbA5TpehK/ DP6Rp0oDc5kGbTumTibUODjiJ6rSHAdgbOkdBJu/PPBD3ZAG+ScHEn+ITgnnGngaeStp44 cBHiddXcvD+T+pH6mSYNj8DwVyh+p4jzuFenHQVEeE3EVZyhwJy81ufqCMNYjanF0qRcj2 BfxL5PmjtWGBPvTxAIdgW9sUvd8gJbYFmL59fSUEtf3Yb/02gBjO1nPMEylsntPEYdbpHg 4mTEBfvHLua4FHXpEawXKOqza+YW7agisFYIGsRMKsfm7IzKTLNWAoE+6FheJg== References: <8735bot9dp.fsf@guelker.eu> <87lepg6rmh.fsf@localhost> From: M. =?utf-8?B?4oCYcXVpbnR1c+KAmSBHw7xsa2Vy?= To: Ihor Radchenko Cc: Nicolas Goaziou , emacs-orgmode@gnu.org Subject: Re: [bug] Macro in citation not expanded Date: Mon, 17 Oct 2022 19:11:30 +0200 In-reply-to: <87lepg6rmh.fsf@localhost> Mail-Followup-To: Ihor Radchenko , Nicolas Goaziou , emacs-orgmode@gnu.org Message-ID: <87tu425pla.fsf@guelker.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4MrkRk1Pgkz9sTF 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 X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1666027625; 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: 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=Tu5FKXqk1vWR0GWfv8u80gL6K2ySquGalWYpLeWvMKw=; b=recuOEkLVWoQGDq6rT7TreW0v5FlH/NaoM9OefwAH61LzeZa8Irip4Ra07+Dd9Ttr4Oy8H YfD5oVYcVy8+x+rkgOz3kObrxn8XGTuugQQNFvIVOR1BxDnsb5VMZw1ik4SLgA3J3053oZ z95jnBN0z0Zi0Pkn/vDJfSynq22TMHsNmwlH2Fpys/B8yT04kJQsSZRmE0chlzx4O0HCRg azJH8V1wKL1ToNEA89pFsO2D9hmtAHHqqQdVNF65GstUT1ZqVlVHxo4lGBUmGNactLalxQ re7wi1cZR5xHqldv5cm79TMvZQg67MBngEaZfJk9ccOXPwHbyYmh/6++zzEDeg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1666027625; a=rsa-sha256; cv=none; b=lmflzHN09DGBKbnNAcXfbE4fGlD5acjFRhfzgvY1uDaJoJYMwWInWLf5szz12BXjqOkhTb JG8uWAI/YXNAUGARrQCstdm1YJHRrNEjb/E8RZaqwGkayKo3iNgDJBhl67XnskSs2z8eSZ nEk8pIo68uvIV0X/uu4sWQvaZiAWrPNgPEdpW6GRZgPsFHUeGL0LQvuS5vOu+6/Le0t5tl Aj00TvU/l6jURSvsBu+/4MqrPApsIsVWEgD7tbpP0+ChwbrBgkEa/7x3fVmPVUoGpaK144 taacQHRZndjbuJxBIXZ3IpQNHuPfoLmZtqEujZT/g2rnSfK/dpvvKF5shPoQUA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=guelker.eu header.s=MBO0001 header.b="vGpt/YGH"; dmarc=none; 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" X-Migadu-Spam-Score: -2.12 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=guelker.eu header.s=MBO0001 header.b="vGpt/YGH"; dmarc=none; 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" X-Migadu-Queue-Id: DF47B12703 X-Spam-Score: -2.12 X-Migadu-Scanner: scn1.migadu.com X-TUID: IOeoFKOdwf8l Am Sonntag, dem 16. Oktober 2022 schrieb Ihor Radchenko: > Only bold, code, entity, italic, latex-fragment, strike-through, > subscript, superscript, underline, and verbatim objects are allowed > inside citations. > This is hard-coded inside `org-element-object-restrictions'. This is a bit unfortunate, because I like to use macros for inserting semantic formatting which is not part of org=E2=80=99s syntax. In the examp= le given in my OP, I use it to mark up names with small caps. The exact example given includes a short note by me talking about the cited author a little further. Another example where I need this is when I cite some statement made in an interview, which may come out as something like: [cite:{{{name(Interviewee)}}} in @interviewer p. 5] Indirect statements by persons mentioned in news articles are another example where I would use such a construct. I define the `name' macro in such a way that it will format `Interviewee` in the same way as the citation style formats the author name for @interviewer, ensuring uniformness in the created footnote. I also use the very same `name' macro inside the actual article text, so that uniform formatting is guaranteed there as well. > It sounds reasonable to allow macros inside citation references. > Maybe we also want to allow other things. Maybe simply allow all objects > but other citations, line-breaks, and table-cells? I have no strong opinion on this. I certainly do not need tables inside citations. If it is easy to just permit everything except what you named, I would say just allow it. Maybe someone has use for it. Maybe footnotes inside [cite:] construct should also not be allowed, at least for footnote-based styles. -quintus --=20 Dipl.-Jur. M. G=C3=BClker | https://mg.guelker.eu | PGP: Siehe Webseite Passau, Deutschland | kontakt@guelker.eu | O<