From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Org-mode release 4.58 Date: Wed, 6 Dec 2006 03:52:01 +0100 Message-ID: <3133afbe070539675916ee37bf281faa@science.uva.nl> References: <52a846166a54d45fda4e35fb00b089cd@science.uva.nl> <20061205211405.GB3211@bertrand.carcosa.net> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GrmtB-0003Ug-VY for emacs-orgmode@gnu.org; Tue, 05 Dec 2006 21:52:06 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Grmt9-0003UU-It for emacs-orgmode@gnu.org; Tue, 05 Dec 2006 21:52:05 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Grmt9-0003UR-Ge for emacs-orgmode@gnu.org; Tue, 05 Dec 2006 21:52:03 -0500 Received: from [193.252.22.241] (helo=smtp-1.orange.nl) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Grmt9-0001Yo-JF for emacs-orgmode@gnu.org; Tue, 05 Dec 2006 21:52:03 -0500 In-Reply-To: <20061205211405.GB3211@bertrand.carcosa.net> 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: "Jason F. McBrayer" Cc: emacs-orgmode On Dec 5, 2006, at 22:14, Jason F. McBrayer wrote: > I've tried this with the example provided before, and also replaced a > lot of the functions that switch from the agenda buffer to the > corresponding org-mode buffer with functions that switch to the > subtree indirect buffer. > > Now I've switched back to the original, default behaviour. The > problem with what I tried was that I tended to clock-in to the > indirect buffer, with the result that org-clock-marker tended to get > lost, making switching tasks or clocking out break. I consider this > my fault, though, not an org-mode issue. Yes, in this case clocking out will only be possible as long as the indirect buffer lives. However, we can easily put the clock marker into the base buffer. Try the following patch: --- org.el.orig 2006-12-06 03:45:40.000000000 +0100 +++ org.el 2006-12-06 03:46:45.000000000 +0100 @@ -6805,7 +6805,7 @@ (indent-relative) (insert org-clock-string " ") (setq ts (org-insert-time-stamp (current-time) 'with-hm 'inactive)) - (move-marker org-clock-marker (point)) + (move-marker org-clock-marker (point) (buffer-base-buffer)) (message "Clock started at %s" ts)))) (defun org-clock-out (&optional fail-quietly)