From: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
To: Org Mode List <emacs-orgmode@gnu.org>, Eric S Fraga <e.fraga@ucl.ac.uk>
Subject: Re: [PATCH] Add support for $…$ latex fragments followed by a dash
Date: Tue, 25 Jan 2022 10:32:36 +0000 [thread overview]
Message-ID: <96431eee-4b2b-8faf-e89a-bda258130341@posteo.eu> (raw)
In-Reply-To: <874k5si6zh.fsf@ucl.ac.uk>
Hi,
Eric S Fraga writes:
> But is not necessary (and further complicates the issue of support $...$
> in org as recently discussed on this list) as you can simply type
> \(n\)-th?
What complication are you referring to, precisely ?
The patch is fairly trivial, and a similar extension was already
implemented by Nicolas in 2017[1]. Yes, the $…$ syntax is redundant,
but I do not think it follows that this change is unnecessary.
This patch should have no bearing on the possible deprecation of the
$…$ syntax.
[1]:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=c0369a798470763f8f3c69cf2079c3a194635feb
Regards,
--
Sébastien Miquel
next prev parent reply other threads:[~2022-01-25 10:34 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 [this message]
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
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=96431eee-4b2b-8faf-e89a-bda258130341@posteo.eu \
--to=sebastien.miquel@posteo.eu \
--cc=e.fraga@ucl.ac.uk \
--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).