From: Titus von der Malsburg <malsburg@posteo.de>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Inline LaTeX formulae
Date: Wed, 06 May 2015 13:35:08 -0700 [thread overview]
Message-ID: <87vbg5xx4z.fsf@posteo.de> (raw)
In-Reply-To: <87wq0mc8bc.fsf@gmx.us>
[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]
On 2015-05-06 Wed 03:24, Rasmus wrote:
> Hi Titus,
>
> Titus von der Malsburg <malsburg@posteo.de> writes:
>
>> Parentheses are punctuation, so the $ in my example should be
>> interpreted as math delimiters. I think whoever wrote the code, simply
>> overlooked parentheses when implementing the punctuation part.
>
> I believe the problem is complicated.
I had a look at the code in org-element.el (thanks for the
pointer). There is clearly a bigger problem here: There is a
regexp listing all characters that must follow the final $ to make it
qualify as a math delimiter (whitespace, punctuation). As I suspected,
the parentheses are missing from that list (and adding them solves my
problem). However, a metric ton of other punctuation marks are missing
as well, Spanish question marks, curly/smart quotes, real dashes (a
minus is not a dash!), …, even the exclamation mark is missing.
If syntax tables allow a proper solution, great. I understand that
syntax tables have a different meaning in different modes but does that
matter? We’re only concerned about org-mode, right? Are there
scenarios where the org parser is used in a non-org-mode buffer?
I also saw that the commit that introduced the problem had the following
description:
Avoid using slow regexp.
So if the problem is only due to mistaken optimization, it would perhaps
be best to just revert to the previous code.
Titus
> In principal you could change the regexp in
> org-element-latex-fragment-parser to something like
>
> "\\(\\s.\\|\\s-\\|\\s)\\|\\s\"\\|\\s_\\)"
>
> You'd only be relying on syntax tables, which I believe is what you are
> suggesting. But this is also dangerous, see e.g. the recent change of
> org-string-nw-p which previously relied on "\\S" cf.:
>
> http://article.gmane.org/gmane.emacs.orgmode/95473
>
>> This should be fixed.
>
> Patches welcome. You could try to submit a patch where you add closing
> parenthesis characters.
>
> It could even be patches to org.texi!
>
> Thanks,
> Rasmus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-05-06 20:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 20:14 Inline LaTeX formulae Titus von der Malsburg
2015-05-05 20:23 ` Rasmus
2015-05-05 20:27 ` Marcin Borkowski
2015-05-05 21:32 ` Titus von der Malsburg
2015-05-05 22:56 ` Marcin Borkowski
2015-05-06 10:24 ` Rasmus
2015-05-06 20:35 ` Titus von der Malsburg [this message]
2015-05-07 7:42 ` Eric S Fraga
2015-05-07 18:00 ` Titus von der Malsburg
2015-05-07 20:00 ` Nicolas Goaziou
2015-05-08 19:52 ` Titus von der Malsburg
2015-05-08 21:40 ` Nicolas Goaziou
2015-05-08 22:25 ` Titus von der Malsburg
2015-05-09 8:01 ` Nicolas Goaziou
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=87vbg5xx4z.fsf@posteo.de \
--to=malsburg@posteo.de \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).