emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Greg Troxel <gdt@ir.bbn.com>
To: Bastien <bzg@altern.org>
Cc: Carsten Dominik <dominik@uva.nl>,
	Jason Dunsmore <emacs-orgmode@dunsmor.com>,
	emacs-orgmode@gnu.org
Subject: Re: Schedule event
Date: Fri, 26 Aug 2011 08:08:17 -0400	[thread overview]
Message-ID: <rmifwkos7da.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87vctnds1b.fsf@gnu.org> (Bastien's message of "Wed, 24 Aug 2011 12:26:24 +0200")

[-- Attachment #1: Type: text/plain, Size: 2115 bytes --]


Bastien <bzg@altern.org> writes:

> Jason Dunsmore <emacs-orgmode@dunsmor.com> writes:
>
>> Carsten Dominik <dominik@uva.nl> writes:
>>
>> 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.

I just started struggling with this when trying to make ical exports.
(In my not-really-defined planning system :-) I have multiple kinds of
events:

  events that I wish to be aware of, and perhaps choose to go to, but I
  don't consider myself to have a plan to attend.   For this I use bare
  active timestamps.

  events that I am planning to attend, but which I feel reasonably free
  not to.  For this I'm using TODO and SCHEDULED: (which I am thinking
  is wrong).

  events/meetings that I am committed to attending.  For these I use
  APPT (a custom TODO sequence keyword) and SCHEDULED:


After writing the above, I think my use of SCHEDULED: for events is just
wrong, and I should use it only to label days (and perhaps times) that I
plan to complete TODO items, and then use APPT/active and TODO/active
for meetings and maybe-meetings.

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

I almost always leave the property drawer collapsed, and it seems like
it hides things I don't want to see.  But I do want SCHEDULED, DEADLINE,
etc. to be very visible.    On the other hand, I would like the location
property to be hoisted to the first/second line, so perhaps putting them
all in the property drawer and having a customizable view where everyone
can see their preferred subset, formatted nicely, would be best.  Is
that more or less what you are suggesting?


[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

      reply	other threads:[~2011-08-26 12:08 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
2011-08-26 12:08       ` Greg Troxel [this message]

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=rmifwkos7da.fsf@fnord.ir.bbn.com \
    --to=gdt@ir.bbn.com \
    --cc=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).