From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Abrahams Subject: Re: [BUG] Unable to use TODO(t@!) to track TODO state changes Date: Wed, 09 Nov 2011 12:53:00 -0500 Message-ID: References: <8762itbazi.fsf@riotblast.dunsmor.com> <83pqh1pam5.fsf@yahoo.it> <87ty6d9sbp.fsf@riotblast.dunsmor.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:48634) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ROCQf-0004Ie-Tc for emacs-orgmode@gnu.org; Wed, 09 Nov 2011 12:59:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ROCQe-0004M4-HJ for emacs-orgmode@gnu.org; Wed, 09 Nov 2011 12:59:17 -0500 Received: from lo.gmane.org ([80.91.229.12]:45168) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ROCQe-0004M0-B1 for emacs-orgmode@gnu.org; Wed, 09 Nov 2011 12:59:16 -0500 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1ROCQc-0002oX-SP for emacs-orgmode@gnu.org; Wed, 09 Nov 2011 18:59:14 +0100 Received: from 207-172-223-249.c3-0.smr-ubr3.sbo-smr.ma.static.cable.rcn.com ([207.172.223.249]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 09 Nov 2011 18:59:14 +0100 Received: from dave by 207-172-223-249.c3-0.smr-ubr3.sbo-smr.ma.static.cable.rcn.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 09 Nov 2011 18:59:14 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org on Wed Nov 09 2011, Jason Dunsmore wrote: > Giovanni Ridolfi writes: > >> Jason Dunsmore writes: >> >> Hi, _Jason, >> >>> After reading http://orgmode.org/org.html#Tracking-TODO-state-changes, >>> I expected the "@!" TODO syntax, eg. TODO(t@!), to do the following: >>> >>> - Log timestamp when entering state >>> - Add note when entering state >> >> Well the TODO(t@!) syntax seems not to be allowed. >> >> It is your expectation, I'd say a feature request ;-) > > I thought it was a bug because each of the special characters is > described in the manual as being an individual feature and it isn't > documented that only certain combinations of features work together. There's definitely a bug; either in the manual or code (or both ;->). -- Dave Abrahams BoostPro Computing http://www.boostpro.com