From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id kCaaMf2sbmdgBAEAe85BDQ:P1 (envelope-from ) for ; Fri, 27 Dec 2024 13:34:54 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id kCaaMf2sbmdgBAEAe85BDQ (envelope-from ) for ; Fri, 27 Dec 2024 14:34:53 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=YTNaESq2; 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=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1735306493; 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=FsaqLKYjb5bzvNT1bXhHK9Mobo/91FlRBEcnGlo5wqk=; b=bKAU1gGvobzRsBCEV/i41fBj2dqyPfiytxez8wLBv6C9XUaow5fs1F8SZi7dAdDO6gfo9o pyhzR8pFicvHllbkeS/JvcOiLB5i+cGrLf3SbBV6SO/tWHasQo8Zq8Ba4vMLrykJ0Cspyd icCKtExevq6itZ0bFzLkIruA6gRLSfAE0f8XH3E8186gKcpBDJ0VyIDiA0CoxHul1FHRFP VjeqhmVF202XbX1jeQ6xPFz98NANIaZlwAvhlJ/blwmBPjSowQKuwxjM36cl4X6kiz1Xj9 Czo/jE4wr9nnZSdFQreSoJIBWpR8X1Q7TlkiU65M4P2TIqs1qhPPy6O8hP33UA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=YTNaESq2; 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=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1735306493; a=rsa-sha256; cv=none; b=Z0zZJnIG9BtRwD0SBMrbQ9dVK5N3m0aBg5Jb8kvAcqQWNDsyUZNSy6ZYYVns2knKgZmtz3 6TL0aBob+GJuJLnxBiZSxjXpSMVB5Q016Ju3M+wqX08xppFmEmV+oecVDVOXp5x0F2xAKY NJD4RTTx/i+2Xjb/IeuRvLIRwroNXB78aKHzbBI0lmorr+U5+hPMCnhrKLifUB5C8mdDUT mVllY40zBhCL4OQPvXrqemz7prYpLYlwfiXFuZSH/guAZNUi4X2NsZXdrHhop6dlmDEEW7 1/0Ga5JmTOSeKa55vAkuIwfvswMJnQML8IxlYOGxOFn4H8Pk2jDQ9SSM1gMGBw== 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 E08539E3F8 for ; Fri, 27 Dec 2024 14:34:52 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tRATK-0004Wv-CT; Fri, 27 Dec 2024 08:33:46 -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 1tRATH-0004Wd-Ac for emacs-orgmode@gnu.org; Fri, 27 Dec 2024 08:33:43 -0500 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tRATE-0001C3-Q8 for emacs-orgmode@gnu.org; Fri, 27 Dec 2024 08:33:43 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 33874240027 for ; Fri, 27 Dec 2024 14:33:36 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1735306417; bh=MnZCiUdv+5LcnIny35nyV3k78Ovosq/Md2rjE3Hus+Q=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding:From; b=YTNaESq2hhqzNEau7s9XvlTWQiIQ8NBdqDw86A2ZOaj0qiZxjzW+x5D7EbkuRRfua zNvew+z7vlNZ6vWJrnqnudNKkrODoyR1IUJQE17PWdCdLKYVrCN4BkTVNYru1t0pjh u/nUp407H+Ca1nS5Ipj1njbeZqFDYFDPTYw44n2RZotu06WR+q/Z2IqopG53XrP7qo FUrO7ribfCmOMwq8e/i9VoLTTRlcynfXKUy+R+GOnIVW9iRWthNQZ8Byaw6qRZJdpu FdQ/85+HCzS6aMfbkK6Qlm42ggqM9VUUFGg42j8gkAa9UkXU8/Gp3mDf6XIV8oTJ2A be89+dMcjQeyw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4YKRKC6SPsz6tvx; Fri, 27 Dec 2024 14:33:35 +0100 (CET) From: Ihor Radchenko To: Rudolf =?utf-8?Q?Adamkovi=C4=8D?= Cc: emacs-orgmode@gnu.org Subject: Re: The less ambiguous math delimiters in tables In-Reply-To: References: <87ldw5igab.fsf@localhost> <87r05vy6xq.fsf@localhost> <87frmayfal.fsf@localhost> <87h66q7dtf.fsf@localhost> Date: Fri, 27 Dec 2024 13:35:00 +0000 Message-ID: <87msgh5jwb.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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_MED=-2.3, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, 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-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -8.97 X-Spam-Score: -8.97 X-Migadu-Queue-Id: E08539E3F8 X-Migadu-Scanner: mx10.migadu.com X-TUID: dSy5PT9kCNOy Rudolf Adamkovi=C4=8D writes: >> In a theoretical case if we agree to what you are suggesting, it should >> not be just for tables. There are similar cases with other markup, like >> >> *foo =3D* *=3D bar* > > Agreed! We could introduce a kind of escaping that means "this MUST be > interpreted as markup" and/or "this MUST NOT be interpreted as markup", > but that could lead to documents that are hard to read for humans. Or, > we could add structured markup that is unambiguous and takes precedence > over all unstructured markup. For example: > > emphasis{...} > verbatim{...} > table[...]{...} > src[...]{...} > > The last one already exists. :) See https://list.orgmode.org/875xwqj4tl.fsf@localhost/ > That said, as for my original problem, I still think that \(...\) should > take precedence over |. Even if we added structured latex{...} markup, > it should not be necessary in my case, as Org should not severely break > basic LaTeX within tables in the first place. Sorry, but no. Basically, what you propose is a rabbit hole that will introduce new parser bugs and, worse, new systematic problems with syntax. For context, I proposed similar ideas to Nicolas, the author of org-element parser, in the past, and he rejected them firmly. FYI, my approach to solve this problem is different - I want (eventually) to allow some kind of alternative syntax for tables that will allow bypassing similar situations. For example, we can allow multiple || to serve as delimiters: | this | is | a | normal | table | row | || here || we || allow || verbatim "|" || inside || || --=20 Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org development at , or support my work at