Re: [PATCH] org-manual.org: $n$-th is not math

2023-03-15 Thread Rudolf Adamkovič
Bummer the dash will not be supported. :(

(I am super-happy with $...$, except for the dash case.)

Max Nikulin  writes:

> Prefer =\(...\)= for + inline snippets.

Fragments, not snippets.  Right?

> The =$...$= alternative has some restrictions and may be source of confusion.

I am not a native speaker, but "may be a source of confusion" (note the "a")
sounds more correct.

Rudy
-- 
"It is no paradox to say that in our most theoretical moods we may be
nearest to our most practical applications."
-- Alfred North Whitehead, 1861-1947

Rudolf Adamkovič  [he/him]
Studenohorská 25
84103 Bratislava
Slovakia



Re: [PATCH] org-manual.org: $n$-th is not math

2023-03-15 Thread Loris Bennett
Max Nikulin  writes:

[snip (17 lines)]

> Detection of "$-" as closing math delimiters is broken since 2015 as a

[snip (44 lines)]

Detection of "$-" as closing math delimiters has been broken since 2015 as a

-- 
This signature is currently under constuction.



[PATCH] org-manual.org: $n$-th is not math

2023-03-15 Thread Max Nikulin

Hi,

yesterday an issue with $n$-th TeX markup was risen again. I think, the 
manual should not declare that it is supported. It is broken for a 
decade. So \(n\)-th should be suggested instead.From 6feb228a1bcc485441bab707771e6d87a3d69671 Mon Sep 17 00:00:00 2001
From: Max Nikulin 
Date: Wed, 15 Mar 2023 19:08:37 +0700
Subject: [PATCH] org-manual.org: $n$-th is not math
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* doc/org-manual.org (LaTeX fragments): Do not state that dash is
allowed after single "$" math delimiter and recommend "\(...\)".

Detection of "$-" as closing math delimiters is broken since 2015 as a
side effect of using punctuation class in regular expressions while
dash is considered as a word constituent.  See commits
6779f8f424 and c0369a7984.  Bring the manual in accordance to the code
instead of allowing "($-2 change)" false positives.  Users who do not
like "\(...\)" constructs may use a helper for typing it and may change
how it is displayed to minimize visual noise by fontification, see

- Eric S Fraga to emacs-orgmode. Re: Depreciating TeX-style LaTeX
  fragments. Sun, 16 Jan 2022 12:10:30 +.
  <https://list.orgmode.org/87k0ezdgp5@ucl.ac.uk>
- Ihor Radchenko to emacs-orgmode. Re: [PATCH] Add support for $…$ latex
  fragments followed by a dash. Thu, 27 Jan 2022 16:28:10 +0800.
  <https://list.orgmode.org/87r18t7fc5.fsf@localhost>
---
 doc/org-manual.org | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index 1c97d6aa8..7bb1ac637 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -11152,14 +11152,14 @@ *** LaTeX fragments
   =\begin= statement appears on a new line, preceded by only
   whitespace.
 
-- 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.
+- Text within the usual LaTeX math delimiters.  Prefer =\(...\)= for
+  inline snippets.  The =$...$= alternative has some restrictions and
+  may be source of confusion.  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 or
+  punctuation (but not a dash).
 
 #+texinfo: @noindent
 For example:
-- 
2.25.1