From: Dominik Schrempf <dominik.schrempf@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Hyphen after LaTeX fragments
Date: Tue, 21 Mar 2023 17:39:50 +0100 [thread overview]
Message-ID: <87v8iut5ph.fsf@gmail.com> (raw)
In-Reply-To: <m2jzzagizo.fsf@me.com>
I like the $...$ syntax, but since it is not fully supported, I rather
use \(...\) consistently; I do not really care.
Maybe the best thing to do is drop support for $...$ completely?
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."
Dominik
Rudolf Adamkovič <salutis@me.com> writes:
> iemacs@gmail.com writes:
>
>> You can write \(n\)-dimensional space.
>
> ROFL.
>
> My apologies for the laugh, but this question will keep coming over and
> over and over until the end of times. Clearly, there is a need for the
> dash, and given the quality and syntactic stability of TeX, the problem
> is not going anywhere ... ever.
>
> Rudy
next prev parent reply other threads:[~2023-03-21 16:44 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 [this message]
2023-03-22 12:25 ` Ihor Radchenko
2023-03-22 12:35 ` Dominik Schrempf
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:
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=87v8iut5ph.fsf@gmail.com \
--to=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).