From: Max Nikulin <manikulin@gmail.com> To: emacs-orgmode@gnu.org Subject: Re: [PATCH] Add support for $…$ latex fragments followed by a dash Date: Sun, 30 Jan 2022 22:28:38 +0700 [thread overview] Message-ID: <st6ar8$tjk$1@ciao.gmane.io> (raw) In-Reply-To: <8735l7olmj.fsf@gmail.com> On 28/01/2022 23:37, Timothy wrote: > >> There is no point to discuss deprecation of $…$ and ... while usage of >> such constructs is not discouraged by the org manual > > Isn’t the point of discussing depreciation now that we’d change the manual etc. > to discourage it? 😛 It is funny that nobody have checked what the manual actually states: > Text within the usual LaTeX math delimiters. To avoid conflicts with > currency specifications, single ‘$’ characters are only recognized as > math delimiters if the enclosed text contains at most two line breaks, > is directly attached to the ‘$’ characters with no whitespace in > between, and if the closing ‘$’ is followed by whitespace, punctuation > or a dash. For the other delimiters, there is no such restriction, so ^^^^^^ > when in doubt, use ‘\(...\)’ as inline math delimiters. I have no idea whether it ever worked in such way. So either the manual must be updated or a fix must be committed. False positive with the proposed patch: > Balance decreased from $10 to negative value ($-2 approximately) certainly it is more rare than $n$-th valid case. >>> 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. > > Tim, as mentioned before I’m strongly in favour of a ~half decade transition > including utility functions to shift existing TeX constructs to LaTeX, and > adding warnings, well before dropping support. That period should be started when manual is updated. Functions updating old file to the current syntax is an interesting idea, but it assumes a copy of org-element as it was in that old org version.
next prev parent reply other threads:[~2022-01-30 15:29 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 16:42 Sébastien Miquel 2022-01-25 7:56 ` Eric S Fraga 2022-01-25 10:32 ` Sébastien Miquel 2022-01-26 17:15 ` Rudolf Adamkovič 2022-01-27 8:28 ` Ihor Radchenko 2022-01-27 19:15 ` Tim Cross 2022-01-28 14:37 ` Max Nikulin 2022-01-28 16:37 ` Timothy 2022-01-30 15:28 ` Max Nikulin [this message] 2022-02-01 14:26 ` Max Nikulin 2022-01-27 19:34 ` Sébastien Miquel 2022-02-01 21:00 ` Rudolf Adamkovič 2022-02-02 2:48 ` João Pedro de Amorim Paula 2022-02-06 19:45 ` Rudolf Adamkovič 2022-02-07 0:00 ` Tim Cross 2022-01-26 6:33 ` Tom Gillespie 2022-01-26 17:49 ` Sébastien Miquel 2022-01-26 21:49 ` Tom Gillespie 2022-01-27 19:11 ` Sébastien Miquel 2022-01-25 18:09 Goran Zuzic 2022-01-27 18:54 autofrettage
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='st6ar8$tjk$1@ciao.gmane.io' \ --to=manikulin@gmail.com \ --cc=emacs-orgmode@gnu.org \ --subject='Re: [PATCH] Add support for $…$ latex fragments followed by a dash' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).