From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Add support for $…$ latex fragments followed by a dash
Date: Fri, 28 Jan 2022 21:37:16 +0700 [thread overview]
Message-ID: <st0v2t$5tm$1@ciao.gmane.io> (raw)
In-Reply-To: <87mtjhnfd0.fsf@gmail.com>
On 28/01/2022 02:15, Tim Cross wrote:
>
> 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.
There is no point to discuss deprecation of $...$ and $$...$$ while
usage of such constructs is not discouraged by the org manual info
"(org) LaTeX fragmets" https://orgmode.org/manual/LaTeX-fragments.html
and by the compact guide https://orgmode.org/guide/Embedded-LaTeX.html
Even though org syntax says that support of these constructs ought to be
removed, users expect that they should work well.
next prev parent reply other threads:[~2022-01-28 14:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 16:42 [PATCH] Add support for $…$ latex fragments followed by a dash 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 [this message]
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
2022-01-27 19:11 ` Sébastien Miquel
-- strict thread matches above, loose matches on Subject: below --
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='st0v2t$5tm$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).