emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Org emphasis markers inside src blocks causes incorrect fontification
Date: Thu, 16 Nov 2017 21:56:56 +0000	[thread overview]
Message-ID: <CAFyQvY2Eb63D35EmXBQg+q1ztaPCk4EzVRf2EOrmgAjOjZOxDA@mail.gmail.com> (raw)
In-Reply-To: <87bmk1vqtt.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 858 bytes --]

On Thu, Nov 16, 2017 at 4:47 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> At the moment, my suggestion would be to not mess with
> `org-emphasis-regexp-components'.
>

I stayed away from messing with that for the longest time, until a bug got
into me to always auto-fill the Org files (as it makes it easier to read
them in browser, etc.)

As I started auto-filling, I noticed that stuff like:

=====
Line 1 starts with /three words
italicized/, but the third word ends
up on the 2nd line.
=====

It wasn't always in my control to always begin and end emphasis on the same
line, and so resorted to tweaking org-emphasis-regexp-components. Overall
it works great, except for cases like these.

Again it's a font-locking bug, and thankfully doesn't impact the empasis
detection in exporters.

Would you please look into fixing this?
-- 

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 1413 bytes --]

  reply	other threads:[~2017-11-16 21:57 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
2017-11-16 21:56   ` Kaushal Modi [this message]
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=CAFyQvY2Eb63D35EmXBQg+q1ztaPCk4EzVRf2EOrmgAjOjZOxDA@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).