From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: SW <sabrewolfy@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: if both schedule and deadline, appear only once in agenda
Date: Wed, 30 May 2012 11:46:19 +0200 [thread overview]
Message-ID: <CAMXnza2-HmF97YR2+q9ENS+0NettFF4aSW2piV_dCuvc47y9Aw@mail.gmail.com> (raw)
In-Reply-To: <loom.20120530T110720-856@post.gmane.org>
On Wed, May 30, 2012 at 11:12 AM, SW <sabrewolfy@gmail.com> wrote:
> I think what the OP wanted (and what lead me to this thread) is an advanced
> warning for *scheduled* items. For example, I'd like to know on the Friday
> before that I have a scheduled item starting on the Monday. To do this I
> SCHEDULE the item to Monday and then also set a DEADLINE for Monday, which will
> obviously warn be in advance. I'm not unhappy with this solution, but I was
> wondering if there were an alternative.
<http://orgmode.org/manual/Deadlines-and-scheduling.html#Deadlines-and-scheduling>
...
Important: Scheduling an item in Org mode should not be understood in
the same way that we understand scheduling a meeting. Setting a date
for a meeting is just a simple appointment, you should mark this entry
with a simple plain timestamp, to get this item shown on the date
where it applies. This is a frequent misunderstanding by Org users. In
Org mode, scheduling means setting a date when you want to start
working on an action item.
...
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2012-05-30 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 5:28 if both schedule and deadline, appear only once in agenda Gijs Hillenius
2007-10-12 13:05 ` Bastien
2007-10-12 12:21 ` Gijs Hillenius
2007-10-12 13:36 ` Bastien
2012-01-10 10:15 ` Detlef Steuer
2012-05-30 9:12 ` SW
2012-05-30 9:46 ` suvayu ali [this message]
2012-05-30 9:52 ` SW
2012-06-01 8:09 ` Eric S Fraga
2012-06-05 22:31 ` Mike McLean
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=CAMXnza2-HmF97YR2+q9ENS+0NettFF4aSW2piV_dCuvc47y9Aw@mail.gmail.com \
--to=fatkasuvayu+linux@gmail.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).