From: Timothy <tecosaur@gmail.com> To: Max Nikulin <manikulin@gmail.com> Cc: emacs-orgmode@gnu.org Subject: Re: [PATCH] Add support for $…$ latex fragments followed by a dash Date: Sat, 29 Jan 2022 00:37:27 +0800 [thread overview] Message-ID: <8735l7olmj.fsf@gmail.com> (raw) In-Reply-To: <st0v2t$5tm$1@ciao.gmane.io> [-- Attachment #1: Type: text/plain, Size: 1240 bytes --] Hi Max, > 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? 😛 FWIW, I have an extra 2c to add: I think that there’s a danger in having $…$ /almost/ behave like LaTeX, as the closer it is the more surprising the edge cases are, and due to the nature of Org there will /always/ be a collection of edge cases with $…$. By comparison, \(…\) has much less ’surprising’ behaviour. >> 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. All the best, Timothy
next prev parent reply other threads:[~2022-01-28 17:18 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 [this message] 2022-01-30 15:28 ` Max Nikulin 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=8735l7olmj.fsf@gmail.com \ --to=tecosaur@gmail.com \ --cc=emacs-orgmode@gnu.org \ --cc=manikulin@gmail.com \ --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).