From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: switching between todo groups Date: Fri, 02 Nov 2007 17:38:38 +0000 Message-ID: <873avor1i9.fsf@bzg.ath.cx> References: <7qir4l4ghj.fsf@home.net> <877il0d7gw.fsf@bzg.ath.cx> <874pg4bqah.fsf@bzg.ath.cx> 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 1Io0Gp-00040E-GJ for emacs-orgmode@gnu.org; Fri, 02 Nov 2007 13:25:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Io0Gm-000402-Up for emacs-orgmode@gnu.org; Fri, 02 Nov 2007 13:25:22 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Io0Gm-0003zz-S9 for emacs-orgmode@gnu.org; Fri, 02 Nov 2007 13:25:20 -0400 Received: from fk-out-0910.google.com ([209.85.128.185]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Io0Gm-00016t-DX for emacs-orgmode@gnu.org; Fri, 02 Nov 2007 13:25:20 -0400 Received: by fk-out-0910.google.com with SMTP id 19so1110861fkr for ; Fri, 02 Nov 2007 10:25:19 -0700 (PDT) In-Reply-To: (Richard G. Riley's message of "Fri, 02 Nov 2007 16:05:25 +0100") 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 Richard G Riley writes: >> Mh... how do you "remember" what set you're using for en entry? > > I don't know the details of the elisp but I assume that for one open > file there is a "current sequence" variable? It is initialised to the > first. `org-todo-sets' is buffer-local and is a list of keywords sets. AFAIK there is no variable identifying the "current sequence". And I don't know if such a variable would be useful, because the "current sequence" has no sense outside each specific headline. BTW, having slightly different keywords could be a temporary workaround. What about: #+SEQ_TODO: TODO_1 | DONE_1 #+SEQ_TODO: TODO_2 NEXT WAITING | DONE_2 > It is only to be remembered for the life of the session. I think I need an example to see how such a piece of information could be used... can you provide one? -- Bastien