emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dominik Schrempf <dominik.schrempf@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Hyphen after LaTeX fragments
Date: Wed, 22 Mar 2023 13:35:28 +0100	[thread overview]
Message-ID: <87r0tht0zl.fsf@gmail.com> (raw)
In-Reply-To: <87edphnfbl.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

> Dominik Schrempf <dominik.schrempf@gmail.com> writes:
>> Maybe the best thing to do is drop support for $...$ completely?
> We cannot do it. Otherwise, existing Org documents may be broken.

Well, and as detailed later in my mail, I meant deprecating support for
$...$. But thanks for pointing this out!

>> I quote the Org mode manual section about $...$ syntax:
>>     Text within the usual LaTeX math delimiters. To avoid conflicts with
>>     currency specifications, single ‘$’ characters are only recognized
>>     as math delimiters if the enclosed text contains at most two line
>>     breaks, is directly attached to the ‘$’ characters with no
>>     whitespace in between, and if the closing ‘$’ is followed by
>>     whitespace, punctuation or a dash. For the other delimiters, there
>>     is no such restriction, so when in doubt, use ‘\(...\)’ as inline
>>     math delimiters.
>> 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?

  reply	other threads:[~2023-03-22 12:39 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 [this message]
2023-03-22 13:02           ` Ihor Radchenko
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:

  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=87r0tht0zl.fsf@gmail.com \
    --to=dominik.schrempf@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \


* 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


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).