From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Bernt Hansen <bernt@norang.ca>,
emacs-orgmode@gnu.org,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: New exporter and dates in tables
Date: Sat, 13 Apr 2013 12:54:24 +0200 [thread overview]
Message-ID: <87mwt2aefz.fsf@gmail.com> (raw)
In-Reply-To: <8738uxrrtc.fsf@bzg.ath.cx> (Bastien's message of "Thu, 11 Apr 2013 17:49:03 +0200")
Hello,
Bastien <bzg@gnu.org> writes:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> Thinking more about it, I think I need to make some more exceptions
>> anyway. For example timestamps in clock lines and in planning info
>> shouldn't react to `org-export-with-timestamps' (it would be silly to
>> have `org-export-with-planning' set to t and still see nothing because
>> `org-export-with-timestamps' is nil).
>
> Indeed :)
>
> Thinking again about Bernt's use-case and Carsten's feedback,
> I suggest making rules for planning instead of exceptions for
> time-stamps.
>
> - planning information is
> - SCHEDULED: <time-stamp>
> - DEADLINE: <time-stamp>
> - CLOSED: <time-stamp>
> - one or more time-stamps (active or inactive) alone on a line
>
> - a non-planning time-stamp is any time-stamp that does not fall
> into the categories above, i.e. if it is inlined in an element
> (usually a paragraph or a table).
SCHEDULED and friends define a property in the associated headline.
Generic timestamps don't (excepted for the first one, but it's arbitrary
and the parser ignores it anyway).
Also, there can be as many active timestamps in a section, but there can
be only one planning info element.
Therefore, I don't think they belong to the same category. We ought to
treat them differently, like we do at the moment.
> The inactive/active time-stamp in a table is handled.
>
> And so is another corner case that we did not discussed yet:
> people using active time-stamps right below a headline, with
> the expectation that this time-stamp will bring the entry up
> in the agenda -- such time-stamp is now considered a time-stamp
> while it is really some planning info.
This is obviously some planning info, but not a "planning-info" element.
Any active timestamp is a planning info by the way. The "planning-info"
term just defines the line with SCHEDULED, DEADLINE, CLOSED keyword. It
may be silly, be a name had to be chosen.
Anyway, I don't think it's a corner case.
> I guess this is cleaner than creating exceptions.
>
> What about it?
I'd rather create the aforementioned exceptions (in tables but more
importantly in planning info and clocks): it is important to distinguish
"planning-info" from a mere timestamp. We can change the name if it's
confusing, though.
Is that OK with you?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-04-13 10:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 0:05 New exporter and dates in tables Bernt Hansen
2013-04-08 2:18 ` Mike McLean
2013-04-08 6:57 ` Nicolas Goaziou
2013-04-08 11:27 ` Bernt Hansen
2013-04-08 11:33 ` Carsten Dominik
2013-04-08 19:49 ` Nicolas Goaziou
2013-04-09 13:06 ` Carsten Dominik
2013-04-10 12:43 ` Nicolas Goaziou
2013-04-10 13:12 ` Carsten Dominik
2013-04-10 13:16 ` Bastien
2013-04-11 11:28 ` Nicolas Goaziou
2013-04-11 15:49 ` Bastien
2013-04-13 10:54 ` Nicolas Goaziou [this message]
2013-04-13 14:02 ` Bastien
2013-04-13 17:33 ` Nicolas Goaziou
2013-04-13 21:07 ` Sebastien Vauban
2013-04-14 9:10 ` Bastien
2013-04-14 8:58 ` Bastien
2013-04-14 13:37 ` Nicolas Goaziou
2013-04-14 13:45 ` Bastien
2013-04-14 13:47 ` Nicolas Goaziou
2013-04-14 14:01 ` Bastien
2013-04-14 14:06 ` Nicolas Goaziou
2013-04-14 14:24 ` Bastien
2013-04-14 20:36 ` Nicolas Goaziou
2013-04-15 3:58 ` Jambunathan K
2013-04-15 6:44 ` Bastien
2013-04-16 7:48 ` Bastien
2013-08-09 9:35 ` Carsten Dominik
2013-08-09 11:02 ` Bernt Hansen
2013-08-12 5:45 ` Carsten Dominik
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=87mwt2aefz.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bernt@norang.ca \
--cc=bzg@gnu.org \
--cc=carsten.dominik@gmail.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).