From: Greg Minshall <minshall@umich.edu>
To: "Colin Baxter 😺" <m43cap@yandex.com>
Cc: "Juan Manuel Macías" <maciaschain@posteo.net>,
"Sébastien Miquel" <sebastien.miquel@posteo.eu>,
orgmode <emacs-orgmode@gnu.org>, Timothy <tecosaur@gmail.com>
Subject: Re: Depreciating TeX-style LaTeX fragments
Date: Sun, 16 Jan 2022 07:16:51 -0800 [thread overview]
Message-ID: <3365676.1642346211@apollo2.minshall.org> (raw)
In-Reply-To: <87v8yju4fb.fsf@yandex.com>
Colin,
> > Colin Baxter writes:
> >> Ah, LaTeX3 - whatever happened to that?
...
> Yes, I know. My remark was tongue in cheek.
which leaves open whether your tongue was already in your cheek at:
> Indeed. Compare something like
>
> $g=\lim_{\delta m\to 0}(\delta F/\delta m)$
>
> with
>
> \(g=\lim_{\delta m\to 0}(\delta F/\delta m)\)
?
additionally, fwiw, i was a long time '$...$'-user. at one point i was
betrayed, and switched to '\(...\)'. it may be more to type (i hadn't
noticed the suggestion Eric just sent in), but i liked the
repeatability. and, in terms of parsing, i'm very sympathetic to having
"directional" end markers.
cheers, Greg
next prev parent reply other threads:[~2022-01-16 15:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 18:02 Org Syntax Specification Timothy
2022-01-15 12:40 ` Sébastien Miquel
2022-01-15 16:36 ` Depreciating TeX-style LaTeX fragments (was: Org Syntax Specification) Timothy
2022-01-16 8:08 ` Sébastien Miquel
2022-01-16 9:23 ` Depreciating TeX-style LaTeX fragments Martin Steffen
2022-01-16 9:46 ` Colin Baxter 😺
2022-01-16 11:11 ` Tim Cross
2022-01-16 13:26 ` Juan Manuel Macías
2022-01-16 14:43 ` Colin Baxter 😺
2022-01-16 15:16 ` Greg Minshall [this message]
2022-01-16 17:45 ` Rudolf Adamkovič
2022-01-16 12:10 ` Eric S Fraga
2022-01-16 14:30 ` Anthony Cowley
2022-01-18 0:54 ` Org Syntax Specification Tom Gillespie
2022-01-18 12:09 ` Ihor Radchenko
2022-01-19 1:22 ` Tom Gillespie
2022-01-19 11:58 ` 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=3365676.1642346211@apollo2.minshall.org \
--to=minshall@umich.edu \
--cc=emacs-orgmode@gnu.org \
--cc=m43cap@yandex.com \
--cc=maciaschain@posteo.net \
--cc=sebastien.miquel@posteo.eu \
--cc=tecosaur@gmail.com \
--subject='Re: Depreciating TeX-style LaTeX fragments' \
/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).