Colon in the headline mistakenly treated as tag

[fullofcaffeine]

Hi there!

Thanks a lot for this! This is the best parser I've found so far, for org-mode. Some are too simplistic and others try to do too much and are too complex to be practical out-of-the-box (like orga). org-mode-parser has a great balance of features while being simple and practical to use! Perfect for my use case where I don't really need an AST but a way to make sense of and find org items :) Keep it up!

I've found a small problem, if the headline has a : in it, it will confuse the parser and it will think the headline is actually a tag. Example:

****** Feature: create and register new wordpress-powered (source) jekyll blog :toblog:
       yaya, cool
       markdown here

For this item, org-mode-parser thinks Feature: ... is a tag, besides :toblog:. If I remove the : in Feature, then it correctly detects it as a headline, and :toblog: as the sole tag.

[daitangio]

Thak you for the compliments and the bug report :) I will fix it during this holidays :)

Please excuse typs as Sent from my iPhone

Il giorno 14 dic 2018, alle ore 07:07, Marcelo Serpa [email protected] ha scritto:

Hi there!

Thanks a lot for this! This is exactly the best parser I've found so far, for org-mode. Some are too simplistic and others try to do too much and are too complex to be practical out-of-the-box (like orga). org-mode-parser has a great balance of features while being simple and practical to use! Perfect for my use case where I don't really need an AST but a way to make sense of and find org items :) Keep it up!

I've found a small problem, if the headline has a : in it, it will confuse the parser and it will thnink the headline is actually a tag. Example:

****** Feature: create and register new wordpress-powered (source) jekyll blog :toblog: yaya, cool markdown here For this item, org-mode-parser thinks Feature: ... is a tag, besides :toblog:. If I remove the : in Feature, then it correctly detects it as a headline, and :toblog: as the sole tag.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.