emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ian Dunn <dunni@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Org Emphasis Issues (Trunk)
Date: Wed, 14 Dec 2016 11:16:12 +0100	[thread overview]
Message-ID: <878tri95oz.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87twa7kvis.fsf@fastmail.fm> (Matt Lundin's message of "Tue, 13 Dec 2016 22:02:51 -0600")

Hello,

Matt Lundin <mdl@imapmail.org> writes:

> Ian Dunn <dunni@gnu.org> writes:
>
>>     I encountered these issues this morning when I updated Org from
>>     trunk (and reloaded it with C-c C-x !). I believe it's following
>>     commit "Split `org-emph-re' and `org-verbatim-re'". I've got 2
>>     issues:
>
>>     1. Nothing longer than one character has emphasis. I find changing
>>     the 4th element of org-emphasis-regexp-components ("body-regexp")
>>     to ".*?" fixes this.
>
> I cannot replicate this particular issue. Could you provide a minimal
> recipe for replicating?

I cannot either.

>>     2. Headings of level >= 3 are fontified as if they were
>>emphasized. I'm guessing org-do-emphasis-face is considering "***" as
>>an acceptable emphasis string.
>
> I can confirm the problems with headlines, though I can only replicate
> it with level 2 headings. (Are you perhaps using org-indent-mode?)
>
> With emacs -Q and the latest org from git, if I open the following file,
> "Subheading 1" appears in bold. If I delete "Subheading 2," the emphasis
> disappears.
>
> * First headline
> ** Subheading 1
> ** Subheading 2

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2016-12-14 10:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14  2:32 Bug: Org Emphasis Issues (Trunk) Ian Dunn
2016-12-14  4:02 ` Matt Lundin
2016-12-14 10:16   ` Nicolas Goaziou [this message]
2016-12-16  2:29     ` Ian Dunn

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=878tri95oz.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=dunni@gnu.org \
    --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).