From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Org emphasis markers inside src blocks causes incorrect fontification
Date: Thu, 16 Nov 2017 22:47:26 +0100 [thread overview]
Message-ID: <87bmk1vqtt.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY0mtxu3gnB8+622Q7GKxeKGWWVHM_ebKPxunS+mxJ3aSA@mail.gmail.com> (Kaushal Modi's message of "Thu, 16 Nov 2017 20:08:20 +0000")
Hello,
Kaushal Modi <kaushal.modi@gmail.com> writes:
> I increase the number of consecutive lines to be parsed for Org emphasis to
> 20 lines using:
>
> =====
> (setcar (nthcdr 4 org-emphasis-regexp-components) 20) ;Up to 20 lines,
> (org-set-emph-re 'org-emphasis-regexp-components
> org-emphasis-regexp-components)
> =====
>
> With that set, I see that equal signs in source blocks falsely trigger the
> org-verbatim fontification. And I see this[1]. Notice the fontification in
> the attached image (link at bottom of this email).. The equal signs in the
> first src block initiate the org-verbatim fontification and that goes on
> till the equal signs in the next code block.. so Heading 2 shows up in
> org-verbatim face.
[...]
> Shouldn't the presence of org emphasis markers be ignored when inside src
> blocks?
It should.
Note that current fontification system only approximates the syntax of
the Org document. There are certainly more bugs like this one lurking in
the shadows.
At the moment, my suggestion would be to not mess with
`org-emphasis-regexp-components'.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-11-16 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 20:08 Org emphasis markers inside src blocks causes incorrect fontification Kaushal Modi
2017-11-16 21:47 ` Nicolas Goaziou [this message]
2017-11-16 21:56 ` Kaushal Modi
2017-11-17 23:30 ` Nicolas Goaziou
2017-11-20 17:34 ` Kaushal Modi
2017-11-25 14:42 ` 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=87bmk1vqtt.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
/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).