Re: [O] Bug: "SCHEDULED: " positioning is fragile [7.8.06 (release_7.8.06.181.ga481)]

[John Wiegley]

>>>>> Bastien  <address@hidden> writes:

> You might also look at org-element.el.

> FYI: Nicolas and I have been discussing about the issue you raised, and the
> integration of org-element.el will force us to be clearer about such cases,
> which is good.

I think Org-X and org-element can be merged.

Org-X is a bidirectional system for turning Org entries into Lisp structure,
and back again.  Because of this bidirectionality, it lets you send Org
entries to other "Backends" (like Redmine, Bugzilla, etc.), and also
receive/sync Org entries with those backends.

While Org-X does parse major structural elements within entries (the scheduled
date, property drawer, and a few others), it makes no attempt to interpret the
textual content of entries, nor does it deal with whole trees, or the
ancillary data outside of heading lines (like the #+keyword markers).

It might be very useful at this point to combine the efforts of these two
projects into a complete abstraction layer for Org.  And it would be
unfortunate to have two entirely separate efforts with different areas of
focus, fragmenting the community of people who want to work with their Org
data programmatically.

I've been using Org-X for utility code for many months now, and I'm ready to
push it to mainstream.  It simply needs some documentation at this point.

If you guys are interested in merging org-element and Org-X, we should discuss
that.  Org-X is already doing a few of the things that org-element does, but I
don't believe org-element is doing much of what Org-X does, in terms of
built-in support for shuttling data to/from various backends.  Even the
Org-mode support itself is implemented as a backend on top of a more general
abstraction layer.

John