From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id 2LLCNA4udGf4AwEAqHPOHw:P1 (envelope-from ) for ; Tue, 31 Dec 2024 17:46:55 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id 2LLCNA4udGf4AwEAqHPOHw (envelope-from ) for ; Tue, 31 Dec 2024 18:46:54 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="l/jOZQlt"; 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=1735667214; 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=hl747FUYui6cOs0itB37FlIWjiUzXybfjgod+hjn/Go=; b=uLZTVSsHyJCEl1YOVT5FTv/10dBj9hL6XzK1F70FKKSzmZOtPywMiCIr509fXq3hOt9mNd 6/MLozJVZwTPCnK9i6O7oXwAiW4AEgCXUDdSboMuabFvrJoY2DXxL3h9H6p6yjW/RX/Byj 3/IsKJCSZQmzVGtjO0VI3nw2bbeoL1GNg9Zaj/ump+kmiXvoMQ+n9YD3/OVbYLQkZzyDZP ATqLh36/SM5YrfiJGhz3lo+EbT0jyWMWMn634DVlB93x5d6s91Uv1Ta8vd0JUjy5QoBVa4 SKlO7EhhtA2lUhErIuBNL0UxYDTlrEn1dMjpiXjX8FzcbSuFzpR689LVaVd09Q== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="l/jOZQlt"; 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=1735667214; a=rsa-sha256; cv=none; b=UsLmsJA9hn6E9K++poBem5WV/8l8ZDUwrRYXWxFRucH8SwyY5fRmRCm0YmFnJPnKue9vDn /NDpNTdgDiJzvDuVvS3CfzcweRLY4BpPaP0QTqk67chFefZPcAjeoHpG5OhmtiFvLVICBm KTRflJK1bUzMvTejRuc3NljxhQDThee9WfdctIdpN9HuREXYHbxInLuQzMWNBzSiCXsa8C EHGFWxYUcKUml6qM9ihYV0pSSAPkk7MY4GRk1f8DxgPUx5Om87qzxWrbGIhpr3u3KGcVCU v2CpjnGays0lJoYKF91+8XJvgnDcV4aR4vpTTo/zVyQ+uCcty5wSXbrp9dMhyg== 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 C70827FCBA for ; Tue, 31 Dec 2024 18:46:54 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tSgJh-0004zr-0t; Tue, 31 Dec 2024 12:46: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 1tSgJe-0004zX-1t for emacs-orgmode@gnu.org; Tue, 31 Dec 2024 12:46:03 -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 1tSgJb-0008W9-2G for emacs-orgmode@gnu.org; Tue, 31 Dec 2024 12:46:00 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id D9453240027 for ; Tue, 31 Dec 2024 18:45:53 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1735667153; bh=kPOp4sUXWmbX4r/lxBEeiq2l9rkC2EpW8edfG3XCQVQ=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding:From; b=l/jOZQlt02sAt3Jm+IEoKYkPB/21SIhjBBVHqdpb6croK5PJ83qxq3Pfoz5sZ3CqP urKyXJE1WZn0OVRfFoy39a/V3kbV18+ECRRlZZr99wvAoT8+hYeBouBj+D6u3EYb7m NCEYUtACoabpCa+5zXW6o/ii1A43JJ9QHTohWIY118eYmnR+NOFKecdzNafEf0w+o+ e7Gjia6M0YFHsz0hxfDzdCwDZxxvIOV2YVTHmBOBbUeb/t2bqiJkbCYoCP2GzxWTdE iAZbWEPUqI67uCaIvkN6GZ1mfNCNWuQcj6YFgUqjdqJFkCMxG4cQndnkfB4vRYCrI/ eQSI1z9SmLh3Q== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4YN0kT32WXz9rxB; Tue, 31 Dec 2024 18:45:53 +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> <87msgh5jwb.fsf@localhost> Date: Tue, 31 Dec 2024 17:47:23 +0000 Message-ID: <87ikqzhhhw.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-Queue-Id: C70827FCBA X-Migadu-Scanner: mx13.migadu.com X-Migadu-Spam-Score: 0.01 X-Spam-Score: 0.01 X-TUID: BiFRzZjLZRF8 Rudolf Adamkovi=C4=8D writes: >> | this | is | a | normal | table | row | >> || here || we || allow || verbatim "|" || inside || || > > Your idea is not that different from what I proposed, except that it is > a less general, in that you special-case one particular problem with > tables. Or, would the "doubling escapes" work for all markup? Yes, all the markup. > ... Still, > that would not solve other table-related problems, such as > > | =3Dfoo=3D and =3Dbar=3D |, > > where the problem is =3D and not |, right? What exactly is the problem in your example? > As for "parser bugs", I find it hard to believe that we could not come > up with some unambiguous sequence of characters, even if ugly, to > instruct the parser about precedence. We can. For example, via inline special blocks. Or via "repetitive marker" syntax I suggested above. And coming up with ugly syntax is worse than finding a good one. --=20 Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org development at , or support my work at