if both schedule and deadline, appear only once in agenda

if both schedule and deadline, appear only once in agenda

[Gijs Hillenius]

Hello,

I hope the subject line is clear, but I bet not.

I have a TODO item with both a schedule and a deadline and this
results in the item appearing twice after the deadline passes in my
Org weekly Agenda.

Is there a way that I can automatically change this behaviour? What I
do now is manually delete the schedule stamp once the deadline is
made.

Or should I maybe simply not use both stamps for the same item? 

Thanks, by the way, for Org mode.

Gijs

Re: if both schedule and deadline, appear only once in agenda

[Bastien]

Gijs Hillenius <gijs@hillenius.net> writes:

> I have a TODO item with both a schedule and a deadline and this
> results in the item appearing twice after the deadline passes in 
> my Org weekly Agenda.

Meaning you have to blame yourself twice :)

> Or should I maybe simply not use both stamps for the same item? 

I don't see why you need both of them. Can you answer that?

-- 
Bastien

Re: if both schedule and deadline, appear only once in agenda

[Gijs Hillenius]

On 12 Oct 2007, Bastien wrote:

>> Or should I maybe simply not use both stamps for the same item? 
>
> I don't see why you need both of them. Can you answer that?

Yes.

But maybe I should not :-). But here goes: I plan to start working on
an item by date X -> schedule stamp. The item has a deadline, so ->
deadline.

Would an example help:

I'd like to be forewarned by Org that I have a new item coming onto my
todo list, as of next Monday. And I want to see that, I need to get it
done on Wednesday.

But call me crazy..









-- 
/* This bit of chicanery makes a unary function followed by
a parenthesis into a function with one argument, highest precedence. */
		-- Larry Wall in toke.c from the perl source code

Re: if both schedule and deadline, appear only once in agenda

[Bastien]

Gijs Hillenius <gijs@hillenius.net> writes:

> But maybe I should not :-). But here goes: I plan to start working on
> an item by date X -> schedule stamp. The item has a deadline, so ->
> deadline.

For that I use `org-deadline-warning-days'.  I start the deadline when
it shows up in my agenda.  The default value for this is 14, but you can
set a value for each deadline like this:

  DEADLINE: <2004-02-29 Sun -10d>

Meaning that you should start the deadline 10 days before the deadline.

,----[ (info "(org)Deadlines and scheduling") ]
| You can specify a different lead time for warnings for a specific
| deadlines using the following syntax.  Here is an example with a
| warning period of 5 days `DEADLINE: <2004-02-29 Sun -5d>'.
`----

HTH,

-- 
Bastien

Re: if both schedule and deadline, appear only once in agenda

[Detlef Steuer]

On Fri, 12 Oct 2007 14:36:42 +0100
Bastien <bzg@altern.org> wrote:

> Gijs Hillenius <gijs@hillenius.net> writes:
> 
> > But maybe I should not :-). But here goes: I plan to start working on
> > an item by date X -> schedule stamp. The item has a deadline, so ->
> > deadline.
> 
> For that I use `org-deadline-warning-days'.  I start the deadline when
> it shows up in my agenda.  The default value for this is 14, but you can
> set a value for each deadline like this:

I'm all on Gijs' side in using SCHEDULED and DEADLINE just the way he does.
A deadline warning for me describes some different kind of animal.

Nevertheless: If both SCHEDULED and DEADLINE passed by and no work was
done either there was no real deadline or there is a new deadline or
now you're allowed to remove the task silently.  

:-)

Detlef

> 
>   DEADLINE: <2004-02-29 Sun -10d>
> 
> Meaning that you should start the deadline 10 days before the deadline.
> 
> ,----[ (info "(org)Deadlines and scheduling") ]
> | You can specify a different lead time for warnings for a specific
> | deadlines using the following syntax.  Here is an example with a
> | warning period of 5 days `DEADLINE: <2004-02-29 Sun -5d>'.
> `----
> 
> HTH,
> 
> -- 
> Bastien
> 
> 
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> 

Re: if both schedule and deadline, appear only once in agenda

[SW]

I know I'm bumping a thread from 5 years ago :)

Bastien <bzg <at> altern.org> writes:

> Gijs Hillenius <gijs <at> hillenius.net> writes:
>
> > But maybe I should not . But here goes: I plan to start working on
> > an item by date X -> schedule stamp. The item has a deadline, so ->
> > deadline.
> 
> For that I use `org-deadline-warning-days'.  I start the deadline when
> it shows up in my agenda.  The default value for this is 14, but you can
> set a value for each deadline like this:
> 
>   DEADLINE: <2004-02-29 Sun -10d>
> 
> Meaning that you should start the deadline 10 days before the deadline.
> 
> ,----[ (info "(org)Deadlines and scheduling") ]
> | You can specify a different lead time for warnings for a specific
> | deadlines using the following syntax.  Here is an example with a
> | warning period of 5 days `DEADLINE: <2004-02-29 Sun -5d>'.
> `----

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.

Re: if both schedule and deadline, appear only once in agenda

[suvayu ali]

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.

Re: if both schedule and deadline, appear only once in agenda

[SW]

suvayu ali <fatkasuvayu+linux <at> gmail.com> writes:

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

Thanks. I have read that page many times and I understand what the term
"SCHEDULE" means in org-mode.

However, this is not what my question is about. My question relates to advance
warning that an item is scheduled in the future. I want to know on Friday that I
have scheduled a large project to start on Monday. That is, I would like to know
beforehand that I need to start working on a large project in a few days time.

Aside: Awesome! The spam-prevention Captcha graphic for this post is the word
"scheduled" :)

Re: if both schedule and deadline, appear only once in agenda

[Eric S Fraga]

SW <sabrewolfy@gmail.com> writes:
> However, this is not what my question is about. My question relates to advance
> warning that an item is scheduled in the future. I want to know on Friday that I
> have scheduled a large project to start on Monday. That is, I would like to know
> beforehand that I need to start working on a large project in a few days time.

One approach is to consider that "thinking about a large project about
to start" is itself a task so you could look at adding a task for the
Friday, when you first scheduled the large task for the Monday, to tell
you start thinking...

This might sound silly but it can actually be quite useful if you get
into the habit of thinking about such aspects when you schedule tasks.

And, of course, you can group related tasks like these as subheadings
under a common headline.

Something to think about over the weekend ;-)

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.10-630-g4144c5.dirty

Re: if both schedule and deadline, appear only once in agenda

[Mike McLean]

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


On Jun 1, 2012, at 4:09 AM, Eric S Fraga wrote:

> SW <sabrewolfy@gmail.com> writes:
>> However, this is not what my question is about. My question relates to advance
>> warning that an item is scheduled in the future. I want to know on Friday that I
>> have scheduled a large project to start on Monday. That is, I would like to know
>> beforehand that I need to start working on a large project in a few days time.
> 
> One approach is to consider that "thinking about a large project about
> to start" is itself a task so you could look at adding a task for the
> Friday, when you first scheduled the large task for the Monday, to tell
> you start thinking...
> 
> This might sound silly but it can actually be quite useful if you get
> into the habit of thinking about such aspects when you schedule tasks.

I agree with this sentiment wholeheartedly. My default “project” org-capture template has a sub task for defining the project. You could setup your template in whatever way works for you. 

I used to use a version of the GTD Natural Planning model with bullets for Purpose, Principles, Vision, Outcome, etc. I have since simplified to a MadLibs user story format: http://www.mountaingoatsoftware.com/blog/advantages-of-the-as-a-user-i-want-user-story-template

If I know the broad outlines of project at the time of capture, I fill it all in with the capture template. If I do not yet have the project fully thought out, I add a TODO keyword to the “Project Definition” subheading. Depending on the project I add scheduled and/or deadline dates to the project itself and/or the Project Definition TODO. The relevant snippet from my org-capture is:

#+begin_src emacs-lisp
(setq org-capture-templates (quote (
	("P" "project" entry (file "~/Documents/OrgMaster/org/refile.org") "* %?       :Project_Backlog: \n  %U\n** Project Definition\n- Summary\n  + As <personal role>, I want <goal> so <reason>\n- Completion Criteria (Don't do too much)\n  + \n" :clock-in t :clock-resume t)
)))
#+end_src

Since I have clocking as part of my capture template, I also record the time I spend writing the project requirements against the project -- when I refile the project that time moves with the refile to be charged against the broader desired outcome. I get quite a bit of quantified self information this way :)



[-- Attachment #2: Type: text/html, Size: 3299 bytes --]