From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manuel Hermenegildo Subject: Re: done-ing a repeating scheduled task now inserts closed timestamp? Date: Sun, 8 Mar 2009 19:25:28 +0100 Message-ID: <18868.3480.497640.673958@clip.dia.fi.upm.es> References: <20524da70903021729g43632321u711b26a43f5b26bf@mail.gmail.com> <9062-Tue03Mar2009095608+0100-herme@clip.dia.fi.upm.es> <1DF4862F-AD7B-4219-80EF-15483A28EE5E@uva.nl> <87eixduzxm.fsf@gollum.intra.norang.ca> Reply-To: Manuel Hermenegildo Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LgZYp-0003bL-HK for emacs-orgmode@gnu.org; Mon, 09 Mar 2009 03:06:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LgZYk-0003at-7g for emacs-orgmode@gnu.org; Mon, 09 Mar 2009 03:06:02 -0400 Received: from [199.232.76.173] (port=43589 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LgZYk-0003am-1W for emacs-orgmode@gnu.org; Mon, 09 Mar 2009 03:05:58 -0400 Received: from relay.fi.upm.es ([138.100.8.77]:50492 helo=relay4.fi.upm.es) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LgZYh-00078a-QP for emacs-orgmode@gnu.org; Mon, 09 Mar 2009 03:05:57 -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: Carsten Dominik Cc: Bernt Hansen , emacs-orgmode@gnu.org Sorry for the pause (I was pretty busy last week): > Another idea to get this: > > Turn on state change notes or at least time stamps. Either globally, > or locally for this entry with a LOGGING property: > > ** TODO Check backups > SCHEDULED: <2009-03-05 Thu 11:00 +2d> > :PROPERTIES: > :LOGGING: DONE(!) > :END: > > (yes, scheduled, thanks Bernt...) > Then each time you go through the DONE state, a time stamp > will be recorded like this (I am assuming that you have > org-log-into-drawer set...) > > ** TODO Check backups > SCHEDULED: <2009-04-28 Tue 11:00 +2d> > :LOGBOOK: > - State "DONE" from "TODO" [2009-03-04 Wed 14:25] > - State "DONE" from "TODO" [2009-03-02 Mon 14:25] > - State "DONE" from "TODO" [2009-02-28 Sat 14:25] > - State "DONE" from "TODO" [2009-02-26 Thu 14:25] > :END: > :PROPERTIES: > :LOGGING: DONE(!) > > In the agenda, if you press `C-u l', these state notes > will become visible. > > I believe this will take care of it, right?? Yes, this is much closer than what one would like. And having those "done states" together could be useful. However, I have to say that though that after trying to adapt to these settings I cannot bend my mind to find the behavior comfortable, specially comparing to how normal tasks work. For me it is confusing that when I do "t" on such a task it goes to "DONE" as I would expect (i.e., like a normal TODO task) but when I refresh the agenda it disappears (unlike normal DONE tasks, at least with my settings --I use archiving to make done tasks disappear and "v" to toggle viewing archived tasks). Actually, I think it goes to DONE only for the first repeat, for the following repeats it stays as TODO, at least with my settings. I guess I can use org-agenda-skip-scheduled-if-done to get the non-repeating tasks to disappear also when marked as done (so that there is more orthogonality) but, again, it will only work if I remember to use "SCHEDULED" for them, and, also, I do not want them to disappear yet! ;-) Also, I feel I have to remember too many things for, say, a simple weekly meeting: a) putting SCHEDULED, b) setting the properties, c) making sure org-log-into-drawer is set, etc. Ideally any simple TODO entry with a repeating timestamp should behave well when marked as done, right? > to me this sounds like a pretty convincing argument *not* > to copy entries... Yes, I guess this is a problem (although in my case all repeating entries --which are regular meetings, classes, birthdays, etc.-- are typically one liners so it would not make a difference if they were copied...). Sorry to insist, but I still think copying the tasks would produce a more orthogonal behavior. Perhaps it could be made optional? Man -- ------------------------------------------------------------------------------- Manuel Hermenegildo | Prof., C.S.Dept., T.U. Madrid (UPM) Director, IMDEA-Software and CLIP Group | +34-91-336-7435 (W) -352-4819 (Fax) -------------------------------------------------------------------------------