From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Change property drawer syntax
Date: Wed, 15 Oct 2014 22:52:11 +0200 [thread overview]
Message-ID: <8738ap3vk4.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CALn3zoj9UTy6cwxJX+WPdfhJCcBCjdqRvjzu+TV-Tz9zWaFJHA@mail.gmail.com> (Michael Brand's message of "Wed, 15 Oct 2014 19:25:34 +0200")
Hello,
Michael Brand <michael.ch.brand@gmail.com> writes:
> My questions were misleading, I'm sorry. I should not have asked about
> "valid" and not have added a property drawer.
Actually valid/invalid is a bit strong. There is no such thing as
a syntax error in Org. However, Org may differ from your expectations in
some cases.
Instead of using "invalid", I'll describe what Org is supposed to see
and what you can expect.
> Rather I wanted to know when regarding only the agenda whether I can
> still postpone to make these examples valid:
>
> * Yearly meeting
> <2013-08-11 Sun>
> <2014-12-21 Sun>
> SCHEDULED: <2015-02-05 Thu>
> <2015-09-20 Sun>
> - SCHEDULED is used to remind to add a plain timestamp for the
> meeting date in 2016 that will be published latest by
> 2015-02-05. SCHEDULED will be shifted for the next year after
> that.
> * Headline
>
> Will the invalid example above continue on the new branch
> top-properties to show also the SCHEDULED in the default agenda view?
Here, SCHEDULED keyword is not located right after the headline and,
therefore, loses its meaning. Org really sees
* Yearly meeting
<2013-08-11 Sun>
<2014-12-21 Sun>
xxxxxxxxxx <2015-02-05 Thu>
<2015-09-20 Sun>
xxx
* Headline
In this case, 4 plain time-stamps should appear in the agenda. None of
them should be "scheduled". (org-entry-get (point) "SCHEDULED") will
return nil.
> * Yearly task
> DEADLINE: [2013-08-11 Sun -2d]
> DEADLINE: <2014-12-21 Sun -2d>
> SCHEDULED: <2015-02-05 Thu>
> DEADLINE: <2015-09-20 Sun -2d>
> - SCHEDULED is used to remind to add a DEADLINE for the due date
> in 2016 that will be published latest by 2015-02-05. SCHEDULED
> will be shifted for the next year after that.
> - All past DEADLINE are inactive and document when the task had
> to be done in the past.
> * Headline
>
> Will the invalid example above continue on the new branch
> top-properties to show all three active timestamps in the default
> agenda view?
Here, DEADLINE is correctly located, but isn't followed by an active
time-stamp. It also loses its meaning, leading to:
* Yearly task
xxxxxxxxxx [2013-08-11 Sun -2d]
xxxxxxxxxx <2014-12-21 Sun -2d>
xxxxxxxxxx <2015-02-05 Thu>
xxxxxxxxxx <2015-09-20 Sun -2d>
xxx
* Headline
The three active timestamps should appear in the agenda. None of them
should be either "scheduled" or "deadline". Both (org-entry-get (point)
"SCHEDULED") and (org-entry-get (point) "DEADLINE") will return nil.
If anything different happens, it is a bug. I don't know if that bug
still exists in "top-properties" branch. Anyway, I suggest to not count
on it, as it may be fixed, sooner or later.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-10-15 20:51 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 14:42 [RFC] Change property drawer syntax Nicolas Goaziou
2014-10-14 14:55 ` Andreas Leha
2014-10-14 15:55 ` Nicolas Goaziou
2014-10-14 16:18 ` Eric Abrahamsen
2014-10-14 19:26 ` Nicolas Goaziou
2014-10-14 16:25 ` Michael Brand
2014-10-14 19:38 ` Nicolas Goaziou
2014-10-15 17:25 ` Michael Brand
2014-10-15 20:52 ` Nicolas Goaziou [this message]
2014-10-15 2:58 ` Eric Abrahamsen
2014-10-15 10:11 ` Nicolas Goaziou
2014-10-15 11:22 ` Eric Abrahamsen
2014-10-15 7:38 ` Rainer M Krug
2014-10-15 10:14 ` Nicolas Goaziou
2014-10-15 11:27 ` Rainer M Krug
2014-10-20 22:35 ` Rasmus
2014-10-26 15:24 ` Nicolas Goaziou
2014-10-28 13:27 ` Nicolas Goaziou
2014-11-06 10:21 ` Sebastien Vauban
2014-11-08 13:46 ` Nicolas Goaziou
2014-11-10 10:19 ` Sebastien Vauban
2014-11-10 10:41 ` Nicolas Goaziou
2014-11-10 11:04 ` Sebastien Vauban
2014-11-10 11:51 ` Nicolas Goaziou
2014-11-10 12:55 ` Sebastien Vauban
2014-11-12 10:40 ` Sebastien Vauban
2014-11-13 19:58 ` Nicolas Goaziou
[not found] ` <87sihmq3dd.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2014-11-26 14:09 ` Sebastien Vauban
2014-10-31 13:10 ` Christian Egli
2014-10-31 16:10 ` John Hendy
2014-11-03 8:27 ` Christian Egli
2014-11-03 8:33 ` Nicolas Goaziou
2014-11-01 10:57 ` Nicolas Goaziou
2014-11-03 8:38 ` Christian Egli
2014-11-03 20:14 ` Nicolas Goaziou
2014-11-12 11:01 ` Sebastien Vauban
2014-11-12 11:11 ` Sebastien Vauban
2014-11-26 14:18 ` Sebastien Vauban
2014-11-26 23:37 ` Nicolas Goaziou
2014-11-27 9:24 ` Sebastien Vauban
2014-11-28 22:16 ` Nicolas Goaziou
2014-12-05 14:33 ` Puneeth Chaganti
2014-12-05 23:31 ` Nicolas Goaziou
2014-12-06 6:42 ` Puneeth Chaganti
2014-12-06 20:36 ` Nicolas Goaziou
2014-11-14 8:36 ` Nicolas Goaziou
[not found] ` <87ppcqnpq7.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2014-11-14 13:58 ` Sebastien Vauban
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=8738ap3vk4.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=michael.ch.brand@gmail.com \
/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).