From: Bastien <bzg@altern.org>
To: Jason Dunsmore <emacs-orgmode@dunsmor.com>
Cc: Carsten Dominik <dominik@uva.nl>, emacs-orgmode@gnu.org
Subject: Re: Schedule event
Date: Wed, 24 Aug 2011 12:26:24 +0200 [thread overview]
Message-ID: <87vctnds1b.fsf@gnu.org> (raw)
In-Reply-To: <8739hc98rp.fsf@riotblast.dunsmor.com> (Jason Dunsmore's message of "Sun, 07 Aug 2011 17:06:18 -0500")
Hi Jason,
Jason Dunsmore <emacs-orgmode@dunsmor.com> writes:
> Carsten Dominik <dominik@uva.nl> writes:
>
>> Why do you want this special interface for setting an event date.
>> How is that better than `C-c .'? Is it that you don't need to
>> position the cursor?
>
> Yes, that was my original reason. But your suggestion of adding a
> special keyword for events is another good reason. Also, as recently
> discussed, consistent formatting conventions and clarifying the
> frequently-misunderstood issue of SCHEDULED vs. no-keyword active
> timestamps are good reasons.
I agree adding an EVENT: (or "APPT:") would be nice.
What I suggest is this:
1. merge org-schedule and org-deadline into a new org-plan function.
2. allow org-plan to set a new org-schedule-special keyword (this
keyword would be "EVENT" by default, but customizable.)
Now I'm unclear yet whether the set of features that is available
for scheduled entries should also return special-keyword entries
(e.g. org-agenda-get-scheduled) or if this should be a completely
separate set of features -- in which case I have the feeling we
are really emulating the use of an :EVENT: property.
What is your take on this?
Thanks for bringing this up anyway!
PS: it took me long to reply because I'm also considering using
the property drawer to store timestamps like SCHEDULED, DEADLINE
and so on. But it is a big move and we can't delay your request
by relying on such a change.
--
Bastien
next prev parent reply other threads:[~2011-08-24 10:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 17:05 Schedule event Jason Dunsmore
2011-08-06 6:19 ` Carsten Dominik
2011-08-06 15:00 ` Sebastien Vauban
2011-08-06 18:15 ` suvayu ali
2011-08-06 18:59 ` Sebastien Vauban
2011-08-06 19:42 ` suvayu ali
2011-08-07 6:12 ` Sebastien Vauban
2011-08-06 19:45 ` Jason Dunsmore
2011-08-07 6:14 ` Sebastien Vauban
2011-08-06 19:38 ` Jason Dunsmore
2011-08-07 22:06 ` Jason Dunsmore
2011-08-24 10:26 ` Bastien [this message]
2011-08-26 12:08 ` Greg Troxel
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=87vctnds1b.fsf@gnu.org \
--to=bzg@altern.org \
--cc=dominik@uva.nl \
--cc=emacs-orgmode@dunsmor.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).