From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Wiegley Subject: Re: Bug: "SCHEDULED: " positioning is fragile [7.8.06 (release_7.8.06.181.ga481)] Date: Mon, 09 Apr 2012 15:24:31 -0500 Message-ID: References: <871uo1l37g.fsf@gnu.org> <877gxpyxs6.fsf@gnu.org> <878vi5xe7p.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59366) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SHL8k-0002tR-VR for emacs-orgmode@gnu.org; Mon, 09 Apr 2012 16:24:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SHL8j-0004gl-7p for emacs-orgmode@gnu.org; Mon, 09 Apr 2012 16:24:42 -0400 In-Reply-To: <878vi5xe7p.fsf@gnu.org> (Bastien's message of "Mon, 09 Apr 2012 14:49:14 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: Dave Abrahams , emacs-orgmode@gnu.org >>>>> Bastien 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