From: John Wiegley <johnw@newartisans.com>
To: Bastien <bzg@gnu.org>
Cc: Dave Abrahams <dave@boostpro.com>, emacs-orgmode@gnu.org
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 [thread overview]
Message-ID: <m21unwbqm8.fsf@gmail.com> (raw)
In-Reply-To: <878vi5xe7p.fsf@gnu.org> (Bastien's message of "Mon, 09 Apr 2012 14:49:14 +0200")
>>>>> Bastien <bzg@gnu.org> 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
next prev parent reply other threads:[~2012-04-09 20:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 14:41 Bug: "SCHEDULED: " positioning is fragile [7.8.06 (release_7.8.06.181.ga481)] Dave Abrahams
2012-04-06 7:38 ` Bastien
2012-04-06 12:18 ` Dave Abrahams
2012-04-09 11:01 ` Bastien
2012-04-09 11:20 ` Dave Abrahams
2012-04-09 12:49 ` Bastien
2012-04-09 13:58 ` Dave Abrahams
2012-04-09 14:51 ` Bastien
2012-04-09 14:54 ` Dave Abrahams
2012-04-09 15:05 ` Bastien
2012-04-09 15:52 ` Dave Abrahams
2012-04-10 13:43 ` Rainer Stengele
2012-04-10 14:12 ` Bastien
2012-04-09 20:24 ` John Wiegley [this message]
2012-04-10 12:13 ` [PATCH] " Jérémie Courrèges-Anglas
2012-04-10 12:34 ` Bastien
2012-04-10 13:34 ` Jérémie Courrèges-Anglas
2012-04-10 13:40 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m21unwbqm8.fsf@gmail.com \
--to=johnw@newartisans.com \
--cc=bzg@gnu.org \
--cc=dave@boostpro.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).