From mboxrd@z Thu Jan 1 00:00:00 1970 From: James TD Smith Subject: Re: Incompatible change in latest push Date: Thu, 16 Oct 2008 15:23:26 +0100 Message-ID: <20081016142326.GE59512@yog-sothoth.mohorovi.cc> References: <20081016100257.GA19032@nyarlathotep.internal.mohorovi.cc> <87wsg8afma.fsf@gollum.intra.norang.ca> 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 1KqTlD-00048v-QG for emacs-orgmode@gnu.org; Thu, 16 Oct 2008 10:23:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KqTlC-00045Y-8e for emacs-orgmode@gnu.org; Thu, 16 Oct 2008 10:23:31 -0400 Received: from [199.232.76.173] (port=45985 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KqTlB-00045G-Vt for emacs-orgmode@gnu.org; Thu, 16 Oct 2008 10:23:30 -0400 Received: from 81-86-40-42.dsl.pipex.com ([81.86.40.42]:62763 helo=yog-sothoth.mohorovi.cc) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KqTlB-0002aB-8c for emacs-orgmode@gnu.org; Thu, 16 Oct 2008 10:23:29 -0400 Received: from yog-sothoth.mohorovi.cc (localhost [127.0.0.1]) by yog-sothoth.mohorovi.cc (8.14.2/8.14.2) with ESMTP id m9GENRGY090830 for ; Thu, 16 Oct 2008 15:23:27 +0100 (BST) (envelope-from ahktenzero@mohorovi.cc) Received: (from ahktenzero@localhost) by yog-sothoth.mohorovi.cc (8.14.2/8.14.2/Submit) id m9GENRA8090829 for emacs-orgmode@gnu.org; Thu, 16 Oct 2008 15:23:27 +0100 (BST) (envelope-from ahktenzero@mohorovi.cc) Content-Disposition: inline In-Reply-To: <87wsg8afma.fsf@gollum.intra.norang.ca> 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 2008-10-16 08:28:29(-0400), Bernt Hansen wrote: > Thanks for restoring the old behaviour. > > This was confusing me a bit -- I have lots of tasks where the clock > drawer is way down in the body of the task after lots of repeated 'DONE' > notes (for some of my cyclic tasks). I was used to the latest DONE note > being at the top and all of a sudden it looked to me like the logging of > the repeated task stopped working - but in fact the entry was placed > after my :CLOCK: drawer somewhere in the middle of the task and was much > harder to find. Ah, I didn't think of that. Sorry. I had been manually moving my drawers back to the top of the entry since I noticed them moving. Adding the note after the CLOCK drawer when the drawer is not at the start of the entry is completely wrong; the note insertion code should only skip drawers if they are immediately after the scheduling keywords. I'll work on a patch which will fix this. > There is no rule that I'm aware of that the drawer needs to be at the > top of the task. My drawers have moved down for some tasks over the > years because other things were inserted at the top of the task by org > during regular note taking. I'm not so much concerned with the drawers being at the top of the entry as their being in a well-defined place in it. Org inserts them at the start of the entry, so I'm used to them being there, and as I have `org-cycle-include-plain-lists' set, it prevents them from being hidden. Isn't it inconvenient having the clock drawer somewhere in the middle of an entry, for example if you want to adjust clock times? James -- |---|