emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: problem with org-element-parse-buffer
Date: Mon, 26 Nov 2012 09:04:57 +0800	[thread overview]
Message-ID: <8738zxrx6u.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87a9u63v3e.fsf@gmail.com

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>> Strictly speaking, yes. But Org Agenda is a bit permissive (and not only
>>> for that thing). Do you want to help basing Agenda on Elements?


>> This is something I've wanted for a while, as it would make
>> some of my little personal projects a lot easier. I'd be happy to help
>> if there's a roadmap, and if I can be fed bite-sized problems to deal
>> with.
> There's no roadmap for now. If you're looking for small tasks to handle,
> I think interactive functions are a good start (although some can be
> a bit challenging, i.e. `org-open-link'). Particularly good candidates
> are those calling either `org-at-regexp-p', `org-in-regexp' or
> `org-between-regexps-p': using those is almost always wrong (or at least
> fragile).
> If you give a shot at some of them, please include ert tests: writings
> tests for Org is really a must from now on. There are now plenty of
> examples in testing directory.

Great, thanks for the pointers. I'll see if I can't provide a few
patches in the next couple of weeks.


      reply	other threads:[~2012-11-26  1:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12  9:42 problem with org-element-parse-buffer Peter Münster
2012-11-12 10:55 ` Nicolas Goaziou
2012-11-24 12:00   ` Peter Münster
2012-11-24 12:21     ` Nicolas Goaziou
2012-11-24 22:03       ` Peter Münster
2012-11-25  4:29       ` Eric Abrahamsen
2012-11-25  9:11         ` Nicolas Goaziou
2012-11-26  1:04           ` Eric Abrahamsen [this message]

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:

  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=8738zxrx6u.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-orgmode@gnu.org \


* 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


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).