From: "Colin Baxter 😺" <m43cap@yandex.com>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: "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 14:43:36 +0000 [thread overview]
Message-ID: <87v8yju4fb.fsf@yandex.com> (raw)
In-Reply-To: <871r17g6b4.fsf@posteo.net> ("Juan Manuel Macías"'s message of "Sun, 16 Jan 2022 13:26:39 +0000")
>>>>> Juan Manuel Macías <maciaschain@posteo.net> writes:
> Colin Baxter writes:
>> Ah, LaTeX3 - whatever happened to that?
> If you're a LaTeX user, you're already using LaTeX3 to a very high
> extent, even if you don't see it. The current idea is not to
> replace LaTeX2e with LaTeX3 as a new version, but to gradually
> incorporate elements of LaTeX3 into the LaTeX kernel, like the new
> syntax, xparse, etc. LaTeX3 is already present in many aspects of
> LaTeX, and that is an undeniable advance. If anyone is interested
> in the state of the art, this short talk by Frank Mittelbach at
> TUG 2020 is very illustrative:
Yes, I know. My remark was tongue in cheek.
next prev parent reply other threads:[~2022-01-16 14:44 UTC|newest]
Thread overview: 22+ 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 😺 [this message]
2022-01-16 15:16 ` Greg Minshall
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
2022-09-25 9:09 ` Bastien
2022-09-25 21:28 ` Rohit Patnaik
2022-11-26 2:41 ` Ihor Radchenko
2022-11-26 6:24 ` Bastien
2022-11-26 6:05 ` 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=87v8yju4fb.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
--cc=sebastien.miquel@posteo.eu \
--cc=tecosaur@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).