From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: How to define a start date for a task? Date: Sun, 18 Dec 2011 08:46:47 -0500 Message-ID: <87k45uq9fc.fsf@norang.ca> References: <2011-12-17T21-30-46@devnull.Karl-Voit.at> <87sjkirhdu.fsf@norang.ca> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:42944) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RcH4y-00043g-Nx for emacs-orgmode@gnu.org; Sun, 18 Dec 2011 08:47:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RcH4x-0004Pd-3q for emacs-orgmode@gnu.org; Sun, 18 Dec 2011 08:47:04 -0500 Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:32389 helo=mho-01-ewr.mailhop.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RcH4w-0004PT-Tj for emacs-orgmode@gnu.org; Sun, 18 Dec 2011 08:47:03 -0500 In-Reply-To: (Karl Maihofer's message of "Sun, 18 Dec 2011 10:25:31 +0000 (UTC)") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Karl Maihofer Cc: emacs-orgmode@gnu.org Karl Maihofer writes: > Bernt Hansen norang.ca> writes: >> I assume you have a few typos in the following description: >> > I'm not sure if this helps. What I'd like to archive is that an unavailable >> ^^^^^^^ >> achieve > > Of course, that is a typo. ;-) > >> > I do not want the task to show up on my daily agenda when it >> > becomes available. >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> not want the task to show up [only] on my daily agenda > > But that is not a typo. > Ah - sorry about that. > Correct me, but with your solution, tasks become available > (schedule date arrives) and then they will show up on the > daily agenda. And they will show up there every day until > I mark the task as done. That is not really what I'd like > to achieve (not archive!) since tasks with start dates are > tasks I can do when the start date arrived but do not have > to do on a special date. That is essentially what SCHEDULED: is for. It shows up on the scheduled (start) date and stays on your daily agenda until you mark it done. If the task is supposed to be on a specific date I just put a plain date stamp on it (without the SCHEDULED: prefix) I use this for appointments etc which have a fixed date and time. > > My workflow is as follows: I have a look at my daily agenda > to find out what I have to do that day. There I can find > tasks that are scheduled or have a deadline. When I finished The use of SCHEDULED in org-mode can be confusing. >From the org-mode manual ,---- | SCHEDULED | Meaning: you are planning to start working on that task on the | given date. | | The headline will be listed under the given date(1). In addition, | a reminder that the scheduled date has passed will be present in | the compilation for _today_, until the entry is marked DONE, i.e. | the task will automatically be forwarded until completed. | | *** TODO Call Trillian for a date on New Years Eve. | SCHEDULED: <2004-12-25 Sat> | | 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. `---- > these tasks and still have time to do some more work, I do > agenda searches for tags and/or todo keywords. So, tasks > with only a start date should never show up on my daily > agenda. They should be hidden from all agenda searches until > the start date arrives. Until then they should be available > for all agenda searches (but they should not show up on the > daily agenda list until I define a schedule date). > > Is that also possible or am I the only person that has a > need for this? ;-) I think you'll need to write a custom agenda skip function that skips your tasks with an inactive START: [date] in the future. I don't know of a way to apply a custom skip function to the global todo and tags searches so you'll probably need to use custom agenda searches for this. Regards, Bernt