emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jason Dunsmore <emacs-orgmode@dunsmor.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>, dominik@uva.nl
Cc: emacs-orgmode@gnu.org
Subject: Re: Schedule event
Date: Sat, 06 Aug 2011 14:38:13 -0500	[thread overview]
Message-ID: <87ipqa8h5m.fsf@riotblast.dunsmor.com> (raw)
In-Reply-To: <807h6qk2jq.fsf@somewhere.org> (Sebastien Vauban's message of "Sat, 06 Aug 2011 17:00:41 +0200")

"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:

>> Another idea would be to introduce another keyword like APPT an place these
>> time stamps also into the second line. That might be more easy to implement.
>
> FWIW, my instinctive reaction would be: yes, great!  Maybe that clarifies the
> bits around dates: all active dates get keywords, only inactive ones are
> without any keyword.

I agree, a special keyword for events would clarify the issue.  It would
also make this part of the manual easier to understand:
http://orgmode.org/org.html#Deadlines-and-scheduling

> In that case, I'd opt for EVENT or some such in favor of APPT. Just think at
> birthdays, or a TV show: qualifying them as APPT is a bit limitative, IMHO.
> EVENT seems a more general term.

I also like the EVENT keyword.

Regards,
Jason

  parent reply	other threads:[~2011-08-06 19:38 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 [this message]
2011-08-07 22:06   ` Jason Dunsmore
2011-08-24 10:26     ` Bastien
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=87ipqa8h5m.fsf@riotblast.dunsmor.com \
    --to=emacs-orgmode@dunsmor.com \
    --cc=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.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).