From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: PATCH: include in-progress/started todos into daily agenda Date: Thu, 27 Sep 2007 22:49:53 +0200 Message-ID: <87tzpfvnny.fsf@bzg.ath.cx> References: <87sl51dud4.wl%max@openchat.com> <87r6kkdvq3.wl%max@openchat.com> <87ps04droy.wl%max@openchat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ib0J9-0007Ap-2J for emacs-orgmode@gnu.org; Thu, 27 Sep 2007 16:50:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ib0J6-0007Aa-ON for emacs-orgmode@gnu.org; Thu, 27 Sep 2007 16:50:01 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ib0J6-0007AX-H8 for emacs-orgmode@gnu.org; Thu, 27 Sep 2007 16:50:00 -0400 Received: from ug-out-1314.google.com ([66.249.92.173]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ib0J6-000872-4n for emacs-orgmode@gnu.org; Thu, 27 Sep 2007 16:50:00 -0400 Received: by ug-out-1314.google.com with SMTP id m4so1618690uge for ; Thu, 27 Sep 2007 13:49:59 -0700 (PDT) In-Reply-To: <87ps04droy.wl%max@openchat.com> (Max Mikhanosha's message of "Thu, 27 Sep 2007 12:00:13 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Max Mikhanosha writes: > Seeing "INPROGRESS Finish coding feature X" instead does not > discourage me as I don't have to be reminded that I had already wasted > 2 weeks on it, it just reminds me to continue to work on it today. I get this point. The only problem I can see with the solution you're proposing is this: how do you know that a INPROGRESS headline is of the "sticky" kind? How do you distinguish between those "keep-motivation-up" headings and other INPROGRESS headings that are scheduled for this date? Maybe you just don't *want* to distinguish between them, but other people might at least expect some visual clue. As for the vertical space limitation, I guess this wouldn't hurt that much to get rid of the blank line and of the "========" line. And if you want your INPROGRESS tasks to be displayed first, just swap the order of (agenda) and (todo "INPROGRESS") in org-agenda-custom-commands? -- Bastien