Can’t parse trivial .org file about org-web HOT 11 OPEN

I looked into that parser but had already done so much work on my own by that point that I opted not to use it. One day it might make sense to swap it in, though.

My philosophy behind org-web has always been a sort of progressive enhancement. That is, I've wanted to allow editing the raw headers as plain text, but progressively over time support more org features natively (like TODOs, checklists, timestamps, etc). I think I just missed this case of allowing text before a header like this.

from org-web.

I just tried it with an empty file, same result.

from org-web.

@tokuchan I have done a little work on the parser, so I can tell you from memory what's the issue. What's "trivial" and what is not is itself not trivial^^

org-web expects a file to start with either these keywords #+TODO, #+TYP_TODO or with a header (indicated by a *).

I have opened a separete issue two weeks ago that's going in a similar direction: #55

from org-web.

from org-web.

from org-web.

Hey @tokuchan, thanks for the report! org-web was largely built around my own particular use cases, which is one monolithic org file. Adding support for creating new files has been a rather commonly requested feature, however. Is that your use case here?

from org-web.

As I mentioned in #71, org allows content before the first headline, so opening such a file should ideally be supported by org-web. I think many people stumble on the complex syntax of org, which has no real formal definition except the elisp-implementation (even though this "draft" page on worg seems to document it well).
Many people have attempted to write more or less complete parsers as well, for example: https://www.reddit.com/r/orgmode/comments/7wjmwr/orga_the_ultimate_orgmode_parser_in_javascript/

Would there be a point of using something like this in org-web? Otherwise I guess it’s a quite pragmatic solution to parse the basics, and then allow free-text editing of other things in the sections. In my understanding, org-web isn’t supposed to enable all org mode workflows, but is mainly aimed towards the planning functionality.

from org-web.

I noticed that text content before the first * section (valid org-mode content, as far as I know) is not available in the web app. It looks like that is a subset of this issue, is that right?

from org-web.

Ah, yep, that is probably contained in this issue. I didn't realize you could put valid org-mode content before the first header.

from org-web.

Definitely! After all, one has to be able to define things like properties and todo keywords. Speaking of which, how much work would it take to become able to parse custom todo keywords?

from org-web.

Ah I think I misunderstood what "valid content" was in this context. org-web actually already does support custom todo keywords, @tokuchan!

In the help file (Settings icon in the top right corner > Help), check out the third header under Actions > Todos (https://github.com/DanielDe/org-web/blob/master/sample.org#L2 and https://github.com/DanielDe/org-web/blob/master/sample.org#L18)

from org-web.