From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id qE5FN/v08mE/IgEAgWs5BA (envelope-from ) for ; Thu, 27 Jan 2022 20:39:39 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id CL6wM/v08mHCTAEAauVa8A (envelope-from ) for ; Thu, 27 Jan 2022 20:39:39 +0100 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 7BF7AABC1 for ; Thu, 27 Jan 2022 20:39:39 +0100 (CET) Received: from localhost ([::1]:46570 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nDAcM-0005pk-Jo for larch@yhetil.org; Thu, 27 Jan 2022 14:39:38 -0500 Received: from eggs.gnu.org ([209.51.188.92]:46098) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nDAWK-00009g-Gx for emacs-orgmode@gnu.org; Thu, 27 Jan 2022 14:33:24 -0500 Received: from [2607:f8b0:4864:20::102d] (port=55217 helo=mail-pj1-x102d.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nDAWH-0001V9-8K for emacs-orgmode@gnu.org; Thu, 27 Jan 2022 14:33:23 -0500 Received: by mail-pj1-x102d.google.com with SMTP id r59so4015653pjg.4 for ; Thu, 27 Jan 2022 11:33:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:user-agent:from:to:subject:date:in-reply-to:message-id :mime-version:content-transfer-encoding; bh=mwlXi5W1vCk2PEp90rfBfLSZwEP4TYAJWTx/LkEZZWs=; b=LhMSbePX1t788Lx/l8zUidmsVK8Y648/2sSGNZwR4SgGoUgiglv4fTk22gJBtW0ZYx Z5QDFIVV+bAj9q58OEN7s2zgnw7OOG2bzs0YoelrxbsexvIrA76pIABfL8xeJpebPNUt RZePTquD5PU5bgpWIUaG8yWbY/8o8GlCkwrWlK0Fna+kXt1+DPEu1f8TUMIog+lYOqid cpwNdcLvnVXrrmtQdvCFn/wCeylLoTT9YGqikT6RfwR30FR6tQfMtQ0QlF3aIhhvLPjb IevyVmJbo5KwihO1eDxG+Si1C6vndJy6uLLWw3HiWncLpYiBfPlhFmxxyQo/fK2xE60G xUPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:references:user-agent:from:to:subject:date :in-reply-to:message-id:mime-version:content-transfer-encoding; bh=mwlXi5W1vCk2PEp90rfBfLSZwEP4TYAJWTx/LkEZZWs=; b=5sKwz+7whEPmxi1jEPZFdfCkIqb9tulpsMTHsMDBHdJQiCGJX4sErKEhjnd/Nk5jtl ++NTu8B254HRrjqDzEnWEZERRwYzsn5q0rlzC8xUXXTOAFuZdtHcP2G7ZzXO+uMo/0Gr K/erbJoTkUUtMnldhjI/ivAAWIHDZgYiRuFii1jUMyzgiTFS2cqX+es1RW7qRI3EF+9v 3s9Rrmm1zQjb5TqJ6gNzMa927TzeJKCTlQi34aqtE23doAyEw4IolyfVzf6JH+MXPmF+ JdKyrRZf3BxsdXpeKV6fle883ONjI1cMfXkc7Nm9YwB4tfvgBo4UN3/uvceuE1zV9U7y 5rmg== X-Gm-Message-State: AOAM530o3hEhfhep3rzp405gavsq+kEPswIQc0s0ATkHtoRt7RsoNEow 7tj9zDC24FURc15uEFT+PV47nELi9yU= X-Google-Smtp-Source: ABdhPJwMN+Cb+IrLqagCHeAOPkgdjZh1TR4twZXMuWwN7VgfCl0sWyC15kOiJvIVNDk2T14Os5tySg== X-Received: by 2002:a17:90a:17a5:: with SMTP id q34mr15552121pja.1.1643311999106; Thu, 27 Jan 2022 11:33:19 -0800 (PST) Received: from dingbat (2001-44b8-31f2-bb00-d86c-b91e-3f0b-4015.static.ipv6.internode.on.net. [2001:44b8:31f2:bb00:d86c:b91e:3f0b:4015]) by smtp.gmail.com with ESMTPSA id h9sm6988699pfi.124.2022.01.27.11.33.17 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 27 Jan 2022 11:33:18 -0800 (PST) References: <874k5si6zh.fsf@ucl.ac.uk> <87r18t7fc5.fsf@localhost> User-agent: mu4e 1.7.6; emacs 28.0.91 From: Tim Cross To: emacs-orgmode@gnu.org Subject: Re: [PATCH] Add support for =?utf-8?Q?$=E2=80=A6$?= latex fragments followed by a dash Date: Fri, 28 Jan 2022 06:15:10 +1100 In-reply-to: <87r18t7fc5.fsf@localhost> Message-ID: <87mtjhnfd0.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:f8b0:4864:20::102d (failed) Received-SPF: pass client-ip=2607:f8b0:4864:20::102d; envelope-from=theophilusx@gmail.com; helo=mail-pj1-x102d.google.com X-Spam_score_int: -12 X-Spam_score: -1.3 X-Spam_bar: - X-Spam_report: (-1.3 / 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, FREEMAIL_FROM=0.001, PDS_HP_HELO_NORDNS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, 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" 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=1643312379; 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=mwlXi5W1vCk2PEp90rfBfLSZwEP4TYAJWTx/LkEZZWs=; b=fv49YJTQT80U5Xf10iy/kD5E/N0EiWM2Kxgs1xqr/GhHm9kUBfvsJz/HWWuYk2FnQLCgIK MPrV5xLIirSwMBgGwXzuSXJHUCLhzBM7LqqpIu33d4Ljj1ZZPo8mRSr9dtfEEGm8DbGs5m TkM7fSXxWs1ANq8AzQJg5dGWAq4vk6TMeAFN3FDTY6UCDk/sqhnHVfwBmSjiKzJFR3F1fH la7TQv1U34ydEWqVK2kgjuXbuuxem3p5totsmTLIy/O7+pBP3i6GOtx6jkiS8JfFNnjIFc 4xxNkRGP3W/lfWP1rIe/LWLmsiWkfv+/zexR0of3XRdMc+GXISO4bF11PGzPkQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1643312379; a=rsa-sha256; cv=none; b=D/yQsehC6OeypdeV0CfOMUvTpKJ992GeA7XExQzXufMFlEANO3bQL5slexR/s0oCDNOtZV M13YAQO4vfRTTQsek1Y5T0Lr+2DontXbKoRfIP+/rggj5V8EvVAQEk61PkXiZpgsp4sDrY 8sSthVr0HwN+75o7t4COIpTBYroS+jtADfHOZcz6nt9gRrCXuUeNP/FhINxPBbl91iq0/x 1niTx+mKbS47JqE8tNYKRuQOSvENjtsBSwZwo2rqSuL3RybCoHTWdqKprmN7LThi3saCs8 G2e7T2ZodRenfTBDeHX1dkZKjKLTEDcEhvgGKAHDM4lOCH8VFmtiDgJYwSg6GA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=LhMSbePX; dmarc=pass (policy=none) header.from=gmail.com; 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: -3.33 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=LhMSbePX; dmarc=pass (policy=none) header.from=gmail.com; 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: 7BF7AABC1 X-Spam-Score: -3.33 X-Migadu-Scanner: scn1.migadu.com X-TUID: A88e9qwED1yN Ihor Radchenko writes: > Rudolf Adamkovi=C4=8D writes: > >> Let $r_i$ denote the \(i\)-th rotation of $t$ with a suffix of $\ell|t|$ >> characters deleted, for [=E2=80=A6] >> >> Me, if I could, I would pay money for this feature, for it would allow >> me to use $$ consistently, focusing on mathematics instead of markup >> idiosyncrasies of "rotation $i$" versus "\(i\)-th rotation". > > Would it improve things for you if we change how \(...\) _looks_ in Org > buffers? > > The problem with parsing is more than just supporting $i$-th and > similar. For example, AMS style guide explicitly advises against using > $i$-th in favour of $i$th [1]: > > Do not hyphenate =E2=80=9Cth=E2=80=9D expressions: xth, not x-th or x= th . > > We can theoretically make a change to support "-", but then it will be > logical to support $i$th as well. (If we don't some users will still be > confused after trying to write $i$th and then not getting the expected > results). In this question, it would make sense to implement > all-or-everything approach. Otherwise, confusion (like raised in this > thread) will be inevitable. > > However, from point of view of Org mode parser, supporting $i$th is a > nightmare. Remember that Org mode is _not_ LaTeX and we have to support > a lot more frivolous syntax (even in LaTeX, runaway $ is often a source > of cryptic compilation errors). Currently, we _must_ rely on heuristics > to determine $$-style latex fragments. I do not know any way to support > $$ syntax without creating deviations from LaTeX. Extending the > heuristics will not resolve the underlying ambiguity of $$ syntax, just > hide it within even more obscure cases. > > Given the raised concerns, may we solve the issue with too verbose > \(...\) unambiguous syntax using the following approach: > 1. Fontify \(...\) replacing the brackets with a single character. For > example: > > \(...\) -> =E2=81=85...=E2=81=86 > > 2. Provide convenient way to input \(\) brackets through > electric-pair-mode or trough org-cdlatex-mode. > > Best, > Ihor > > [1] https://www.ams.org/publications/authors/AMS-StyleGuide-online.pdf +1. Just my $0.02 worth - I think this is the right approach. Retaining support for $..$ doesn't seem feasible given all the complexities it brings with it. The main objections to the alternative appear to centre around readability and inconvenience of having to type additional characters or dealing with muscle memory use to $...$. These are essentially interface issues and I think we can largely address them using existing Emacs facilities. This will reduce the change impact to that sub-set of org users accustomed to $...$ while bringing the benefit of a cleaner and potentially more efficient parser to all org users. If we do deprecate support for $...$, it might also be a good idea to see if we can add a utility function which would make it easier for people to migrate existing documents to the new/alternative syntax. For the same reason it is hard to reliably parse $...$ syntax, we probably can't automate that transition, but we should be able to reduce the effort required to update existing documents.=20