From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: The + character creating strike-through markup within in-line literal / code blocks
Date: Mon, 25 Jun 2018 08:29:42 -0400 [thread overview]
Message-ID: <87y3f3vykp.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 20180625055244.63biztp4zjhgfhha@s70206.gridserver.com
John Magolske <listmail@b79.net> writes:
>> It happens because syntax coloring is a bit dumb. It uses regexps but
>> not the parser. However, if you try, e.g., to export the document, the
>> plus signs will not be treated as markers.
>
> Ok, just tried org-html-export-as-html and see it renders properly
> in html:
>
> ... expression <code>(x +. y)</code> the <code>+.</code> is ...
>
> but I feel like there's a bug in the regex, that the =code= and
> ~verbatim~ marker characters should be able to prevent any other
> marker characters bracketed by them from causing highlighting.
Regexes recognize what is called a "regular" language which obeys a
context-free grammar. Although modern regexes are a bit more powerful,
it is still difficult (and computationally expensive) to have them
recognize context (e.g. figure out that we are now inside a verbatim
environment and so we need to do things differently). That's why
context-sensitive grammars require parsers.
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
prev parent reply other threads:[~2018-06-25 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 7:57 The + character creating strike-through markup within in-line literal / code blocks John Magolske
2018-06-24 8:24 ` Nicolas Goaziou
2018-06-25 5:52 ` John Magolske
2018-06-25 12:29 ` Nick Dokos [this message]
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=87y3f3vykp.fsf@alphaville.usersys.redhat.com \
--to=ndokos@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).