The closest thing that I would have for an agenda would be to have a defined format for the org file itself. I would like to see the org community adopt a format for the org file, and a set of core functions (dealing with manipulating files, nodes, and properties) that behave in a defined fashion. Beyond that, it is basically up to the interface / library how it behaves based on the content of the file.

Update: It looks like someone else may have some similar thoughts.

Thats quite abstract and overwhelming.

IMHO formulating concrete use cases and goals is the first step for improvement.

Producing POD is pretty concrete, and not far from being sufficiently done.

What do you want to produce? Do you want to support all export formats emacs knows?

I'm not such a heavy org-mode user like you are, you need to formulate your needs.

Cheers Rolf

With this one-off script, no. The script is good at what it does. My comments were only things that jumped out as low-hanging fruit. In fact, beyond those couple of changes, I would probably not make any other changes to this.

My goal for processing org-mode files with Perl (not this script) would be as I listed above - manipulating the files, nodes, and properties / drawers. educated_foo stated below, "only org-mode can parse Org". I agree with that mostly. I would love to see the org community stabilize the format, and let org-mode (or Vaporware::Org-mode.pm) respond to the data within that format. The content of the properties and nodes, based on how the configuration is set, determine how the library reacts.

This script solves a very focused problem, and I am not suggesting that that scope be broadened, just that some of the edge cases in parsing some of the org-mode files that may be seen get fixed.

--MidLifeXis

I see in rereading this that my comment about the source for the emacs regexp was misunderstood. I did not mean to imply that all of the other block types contained in that regexp should be parsed, I was only commenting on the possible formats that a "BEGIN_SRC" block could take.

The link to Org::Parser was a reference to the unlinked reference (now linked in a footnote), not an indicator that you should use it in this script.

The suggestion for github was to make it more readily able to have patches applied to it.

OK, I created my first account on git hub:

http://github.com/LanX/org2pod/

lets see were this will lead to. :)

I think Org::Parser is already what you want, you might wanna have a look at this conversation: http://thread.gmane.org/gmane.emacs.orgmode/40388

Cheers Rolf