@seylerius This approach handles a variety of potential characters before the tags, at the expense of speed, since it parses every single character on the header line to get around regex greediness.

(def headlines
  (insta/parser
   "<S> = token (ows token)*
    <token> = section / content
    section = h (ows content)*
    h = ows stars <#'\\s+'> (todo <#'\\s+'>)? title
    <title> = (#'.'+ ws-line? tags) / #'.+'
    stars = #'^\\*+'
    todo = #'TODO|DONE'
    tags = <':'> (tag <':'>)+ ws
    <tag> = #'[a-zA-Z0-9_@]+'
    <ws> = <#'[\r\n\\s]+'>
    <ws-line> = <#'[^\r\n\\S]+'>
    <ows> = <#'\\s*'>
    <content> = #'^([^*].*)?'"))

Probably be an uncommon usage, but technically legal, @aengelberg. Probably ought to do something like this. Hmmm.

Yeah, that works. Definitely going to need the follow-up concatenation I was planning on.

Okay, another puzzle for ya, @aengelberg. In this latest push, why isn't priority getting picked up? I've cleaned up some of the names and added an overall parse function that takes a string, to simplify testing.

(parse (slurp "")) should work for testing.

(Thanks a ton for the help, BTW)

A priority is defined as a letter preceded by a pound sign, in square brackets. [#A] or [#z], for example.

Lol, whoops. Reversed my pound sign and bracket

@aengelberg: Can you help me figure out why the parsed sample is not registering as compliant hiccup to insta/transform?

Okay, I see that it's looking for a root node. Tried to unhide the document node, but it's not showing up.

@seylerius lemme take a look

Thanks.

@seylerius what's the repro case?

(parse (slurp "")) returns a seq, not a vector with a root node.

looks like function reducing doesn't exist

CompilerException java.lang.RuntimeException: Unable to resolve symbol: reducing in this context

Cleared that up.

Thanks

Still isn't giving me a root node, though.

([:author..., rather than [:document [:author...

interesting. transforming on a sequence should work. I think you may have found a bug in instaparse.

The fact that there's a string in the uppermost level is what's throwing it off.

Fascinating

@aengelberg: Maybe make strings pass straight through transform?

I can confirm that's a bug

Yeah, that's what I'm about to do.

Awesome

@seylerius https://github.com/Engelberg/instaparse/pull/145

oops, didn't link properly... edited

Downloaded, testing.

It works! Thanks, @aengelberg!

@aengelberg: Yep, that worked perfectly. What's the release schedule on that, out of curiosity?

In the meantime, I'm moving on to adding additional parsers (drawers, blocks, footnotes, lists, tables, to name a few).

@seylerius For instaparse we prefer to merge fixes, bump version numbers / changelogs, and deploy to clojars all at once. And only my dad has the power to do the last part. So whenever he gets around to doing that is when I'd expect to see the latest version. Should be sometime today.

Shiny. Looking forward to it. Also, shiny that y'all are a father-son team. Be cool if one of my kids coded with me (after I have some).

Thanks. It's fun! You may enjoy the Clojure/west 2014 instaparse talk, which provides some backstory on the collaboration

Awesome. I'll check it out