FWIW, I'm marking this bug as fixed in 38fbd161e4.
Thanks,
--
Bastien
Hello,
Sébastien Miquel 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'.
Hi,
Thanks for taking a look.
Afaict, the only difference between blank and [ \t] are some weird
unicode characters.
It isn't clear to me which one should be preferable and in what
situation. I couldn't find any reference to this in any documentation of
Org syntax.
I've replaced all
Hello,
Sebastien Miquel writes:
> (rx bol (group (zero-or-more blank) "#"
> (group (group (or (seq "+" (one-or-more (any
> "a-zA-Z")) (optional ":"))
> - space
> + blank
This looks
Hi,
The simple patch attached should fix this bug.
>From 27dd7e7cbde6650932342d302000914d72179327 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=A9bastien=20Miquel?=
Date: Tue, 15 Sep 2020 08:08:14 +0200
Subject: [PATCH] org.el (org-fontify-meta-lines-and-blocks-1): Fix meta lines
regexp
*
Hi Sebastian,
Sebastian Miele writes:
> Current master branch Org. Create an Org file with just the following
> two lines
>
> #
> * A
>
> Save, kill the buffer, find the file again. Then "* A" is in
> org-meta-line face.
For the record, the bug is still here in master.
I'm adding it to
Current master branch Org. Create an Org file with just the following
two lines
#
* A
Save, kill the buffer, find the file again. Then "* A" is in
org-meta-line face.
