emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: done-ing a repeating scheduled task now inserts closed timestamp?
Date: Fri, 6 Mar 2009 17:49:44 +0100	[thread overview]
Message-ID: <E4F889D6-E90D-4D99-AE7F-FDA1649146F7@uva.nl> (raw)
In-Reply-To: <87eixduzxm.fsf@gollum.intra.norang.ca>

Hi Bernt,

to me this sounds like a pretty convincing argument *not*
to copy entries...

Another problem is that entries can have IDs, and I
would like the ID of such an entry to remain the same,
as a link target.

- Carsten

On Mar 4, 2009, at 3:26 PM, Bernt Hansen wrote:

> Carsten Dominik <dominik@science.uva.nl> writes:
>
>> On Mar 3, 2009, at 9:56 AM, Manuel Hermenegildo wrote:
>>
>>> I think a perhaps better behavior could be that the same line:
>>>
>>> ** TODO Check backups     <2009-03-05 Thu 11:00 +2d>
>>>
>>> is marked as done, then a) a *copy* is made of the TODO item, and  
>>> that
>>> copy is the one that goes to DONE and gets the CLOSED (i.e., a
>>> "normal" task is generated and updated) and b) the repeating task is
>>> shifted (without attaching anything to it, since it is a "fresh"
>>> task):
>>>
>>> ** DONE Check backups     <2009-03-05 Sat 11:00>
>>> CLOSED: [2009-03-05 Tue 07:57]
>>> - State "DONE"       from "TODO"       [2009-03-03 Tue 07:57]
>>> ** TODO Check backups     <2009-03-07 Sat 11:00 +2d>
>>>
>>> Apart from behaving more like a normal task this would have in my  
>>> mind
>>> some additional advantages: I like DONE tasks to eventually  
>>> disappear
>>> from my agenda. I do this by archiving them (to sibling). This  
>>> allows
>>> me to easily see that I have not left anything behind in past  
>>> days. I
>>> could now do this with the copied task, independently of the updated
>>> repeater. When I want to look at what I did on a certain day I hit  
>>> the
>>> handy "v" key and the archived, done tasks appear again, including
>>> those that originated from the repeater --great!  I.e., the
>>> repeater leaves behind a trail of normal tasks.
>>
>> This is an interesting, alternative proposal for repeating tasks.
>>
>> Anyone else would like to comment on this?
>
> Here are some comments :)
>
> I've thought that copying the repeated task would be useful as well  
> but
> it might not be worth the effort to get it right for the general case.
>
> My concern in copying it is I want most of the content copied too.  I
> regularly add check box lists to repeated tasks with a list of  
> things to
> do and properties to reset the check boxes.
>
> The new copied task would ideally (for me) keep the :PROPERTIES:  
> drawer
> and the content but not the :LOGBOOK: drawer.
>
> Any notes and things would go in the LOGBOOK drawer that shouldn't be
> carried forward.
>
> ,----[ before copy ]
> | ** TODO Weekly Review
> |    SCHEDULED: <2009-03-09 Mon ++1w>
> |    :LOGBOOK:...
> |    :PROPERTIES:
> |    :RESET_CHECK_BOXES: t
> |    :END:
> |
> |    - [ ] Do this
> |    - [ ] Do that
> |    - [ ] Do another thing
> |
> |    Skip these
> |
> |    - [ ] Used to be Important task 1
> |    - [ ] Used to be Important task 2
> |
> | ** Next task
> `----
>
> After copying for repeat I'd like the new task to be:
>
> ,----[ after copy (new copied task) ]
> | ** TODO Weekly Review
> |    SCHEDULED: <2009-03-16 Mon ++1w>
> |    :PROPERTIES:
> |    :RESET_CHECK_BOXES: t
> |    :END:
> |
> |    - [ ] Do this
> |    - [ ] Do that
> |    - [ ] Do another thing
> |
> |    Skip these
> |
> |    - [ ] Used to be Important task 1
> |    - [ ] Used to be Important task 2
> |
> | ** Next task
> `----
>
> The DONE task should probably have the check boxes retained checked,  
> and
> the new copy has the checkboxes cleared.  This seems like it could get
> overly complicated real fast. :(
>
> I could also see this for more involved tasks where you want to
> propagate the subtree too (like my bookkeeping task has lots of steps
> which I keep as separate tasks below the repeated tasks).
>
> Copying the level 2 task (Q2 Accounting) would need to copy all of the
> subtasks in the tree and strip out the :LOGBOOK: drawers from the  
> copy.
>
>
> ------------------------------------------------------------------------
> ** TODO Q2 Accounting						       :PROJECT:
>   DEADLINE: <2009-04-30 Thu +1y>
>   :PROPERTIES:
>   :Effort:   3:00
>   :ORDERED: t
>   :END:
> *** TODO January Accounting [0/17] [0%] 					  :NEXT:
>    :LOGBOOK:...
>    :PROPERTIES:
>    :RESET_CHECK_BOXES: t
>    :END:
>      - [ ] Enter Personal Expenses
>      - [ ] Enter credit card charges
>      - [ ] Balance credit card statement
>      - [ ] Enter Cheques and payments
>      - [ ] Enter Invoices - Receive Payments
>      - [ ] Balance Bank accounts
>      ...
>      - [ ] Get USD value at month end
>      - [ ] Foreign Exchange Adjustments
>      - [ ] Print Reports
>      - [ ] File receipts and reports
>
> *** TODO February Accounting [0/17] [0%]...
> *** TODO Mileage Jan - Mar
>     :PROPERTIES:...
>
> |   | Date        | Car     |  From |    To | Total | Where      |  
> Why                       |
> |---+-------------+---------+-------+-------+-------+------------ 
> +---------------------------|
> | # |             |         |       |       |       |             
> |                           |
>
> *** TODO March Accounting [0/17] [0%]...
> **** TODO Record personal mileage details...
> *** TODO GST [0/3] [0%]
>    :LOGBOOK:...
>    :PROPERTIES:
>    :Effort:   0:10
>    :RESET_CHECK_BOXES: t
>    :END:
>
>   - [ ] Print GST Reports
>   - [ ] File receipts and reports
>   - [ ] File GST Tax Return
>
> ------------------------------------------------------------------------
>
> After writing all this... it would probably be easier just to extract
> out the :LOGBOOK: entries and duplicate the subtree structure for the
> completed tasks.  (ie. the copy is the completed task and just
> reschedule the existing task into the future like we do now)
>
> It might be nice to have a way to have some subtasks in the tree _not_
> be copied.  If you have something to remember for this upcoming  
> repeated
> task you create a subtask for that... but you won't need that in the
> repeated task.
>
> Regards,
> Bernt
>

  reply	other threads:[~2009-03-06 17:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03  1:29 Samuel Wales
2009-03-03  8:56 ` Manuel Hermenegildo
2009-03-04 13:03   ` Carsten Dominik
2009-03-04 14:26     ` Bernt Hansen
2009-03-06 16:49       ` Carsten Dominik [this message]
2009-03-07 21:26         ` Bernt Hansen
2009-03-08 18:25         ` Manuel Hermenegildo
2009-03-09  7:41           ` Carsten Dominik
     [not found]             ` <18870.13851.387945.968246@clip.dia.fi.upm.es>
2009-03-11 14:15               ` Carsten Dominik
2009-03-04 13:15   ` Bernt Hansen
2009-03-04 13:30   ` Carsten Dominik
2009-03-04  6:17 ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E4F889D6-E90D-4D99-AE7F-FDA1649146F7@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).