emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
Cc: bzg@gnu.org, emacs-orgmode@gnu.org, sebastian.miele@gmail.com
Subject: Re: [PATCH] Bug: Fontification: Heading following a comment
Date: Wed, 16 Sep 2020 21:44:40 +0200	[thread overview]
Message-ID: <87v9gd1p7b.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <d9752975-0022-babf-afa3-28a0207ede3f@posteo.eu> (=?utf-8?Q?=22S=C3=A9bastien?= Miquel"'s message of "Wed, 16 Sep 2020 08:30:36 +0200")


Sébastien Miquel <sebastien.miquel@posteo.eu> writes:

> It isn't clear to me which one should be preferable and in what
> situation.

It is [ \t] almost everywhere, as shown in the code base. The only
exception I know about is when we need to escape with zero-width space,
e.g., in `org-emphasis-regexp-components'.

> I couldn't find any reference to this in any documentation
> of Org syntax.

It should be in the document describing the syntax. If it is not there,
it should be added.

> I've replaced all instances of blank with (any " \t") in this function
> (that's the only instances in org.el).
> The attached patch fixes the original issue.

Thank you. I applied your patch.

Nicolas Goaziou

  reply	other threads:[~2020-09-16 19:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 11:59 Bug: Fontification: Heading following a comment Sebastian Miele
2020-09-04  8:44 ` Bastien
2020-09-15  6:26   ` [PATCH] " Sebastien Miquel
2020-09-15 12:05     ` Nicolas Goaziou
2020-09-16  6:30       ` Sébastien Miquel
2020-09-16 19:44         ` Nicolas Goaziou [this message]
2020-09-23  8:02     ` Bastien

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:

  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=87v9gd1p7b.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastian.miele@gmail.com \
    --cc=sebastien.miquel@posteo.eu \


* 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


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).