From: Nicolas Goaziou <firstname.lastname@example.org>
To: Anders Johansson <email@example.com>
Subject: Re: Bug? Changed behaviour makes tags in headlines without a title parsed as the title
Date: Fri, 10 Apr 2015 18:24:07 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <552530AE.email@example.com> (Anders Johansson's message of "Wed, 08 Apr 2015 15:44:14 +0200")
Anders Johansson <firstname.lastname@example.org> writes:
> I have been using "degenerate" inlinetasks with empty titles but many
> tags for implementing a kind of coding scheme for coding texts for
> qualitative data analysis. Like this:
> Some text that I want to tag (The inlinetask in my scheme refers to
> the paragraph above it)
> *************** :tag1:tag2:tag3:
> Other text (no inlinetask-END, mostly)
> Building org from the master branch, I recently noticed a changed
> behaviour in that these tags as are not parsed as tags but instead as
> the title, meaning my exports don't work as expected (and possibly
> other things, but searching for tags etc.doesn't seem to be affected.
> Those functions don't use org-element perhaps?).
> As far as I could see, this comes from the changes in commit
> 98ee73: org-element: Avoid `org-element-parse-secondary-string',
> where tags are matched with the regexp:
> (org-re "[ \t]+\\(:[[:alnum:]_@#%:]+:\\)[ \t]*$")
> which needs whitespace "after" the non-existent title.
> I haven't checked all the different changes going on in org-element though.
> I don't know if this changed behaviour is intended. Otherwise I guess
> it's a bug.
Empty headings are a pathological case. What if I want to write
? Your interpretation prevents that.
Of course, Org is expected to be consistent. However I'm not convinced
supporting empty headlines with tags is a good thing.
next prev parent reply other threads:[~2015-04-10 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 13:44 Bug? Changed behaviour makes tags in headlines without a title parsed as the title Anders Johansson
2015-04-10 16:24 ` Nicolas Goaziou [this message]
2015-04-10 19:47 ` Anders Johansson
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).