From: Nick Dokos <nicholas.dokos@hp.com>
To: SW <sabrewolfy@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Timestamp, deadline and scheduling clarification
Date: Tue, 29 May 2012 08:50:53 -0400 [thread overview]
Message-ID: <15087.1338295853@alphaville> (raw)
In-Reply-To: Message from SW <sabrewolfy@gmail.com> of "Tue, 29 May 2012 08:35:49 -0000." <loom.20120529T103306-318@post.gmane.org>
SW <sabrewolfy@gmail.com> wrote:
> I'd like to clarify some of the usage of timestamps. Preceeding a timestamp with
> DEADLINE or SCHEDULE gives extra functionality in the agenda. Omitting these
> keywords produces a normal timestamp which *appears* in the agenda but does not
> trigger advanced warning before and does not continue to remind afterwards -- is
> this correct? So such a normal timestamp appears and disappears off the agenda
> and could therefore be missed. What is the use-case of a normal timestamp -- one
> without DEADLINE or SCHEDULE?
>
>
I use them for appointments (and they can have a repeater so they can be
used for periodic meetings e.g.). As you note they appear in the agenda,
so I can get a quick but comprehensive look for what's in store for the
day, but with a bit of configuration (see org-agenda-to-appt), they can
provide reminders using appt.el. Various setups have been described on
worg and on the ML, but they mostly differ in how they deliver the
notification: the basic mechanism is the same.
Nick
next prev parent reply other threads:[~2012-05-29 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 8:35 Timestamp, deadline and scheduling clarification SW
2012-05-29 12:50 ` Nick Dokos [this message]
2012-05-29 13:21 ` Sebastien Vauban
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=15087.1338295853@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=sabrewolfy@gmail.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).