From: Ihor Radchenko <yantar92@posteo.net>
To: Dominik Schrempf <dominik.schrempf@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Hyphen after LaTeX fragments
Date: Wed, 22 Mar 2023 13:02:41 +0000 [thread overview]
Message-ID: <875yatndla.fsf@localhost> (raw)
In-Reply-To: <87r0tht0zl.fsf@gmail.com>
Dominik Schrempf <dominik.schrempf@gmail.com> writes:
>>> I think this is HIGHLY confusing. I think we should write something
>>> along the lines: "Do not use $...$. Only for reasons of backwards
>>> compatibility, $...$ syntax is partly (!) supported."
>>
>> Feel free to provide a patch.
>
> I think that a change in the documentation alone is insufficient. We
> need to make sure that all current and future maintainers of org-latex
> are aware of the decision to deprecate $...$ (if we make this decision).
> How do we do that?
$...$ is a part of Org markup spec.
We can document the deprecation in
https://orgmode.org/worg/org-syntax.html#LaTeX_Fragments and
possibly as a comment in source code (org-element.el).
This is still under discussion in https://list.orgmode.org/orgmode/87r195nt2g.fsf@localhost/
--
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-03-22 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 15:15 Hyphen after LaTeX fragments Yuchen Guo
2023-03-20 1:54 ` iemacs
2023-03-21 16:35 ` Rudolf Adamkovič
2023-03-21 16:39 ` Dominik Schrempf
2023-03-22 12:25 ` Ihor Radchenko
2023-03-22 12:35 ` Dominik Schrempf
2023-03-22 13:02 ` Ihor Radchenko [this message]
2023-03-21 17:22 ` Yuchen Guo
2023-03-22 12:36 ` Ihor Radchenko
2023-04-17 14:01 ` Ihor Radchenko
2023-04-17 15:29 ` Dominik Schrempf
-- strict thread matches above, loose matches on Subject: below --
2023-03-13 19:44 Yuchen Guo
2023-03-14 7:02 Yuchen Guo
2023-03-14 7:04 ` Dominik Schrempf
2023-03-14 11:12 ` Max Nikulin
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=875yatndla.fsf@localhost \
--to=yantar92@posteo.net \
--cc=dominik.schrempf@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).