From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: New implementation of the Org remember process ready for comments and testing Date: Wed, 23 Jun 2010 21:32:22 -0400 Message-ID: <87hbktusex.fsf@gollum.intra.norang.ca> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=55655 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ORbIv-0003KQ-Q2 for emacs-orgmode@gnu.org; Wed, 23 Jun 2010 21:32:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1ORbIu-0006wS-Rk for emacs-orgmode@gnu.org; Wed, 23 Jun 2010 21:32:33 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:56651) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1ORbIu-0006wM-Ou for emacs-orgmode@gnu.org; Wed, 23 Jun 2010 21:32:32 -0400 In-Reply-To: (Carsten Dominik's message of "Tue\, 22 Jun 2010 14\:36\:15 +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: Carsten Dominik Cc: Org Mode Carsten Dominik writes: > 6.4 Multiple capture events going on at the same time > ====================================================== > > If you need to capture something while already capturing something > else, you can now do so. Finishing the second process will > automatically return you to the window setup of the first one. > > Bernt, this might lead to confusing results if you would try to > port your immediate clock-in, clock-out code. It will probably be > better (if you decide at all to try the new code) to use the > built-in :clock-in and :clock-resume properties: > > These will even work for a chain: start capture 1, then 2, then 3, > finalize 3, then 2, then 1, and the previous clock will be > restarted each time. Only when you finish the captures in a > different sequence, then the clock-resume stuff will lead to > undefined results. Hi Carsten, I'm trying out the new capture mode and it works pretty well. The clock in and resume functions work really well :) One thing I'm missing is I have a function that changes my TODO state to NEXT on clock in except when I'm creating a new remember-mode task. I need a similar way to tell if I'm in a capture-mode buffer to prevent changing the todo state to NEXT on clock-in. I can use the buffer name which starts with "CAPTURE-" and ends in ".org" but that feels kind of hackish. Is there a variable or function available that I can use to tell if I'm clocking in a task in a capture buffer? Something like (capture-mode-p) maybe? How do you recommend I deal with this? Thanks, Bernt