From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: in-buffer settings for priorities Date: Tue, 29 May 2007 17:27:32 +0200 Message-ID: References: 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 1Ht4Dh-0003on-KX for emacs-orgmode@gnu.org; Tue, 29 May 2007 12:06:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ht4Dg-0003oL-RX for emacs-orgmode@gnu.org; Tue, 29 May 2007 12:06:49 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ht4Dg-0003oF-NY for emacs-orgmode@gnu.org; Tue, 29 May 2007 12:06:48 -0400 Received: from korteweg.uva.nl ([146.50.98.70]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ht4Dg-0006I4-2k for emacs-orgmode@gnu.org; Tue, 29 May 2007 12:06:48 -0400 In-Reply-To: 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: Dmitri Minaev Cc: emacs-orgmode@gnu.org On May 22, 2007, at 10:07, Dmitri Minaev wrote: > On 5/21/07, Carsten Dominik wrote: > >> > 1. When the state of an item changes from nothing to the first in >> the >> > TODO sequence, no note is taken and the state change is not logged. >> Is >> > this by design? >> >> Yes. > > I should have upgraded more often :). In 4.60, which I used prior to > the last upgrade, this feature was absent. Is there a way to bring the > old behaviour back? Yes. Turns out it was not a feature but a bug, I was mistaken. Sorry about that. Fixed for 4.76. > >> Actually, lets just take your patch > > I hope the reason was not that I was obstinate :) No. But I needed time to understand exactly what it did, and to see if there is anything missing (there was, a side issue with `org-get-current-options). First I wanted to wait until the next release, but then I changed my mind. - Carsten