From: Tom Gillespie <email@example.com> To: firstname.lastname@example.org Cc: emacs-orgmode <email@example.com> Subject: Re: [PATCH] Add support for $…$ latex fragments followed by a dash Date: Wed, 26 Jan 2022 16:49:58 -0500 [thread overview] Message-ID: <CA+G3_PO8dwjeqF7XshP0QNrECGMPCzei9aZi7Q8_juFSHfq3Sw@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> > The change is local and minor. We can't know that. Consider for example someone that has the following line somewhere in their files. #+begin_src org I spent $20 on food and was paid$-10 dollars by friends so I am down $10. #+end_src Yes =paid$-10= is probably a typo that should have a space in between, but it could still be in a file and cause an issue. The more likely case would be of someone that has $ in the name of a variable that also uses dashes. For example if I have a list of variable names such as #+begin_src org Text a $A_BASH_VAR Text b some-$-lisp-var #+end_src The proposed change would break any file with a pattern like this. We have no way of seeing every org file that users have written so we don't know the extent of the impact, and thus have to assume that there would be some impact. Making such a change with an unknown blast radius in the midst of considering removing support for that syntax altogether is inviting disaster. Best, Tom
next prev parent reply other threads:[~2022-01-26 21:51 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 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 [this message] 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=CA+G3_PO8dwjeqF7XshP0QNrECGMPCzei9aZi7Q8_juFSHfq3Sw@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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).