From: Max Nikulin <firstname.lastname@example.org> To: email@example.com Subject: Re: [PATCH] Add support for $…$ latex fragments followed by a dash Date: Tue, 1 Feb 2022 21:26:50 +0700 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> manual states: > >> 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. It is even more interesting. Support of dash likely was unintentionally lost in the following commit: https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=6779f8f424883ffd202e24cbd8bb4e241db294b0 that generalizes handling of punctuation, unfortunately dash and apostrophe are not always belong to punctuation symbols in *text* modes. That commit even updates manual to a less precise phrase, however .texi file only, so the change was lost. Nicolas later restored apostrophe in the commit c0369a798470763f8f3c69cf2079c3a194635feb > False positive with the proposed patch: > > > Balance decreased from $10 to negative value ($-2 approximately) > > certainly it is more rare than $n$-th valid case. > >> Tim, as mentioned before I’m strongly in favour of a ~half decade >> transition Half of decade already passed since dash after currency symbol was broken so maybe it is better to fix current state by updating the manual (including bugfix branch) and by adding some tests. P.S. It is deja vu, I almost certainly saw quite recent discussions whether punctuation may be handled in some regexps in more generic way. Consequences may be similar in respect to characters that are almost punctuation...
next prev parent reply other threads:[~2022-02-01 16:06 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 16:42 Sébastien Miquel 2022-01-25 7:56 ` Eric S Fraga 2022-01-25 10:32 ` Sébastien Miquel 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 [this message] 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 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 \ --firstname.lastname@example.org' \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] Add support for $…$ latex fragments followed by a dash' \ /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
Code repositories for project(s) associated with this 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).