Question about valid input

[AndreasEisele]

Dear orgmunge team,

I was quite happy to discover orgmunge because I need exactly this functionality, so I installed it and started to try it out.
Thanks a lot for providing it!

However, I quickly ran into two behaviors where I don't know they are bugs or features, so any hint on the expected behavior would be welcome.

Firstly, I had a file where the initial section is not under any header but starts with plain text. The parser fails to accept this input while reading the first line.
Secondly, I had a line that reads as follows:
**** TODO 30 XYZ (10 DONE)
which also makes the parser fail. It works however if DONE is written (partly) in lowercase. Alas, even a longer word that starts with DONE leads to parsing failure.

Clearly, I can work around these problems by starting the file with a header and avoiding keywords as part of my text.
I just wanted to know whether maybe I installed a partly obsolete version and I would obtain different behavior from a more recent version or perhaps a cleaner setup.

In case it matters: my setup uses ply version 3.11, while the orgmunge does not seem to contain any version information.

Thanks a lot in advance for any insights on this matter!

Best regards, Andreas

[durableOne]

Hello @AndreasEisele,

Please send examples of the different cases (what was rejected and what was accepted by the parser). I don't think this should depend on the PLY version. It sounds like an implicit assumption that the parser is making about how an Org file should be structured.

[durableOne]

The commit I just pushed should fix the problem of having a todo keyword in your title. Please check that it's gone now. Regarding your other issues:

1. I wasn't able to reproduce the issue of a file having content without a heading. I tried to parse a file that had only one line: "Hello, world!" and it parses correctly for me. Please share a minimal example that fails to parse with this issue.
2. When you showed an example with a level-4 heading I just wanted to make sure that that heading is embedded in a hierarchy of levels 1 through 3 above it. If it isn't it will still fail to parse for you. Even though it's acceptable Org, I made the choice to not accept headings that skip levels so that the tree structure is more uniform.