emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "Peter Münster" <pmlists@free.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: problem with org-element-parse-buffer
Date: Sat, 24 Nov 2012 13:21:12 +0100	[thread overview]
Message-ID: <87ehjjkx8n.fsf@gmail.com> (raw)
In-Reply-To: <877gpbrz1g.fsf@micropit.couberia.selfip.net> ("Peter \=\?utf-8\?Q\?M\=C3\=BCnster\=22's\?\= message of "Sat, 24 Nov 2012 13:00:27 +0100")

Peter Münster <pmlists@free.fr> writes:

> On Mon, Nov 12 2012, Nicolas Goaziou wrote:

>> In Org, planning info (scheduled, deadline, and closed) must be put just
>> after the headline. Your example isn't valid.
> Then, org-agenda should ignore that too, shouldn't it?

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?


Nicolas Goaziou

  reply	other threads:[~2012-11-24 12:25 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 [this message]
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

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=87ehjjkx8n.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pmlists@free.fr \


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