From: Nicolas Goaziou <email@example.com>
To: Marcin Borkowski <firstname.lastname@example.org>
Cc: Org-Mode mailing list <email@example.com>
Subject: Re: org-block-regexp questions
Date: Thu, 22 Jan 2015 18:48:27 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Marcin Borkowski's message of "Thu, 22 Jan 2015 01:36:13 +0100")
Marcin Borkowski <firstname.lastname@example.org> writes:
> I'm studying org-block-regexp. One thing that bugs me is this part:
> It suggests to me that the underscore after "begin" might be optional;
> but a quick experiment with the exporter shows that this is not the
This is the case for dynamic blocks
(info "(org) Dynamic blocks")
> Next, this part:
> \\([^ \n]+\\)
> would suggest that TAB is a valid part of the name of the block.
> Strange, isn't it?
It is. "\\(\\S-+\\)" would be more appropriate I think (this is also
what is used in "org-element.el").
> Finally, the rationale behind
> escapes me completely. What's the use of groups nested like this?
This looks like a plain bug, a minor one, tho. Before fixing it, Someone
has to make sure it doesn't break matching groups somewhere.
prev parent reply other threads:[~2015-01-22 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 0:36 org-block-regexp questions Marcin Borkowski
2015-01-22 17:48 ` Nicolas Goaziou [this message]
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 \
* 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).