* [BUG] Unable to use TODO(t@!) to track TODO state changes @ 2011-11-09 14:56 Jason Dunsmore 2011-11-09 15:40 ` Giovanni Ridolfi 2011-11-09 16:37 ` suvayu ali 0 siblings, 2 replies; 7+ messages in thread From: Jason Dunsmore @ 2011-11-09 14:56 UTC (permalink / raw) To: emacs-orgmode 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 This syntax appears to break the functionality, because it does neither. The state is changed with no logging or note prompt. Is this a bug? I verified that the TODO(t@/!) syntax does work as indicated in the manual. - Add note when entering state - Log timestamp when entering state - Log timestamp when exiting state This is with the latest org-mode (commit a4273cbe0e0) and Emacs 23.2.1. Thanks, Jason ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [BUG] Unable to use TODO(t@!) to track TODO state changes 2011-11-09 14:56 [BUG] Unable to use TODO(t@!) to track TODO state changes Jason Dunsmore @ 2011-11-09 15:40 ` Giovanni Ridolfi 2011-11-09 16:24 ` Jason Dunsmore 2011-11-09 16:37 ` suvayu ali 1 sibling, 1 reply; 7+ messages in thread From: Giovanni Ridolfi @ 2011-11-09 15:40 UTC (permalink / raw) To: Jason Dunsmore; +Cc: emacs-orgmode Jason Dunsmore <jasondunsmore@gmail.com> 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 ;-) cheers, Giovanni > > This syntax appears to break the functionality, because it does neither. > The state is changed with no logging or note prompt. Is this a bug? > > I verified that the TODO(t@/!) syntax does work as indicated in the > manual. > > - Add note when entering state > - Log timestamp when entering state > - Log timestamp when exiting state ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [BUG] Unable to use TODO(t@!) to track TODO state changes 2011-11-09 15:40 ` Giovanni Ridolfi @ 2011-11-09 16:24 ` Jason Dunsmore 2011-11-09 17:53 ` Dave Abrahams 0 siblings, 1 reply; 7+ messages in thread From: Jason Dunsmore @ 2011-11-09 16:24 UTC (permalink / raw) To: Giovanni Ridolfi; +Cc: emacs-orgmode Giovanni Ridolfi <giovanni.ridolfi@yahoo.it> writes: > Jason Dunsmore <jasondunsmore@gmail.com> 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. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [BUG] Unable to use TODO(t@!) to track TODO state changes 2011-11-09 16:24 ` Jason Dunsmore @ 2011-11-09 17:53 ` Dave Abrahams 0 siblings, 0 replies; 7+ messages in thread From: Dave Abrahams @ 2011-11-09 17:53 UTC (permalink / raw) To: emacs-orgmode on Wed Nov 09 2011, Jason Dunsmore <jasondunsmore-AT-gmail.com> wrote: > Giovanni Ridolfi <giovanni.ridolfi@yahoo.it> writes: > >> Jason Dunsmore <jasondunsmore@gmail.com> 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [BUG] Unable to use TODO(t@!) to track TODO state changes 2011-11-09 14:56 [BUG] Unable to use TODO(t@!) to track TODO state changes Jason Dunsmore 2011-11-09 15:40 ` Giovanni Ridolfi @ 2011-11-09 16:37 ` suvayu ali 2011-11-09 17:03 ` [PATCH] Documentation for "Tracking TODO state changes" Jason Dunsmore 1 sibling, 1 reply; 7+ messages in thread From: suvayu ali @ 2011-11-09 16:37 UTC (permalink / raw) To: Jason Dunsmore; +Cc: emacs-orgmode Hi Jason, On Wed, Nov 9, 2011 at 15:56, Jason Dunsmore <jasondunsmore@gmail.com> wrote: > 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 > > This syntax appears to break the functionality, because it does neither. > The state is changed with no logging or note prompt. Is this a bug? > > I verified that the TODO(t@/!) syntax does work as indicated in the > manual. > > - Add note when entering state > - Log timestamp when entering state > - Log timestamp when exiting state > > This is with the latest org-mode (commit a4273cbe0e0) and Emacs 23.2.1. > I believe the above should be: - Add note _with timestamp_ when entering state - Log timestamp when exiting state That said, you can simply hit C-c C-c to simply log the timestamp without a note. In other words, '@' is equivalent to '!' + note, so just enter a blank note. :) > Thanks, > Jason > HTH -- Suvayu Open source is the future. It sets us free. ^ permalink raw reply [flat|nested] 7+ messages in thread
* [PATCH] Documentation for "Tracking TODO state changes" 2011-11-09 16:37 ` suvayu ali @ 2011-11-09 17:03 ` Jason Dunsmore 2011-11-09 17:18 ` Bernt Hansen 0 siblings, 1 reply; 7+ messages in thread From: Jason Dunsmore @ 2011-11-09 17:03 UTC (permalink / raw) To: suvayu ali; +Cc: emacs-orgmode suvayu ali <fatkasuvayu+linux@gmail.com> writes: > Hi Jason, > > On Wed, Nov 9, 2011 at 15:56, Jason Dunsmore <jasondunsmore@gmail.com> wrote: >> 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 >> >> This syntax appears to break the functionality, because it does neither. >> The state is changed with no logging or note prompt. Is this a bug? >> >> I verified that the TODO(t@/!) syntax does work as indicated in the >> manual. >> >> - Add note when entering state >> - Log timestamp when entering state >> - Log timestamp when exiting state >> >> This is with the latest org-mode (commit a4273cbe0e0) and Emacs 23.2.1. >> > > I believe the above should be: > > - Add note _with timestamp_ when entering state > - Log timestamp when exiting state > > That said, you can simply hit C-c C-c to simply log the timestamp > without a note. In other words, '@' is equivalent to '!' + note, so just > enter a blank note. :) Ah, I understand now. Thanks for the explanation. Here's a patch to to the documentation: --8<---------------cut here---------------start------------->8--- diff --git a/doc/org.texi b/doc/org.texi index 4a547d0..e1167eb 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -4032,14 +4032,18 @@ also overrule the setting of this variable for a subtree Since it is normally too much to record a note for every state, Org-mode expects configuration on a per-keyword basis for this. This is achieved by -adding special markers @samp{!} (for a timestamp) and @samp{@@} (for a note) -in parentheses after each keyword. For example, with the setting +adding special markers @samp{!} (for a timestamp) or @samp{@@} (for a note +with timestamp) in parentheses after each keyword. For example, with the +setting @lisp (setq org-todo-keywords '((sequence "TODO(t)" "WAIT(w@@/!)" "|" "DONE(d!)" "CANCELED(c@@)"))) @end lisp +To record a timestamp without a note for TODO keywords configured with +@samp{@@}, just type @kbd{C-c C-c} to enter a blank note when prompted. + @noindent @vindex org-log-done you not only define global TODO keywords and fast access keys, but also --8<---------------cut here---------------end--------------->8--- ^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: [PATCH] Documentation for "Tracking TODO state changes" 2011-11-09 17:03 ` [PATCH] Documentation for "Tracking TODO state changes" Jason Dunsmore @ 2011-11-09 17:18 ` Bernt Hansen 0 siblings, 0 replies; 7+ messages in thread From: Bernt Hansen @ 2011-11-09 17:18 UTC (permalink / raw) To: Jason Dunsmore; +Cc: emacs-orgmode Jason Dunsmore <jasondunsmore@gmail.com> writes: > suvayu ali <fatkasuvayu+linux@gmail.com> writes: > >> That said, you can simply hit C-c C-c to simply log the timestamp >> without a note. In other words, '@' is equivalent to '!' + note, so just >> enter a blank note. :) > > Ah, I understand now. Thanks for the explanation. Here's a patch to to > the documentation: > Thanks Jason, The patch looks good to me. Regards, Bernt ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2011-11-09 17:59 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2011-11-09 14:56 [BUG] Unable to use TODO(t@!) to track TODO state changes Jason Dunsmore 2011-11-09 15:40 ` Giovanni Ridolfi 2011-11-09 16:24 ` Jason Dunsmore 2011-11-09 17:53 ` Dave Abrahams 2011-11-09 16:37 ` suvayu ali 2011-11-09 17:03 ` [PATCH] Documentation for "Tracking TODO state changes" Jason Dunsmore 2011-11-09 17:18 ` Bernt Hansen
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).