From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id 6OxLL97GdmcyIwAAe85BDQ:P1 (envelope-from ) for ; Thu, 02 Jan 2025 17:03:26 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id 6OxLL97GdmcyIwAAe85BDQ (envelope-from ) for ; Thu, 02 Jan 2025 18:03:26 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=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"; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=gmail.com (policy=none) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1735837406; 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; bh=tIY5ht0qfYTyVHQzt/q9c3gYAhCEIfW0mg1BqsTrizU=; b=WcqmqumVrgz7QreFmq/1Cmy+9r8q0tB/GLaenHtRVPu0RDClXE+gzyA4qLxBhfppo9Fwun ItUkPKt9XMsyOkMyZUpF8AJ35WEm8BlcShfjG43J2+u/yKTEjQoyn4p+Fgp58+Oty2xqFN vSEpKClZnde5lM/uyJpbNUCXSJo6QwyLCQAAl3qdeudrGaTua7pnmRYnHBM8KQfpNK5SB2 UwfNzU3CKS3YaGLyTZdiSIyze6oCHDof93JY5Aye6NeFRlryxuFBjRlA94cHugthtOExD3 bnAetwrhyuZtdSff/5Pvfseq8NLAMXVfcOEw5v45agLUcF345+R6Ac9vTjUBLQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=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"; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=gmail.com (policy=none) ARC-Seal: i=1; s=key1; d=yhetil.org; t=1735837406; a=rsa-sha256; cv=none; b=RVUjF5OkDAJeOo6+BOqtLZwaOLsUy4vkjGAjnl4ADJ7RMTcm4V4XlHEeQ9BUHZg7BYeNWQ Sv6Ygh/hq3dfQRxV5Kiq7SHT48Khs0A3yGOX1PCxuk8PX3KtXvK+M36eYOpfCsD8PgjHVa Llr3zmMrH6LdCK1+Z47fyUS5xKMmsqD43u3sQwxqsz/xrp+0ih4tfc1aiMO8VYdz3IC0bb 1VkqOQ7XPYMIZjD+5TjUNmso3bWzQ3BCmjI1zGm1vBoJwyhnKhwUa+6GEewhUpdy5QDzhi DXQ0TcHB9On5vWDnxAgFqzsQu+wxOc4i1D+I6P1zypx6P5Szxk25/aSsMOtEJQ== 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 8E05B63F26 for ; Thu, 02 Jan 2025 18:03:26 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tTOam-0005JE-AV; Thu, 02 Jan 2025 12:02:40 -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 1tTOag-0005E3-Tf for emacs-orgmode@gnu.org; Thu, 02 Jan 2025 12:02:36 -0500 Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tTOaf-00022D-Ac for emacs-orgmode@gnu.org; Thu, 02 Jan 2025 12:02:34 -0500 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1tTOaa-00062F-DC for emacs-orgmode@gnu.org; Thu, 02 Jan 2025 18:02:28 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: emacs-orgmode@gnu.org From: Max Nikulin Subject: Re: The less ambiguous math delimiters in tables Date: Fri, 3 Jan 2025 00:02:18 +0700 Message-ID: References: <87ldw5igab.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit User-Agent: Mozilla Thunderbird Content-Language: en-US, ru-RU In-Reply-To: Received-SPF: pass client-ip=116.202.254.214; envelope-from=geo-emacs-orgmode@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: 25 X-Spam_score: 2.5 X-Spam_bar: ++ X-Spam_report: (2.5 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.2, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no 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-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Scanner: mx12.migadu.com X-Migadu-Spam-Score: 3.80 X-Spam-Score: 3.80 X-Migadu-Queue-Id: 8E05B63F26 X-TUID: DZl3aG2zWpHC On 31/12/2024 04:25, Rudolf Adamkovič wrote: > Max Nikulin writes: >> An extensive test suite is necessary to consider alternatives for >> parsing rules. > > Yes, that much is given. Without an extensive test suite, working on a > parser would be nothing but a waste of time, and the end result would > be, at least for us humans, an infinite stream of bugs. I do not say that there is no tests, but to change the parser almost certainly much more corner cases should be added. The format should be suitable for non-elisp tools. Ihor Radchenko. [PATCH] org-test: Create a collaborative test set for Org buffer parser. Sat, 11 Dec 2021 22:39:07 +0800. >> Current logic may be roughly describes as the following. When Org >> recognizes start of some element, it tries to find its end, mostly >> neglecting opening markers. A fragment is parsed for nested elements >> *after* boundaries of the parent element are determined. > > Honestly? That sounds like a wrong approach to parsing. (And if that > is the case, then that could explain why I keep fighting the Org parser > on a daily basis, compared to practically never in every other language > I use.) I expect that pandoc-like parser may reduce number of pitfalls. However, having no experience with parsers, I will unlikely try to implement it. I would not be surprised if it is unfeasible without some parser generator since it should be bottom-up one. I have no idea how to collect real life cases when current behavior is better. Otherwise it is hard to estimate degree of disaster due to breaking change.