From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: omitting done TODOs from custom agenda Date: Wed, 15 Sep 2010 13:07:35 +0800 Message-ID: <87eicva92g.fsf@ericabrahamsen.net> References: <877hiqj7h3.fsf@ericabrahamsen.net> <87k4mpxz7g.fsf@archdesk.localdomain> <87lj75f8l5.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from [140.186.70.92] (port=47582 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OvkDo-0007rb-OI for emacs-orgmode@gnu.org; Wed, 15 Sep 2010 01:07:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OvkDm-0002ed-HR for emacs-orgmode@gnu.org; Wed, 15 Sep 2010 01:07:52 -0400 Received: from lo.gmane.org ([80.91.229.12]:33564) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OvkDm-0002eI-74 for emacs-orgmode@gnu.org; Wed, 15 Sep 2010 01:07:50 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OvkDi-0004RS-C4 for emacs-orgmode@gnu.org; Wed, 15 Sep 2010 07:07:46 +0200 Received: from 123.121.217.62 ([123.121.217.62]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 15 Sep 2010 07:07:46 +0200 Received: from eric by 123.121.217.62 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 15 Sep 2010 07:07:46 +0200 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 On Tue, Sep 14 2010, Eric Abrahamsen wrote: > On Tue, Sep 14 2010, Matt Lundin wrote: > >> Eric Abrahamsen writes: >> >>> I'm having a bit of confusion: I've created my own TODO sequences with >>> org-todo-keywords, in this case (sequence "CONTACT(n)" "REPLY(r)" "|" >>> "CONTACTED(e@)"). Then I've got a custom agenda defined using >>> org-agenda-custom-commands, where there's a weekly view on top and some >>> TODO items below. When I start this agenda view, and mark one of the >>> TODO items as CONTACTED, it doesn't disappear from the agenda view. It's >>> very clearly marked as done in the original org file, but it stays in >>> agenda. I've looked at all the extra variables for a custom agenda >>> command, and there doesn't seem to be one that say "don't show completed >>> items". >> >> A simple question: Are you refreshing the agenda after marking the item >> done (i.e., CONTACTED)? Similarly, do the inactive items (i.e., >> CONTACTED) remain when you invoke the agenda view the again. >> >> Inactive todos do not disappear from the agenda until it is refreshed >> (r). > > Hi Matt, > > Yup, I am refreshing the agenda with r, or usually g. In the agenda, > when I first mark the item as done, the text of the heading turns green, > but when I next refresh, the text turns back to black. These completed > todos are still there even if I close the agenda and re-invoke it. > >> >>> These items are part of a tag-todo statment, where the selecting regexp >>> is a tag, not a particular todo keyword, so I wouldn't think I've done >>> anything to force it to display these todo keywords. >> >> Would you mind sharing your custom agenda command? > > Of course: > > '(org-agenda-custom-commands (quote (("c" "Agenda plus contacts" > ((agenda "" nil) (tags-todo "TODO=\"CONTACT\"" nil) (tags-todo > "TODO=\"REPLY\"" nil)) nil nil) ("g" "Get It Louder" ((agenda "" nil) > (tags-todo "Gil" nil)) nil)))) > > The problem occurs in both my "Agenda plus contacts" and "Get It > Louder", so maybe it's something with my custom todos? > > (org-todo-keywords (quote ((sequence "TODO(t)" "WAITING(w@)" "|" > "DONE(d)" "CANCELLED(c@)") (sequence "CONTACT(n)" "REPLY(r)" "|" > "CONTACTED(e@)")))) Looks like the problem here was that CONTACT is a substring of CONTACTED—whatever function decides if a todo keyword is pending or completed apparently just reads the string until it finds the first match (?). I changed it to SENT and everything worked fine. Dunno if that's worth considering a bug, but it's certainly surprising behavior. E > > But I don't see how that could be interpreted as anything but CONTACTED > = done... > > Thanks! > >> >> Best, >> Matt > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode