From: Andrew Hyatt <email@example.com>
To: Carsten Dominik <firstname.lastname@example.org>
Cc: Brian van den Broek <email@example.com>,
Andrea Crotti <firstname.lastname@example.org>
Subject: Re: do it today, or well, tomorrow
Date: Wed, 12 Oct 2011 20:29:54 -0400 [thread overview]
Message-ID: <CAM6wYYJ=FOi01mw2hPWvH5L9hBBXuv_Re7xKD7fuXd=6XYXE0Q@mail.gmail.com> (raw)
While we're talking about scheduling... one thing I'd love to see, but
never figured out how to do, is to schedule a parent task, and have
the subtasks all inherit that schedule. I think I've tried most
obvious things, but schedules seem just not to be inherited.
On Wed, Oct 12, 2011 at 1:12 PM, Carsten Dominik
> On 12.10.2011, at 18:08, Andrea Crotti wrote:
>> On 10/12/2011 04:55 PM, Carsten Dominik wrote:
>>> An alternative is to use the scheduling mechanism.
>>> * TODO My Task
>>> SCHEDULED:<2011-10-12 Wed>
>>> This task will automatically be forwarded to the following day, until it is done.
>>> - Carsten
>> I only see the habit page on the manual now, but it has to be enabled,
>> and the "SCHEDULED" setting has to be done by hand right?
> Use C-c C-s for this. All described in detail in the manual - take the time to read it!
>> Maybe I should use a capture template for that?
> That is also a possibility, of course!
>> And it's not very clear how do I set an habit on a task, when I run
>> org-habit-toggle-habits it opens me the agenda buffer, instead of doing something in
>> the current task as I (wrongly) expected.
> Again, the manual does cover this. the toggle-habit function is for turning them on and off in the agenda display.
> - Carsten
next prev parent reply other threads:[~2011-10-13 0:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 14:22 do it today, or well, tomorrow Andrea Crotti
2011-10-12 14:33 ` Brian van den Broek
2011-10-12 14:41 ` John Rakestraw
2011-10-12 15:55 ` Carsten Dominik
2011-10-12 16:08 ` Andrea Crotti
2011-10-12 17:12 ` Carsten Dominik
2011-10-13 0:29 ` Andrew Hyatt [this message]
2011-10-12 14:41 ` Antoine Levitt
2011-10-12 14:54 ` Dave Abrahams
2011-10-12 15:17 ` Andrea Crotti
2011-10-12 20:25 ` John Wiegley
2011-10-12 21:57 ` Andy Moreton
2011-10-12 22:24 ` John Wiegley
2011-10-13 7:36 ` Rainer Stengele
2011-10-13 8:17 ` John Wiegley
2011-10-13 8:45 ` Eric Abrahamsen
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).