From: Ihor Radchenko <yantar92@posteo.net>
To: Daniel Fleischer <danflscr@gmail.com>
Cc: Justin Silverman <jsilve24@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] issue with texmathp [9.6 (release_9.6-22-g78d283 @ /home/jds6696/.emacs.d/straight/build/org-mode/)]
Date: Sat, 07 Jan 2023 15:03:57 +0000 [thread overview]
Message-ID: <87v8lijsiq.fsf@localhost> (raw)
In-Reply-To: <m2358mzc7z.fsf@gmail.com>
Daniel Fleischer <danflscr@gmail.com> writes:
> BTW, I haven't follow any discussions about org syntax and math
> environments inside org (the use of \...[\] instead $...$ etc.) These
> usecases I mentioned are what I'm used to and perhaps they are not
> consistent with changes made to the org syntax, demanding every math
> should be inside a math environment for easier parsing and you still
> managed to solve that without all the previous regexps.
We did not make changes to syntax. Just decided to aim towards less
visibility of $..$ in the documentation.
At the end, we don't want to break existing documents, just to
discourage people from using $...$ syntax.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-01-07 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 16:48 [BUG] issue with texmathp [9.6 (release_9.6-22-g78d283 @ /home/jds6696/.emacs.d/straight/build/org-mode/)] Justin Silverman
2022-12-10 9:25 ` Ihor Radchenko
2022-12-13 19:48 ` Justin Silverman
2022-12-14 8:15 ` Ihor Radchenko
2022-12-18 15:17 ` Justin Silverman
2023-01-06 10:45 ` Daniel Fleischer
2023-01-07 11:23 ` Ihor Radchenko
2023-01-07 13:49 ` Daniel Fleischer
2023-01-07 15:03 ` Ihor Radchenko [this message]
2023-01-11 11:00 ` Ihor Radchenko
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=87v8lijsiq.fsf@localhost \
--to=yantar92@posteo.net \
--cc=danflscr@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jsilve24@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).