From: Christopher Allan Webber <cwebber@dustycloud.org>
To: emacs-orgmode@gnu.org
Subject: Occurance property, or some similar name?
Date: Mon, 11 Apr 2011 17:42:28 -0500 [thread overview]
Message-ID: <87d3ksqujv.fsf@dustycloud.org> (raw)
I was once one of the many people who apparently originally
misunderstood what "SCHEDULED" meant, and used to set it to like, an
appointment time.
It seems the appropriate thing for what I actually meant was to just
put a timestamp anywhere in the entry and that works out well. A lot of
people put it on the header apparently, and that seems insane to me.
I kind of miss how nice it was back when I misunderstood how events work
(escept for all of those non-TODOs staying around forever on my
agenda..) where I had a dedicated property for this, and pressing
C-c C-s would always change that property.
What I'm saying I guess is:
- Is there a popular property name for when something should be
happening, in a non-TODO way? I've thought of "OCCURANCE" but maybe
that isn't the best (I suspect not)
- Maybe if we formalize this property, we should make a command for it?
Maybe C-c C-S-o?
- It would be nice to formalize this so we could actually steer people
in the right direction in the docs.
--
𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻
next reply other threads:[~2011-04-12 1:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 22:42 Christopher Allan Webber [this message]
2011-04-12 4:22 ` Occurance property, or some similar name? theo
2011-04-12 14:41 ` Christopher Allan Webber
2011-04-12 19:28 ` Matt Lundin
2011-04-12 19:25 ` Matt Lundin
2011-04-12 20:52 ` Christopher Allan Webber
2011-04-13 1:01 ` Matt Lundin
2011-04-13 13:07 ` Christopher Allan Webber
2011-04-13 8:19 ` Michael Brand
2011-04-13 13:08 ` Christopher Allan Webber
2011-04-13 14:19 ` Michael Brand
2011-04-13 14:43 ` Christopher Allan Webber
2011-04-13 15:42 ` Michael Brand
2011-04-13 15:57 ` Christopher Allan Webber
2011-04-12 20:00 ` Memnon Anon
2011-04-12 20:24 ` Richard Riley
2011-04-13 15:34 ` 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=87d3ksqujv.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--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).