From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id +JNuCqTrrF8ZagAA0tVLHw (envelope-from ) for ; Thu, 12 Nov 2020 08:00:36 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id QOwiBqTrrF/3fwAAB5/wlQ (envelope-from ) for ; Thu, 12 Nov 2020 08:00:36 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id E058D9408EE for ; Thu, 12 Nov 2020 08:00:34 +0000 (UTC) Received: from localhost ([::1]:45414 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kd7Wy-0002uR-63 for larch@yhetil.org; Thu, 12 Nov 2020 03:00:32 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:60450) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kd7W3-0002tl-7h for emacs-orgmode@gnu.org; Thu, 12 Nov 2020 02:59:35 -0500 Received: from mail-lj1-x22f.google.com ([2a00:1450:4864:20::22f]:46762) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kd7W1-00030s-BL for emacs-orgmode@gnu.org; Thu, 12 Nov 2020 02:59:34 -0500 Received: by mail-lj1-x22f.google.com with SMTP id h23so4989927ljg.13 for ; Wed, 11 Nov 2020 23:59:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZmlArzqW8bXjkohX7R1cHG+jtYyw9isXBz4431/dKb4=; b=lKqN60cT4yLwsZG7drtm5EZ29v/HBQC03IFvdNUrxm+4aq70kMWmdT1XO9Eod2t4L9 6gmLjmFp+b6vBWXr3n+pixw8VSZuVLs1DD8/Z2BuNvmvWVubvoRfAtLoglwI7CM0fKtl lFhomGRkM7f52qm+X3HrbOYCSQ+4Y4i+b/OoFjpKS3aJ2eozC4fpWUxB1kOMNPp6RMzN k9OGK37M7JmsDQLzhmYIVVw/LYJWFL8UNbs2T4BeeDHRTpa5R47XekMXZy2FZTmMTNSJ btf4f2sd+3q2KHck2PMnvHx/Xru0ihGRUBqi/hj+THrrln3KUdeHhrviDeE0NCXQK/tf UeUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZmlArzqW8bXjkohX7R1cHG+jtYyw9isXBz4431/dKb4=; b=myIoR/33J1vLunldlx6z0btrJjwh0hGCt85nFG7E/7/cfWV3B8rhufJmnmlApGC0q2 yMuX62M7V29BxdBIQT1ZsJPnZ1HAVE0D5O4x2n6TZttb7nb8SJEWB5AXxdcvRJ7cBypG b0Wfj2ivJbwQ5ZgmL+f3Jec5D7RMjIVi21yzgkSX+Rw0c9/Tqjuaaim2iMzJE4ZXMT+h ty/GlNL0WwUhOGJno+kOC4Sxwl2EZ09YdayHuKwQvO5Zue1vzJEiUssRAJ7TkE45SdBw k6Q9Xx50eFEuODxyWdAyw4AT03AOdCHWluqkzPapHQJ6Xf+qfiwcgJex6ZOTdsdcq+Va oPFA== X-Gm-Message-State: AOAM531Jaj7tUYMg3vTknsi4m7Rw6+aZV0nuE4+G4i6KKK2AC7E8omGD hkIBDuMVIN+pAX+VgQw62hsxkMKZGTqepBCATts= X-Google-Smtp-Source: ABdhPJxjkIa0kdADra52j4cIdKMcvYg1Hzme4+7O5pVDoBm7lcO7Lh0H7IjYHmYnUazxMV3wAY0f5AJPqoqY1d6VkPc= X-Received: by 2002:a2e:5749:: with SMTP id r9mr6749671ljd.255.1605167970816; Wed, 11 Nov 2020 23:59:30 -0800 (PST) MIME-Version: 1.0 References: <87lffj7zss.fsf@localhost> In-Reply-To: <87lffj7zss.fsf@localhost> From: Gerardo Moro Date: Thu, 12 Nov 2020 09:59:19 +0200 Message-ID: Subject: Re: Archiving repeated tasks under corresponding date tree for each repeated item To: Ihor Radchenko Content-Type: multipart/alternative; boundary="000000000000b4986d05b3e44aba" Received-SPF: pass client-ip=2a00:1450:4864:20::22f; envelope-from=gerardomoro37@gmail.com; helo=mail-lj1-x22f.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=lKqN60cT; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -1.71 X-TUID: ZFlVPncfAIhi --000000000000b4986d05b3e44aba Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks, Ihor. Indeed, that is an excellent feature of agenda. I use it sometimes to visualize what I have DONE during the week on the sopt. What I aim to accomplish however is a more systematic log of all the DONE tasks, this is, to have an archive file where to archive all tasks. This file is in the format: 2020 2020-01-01 DONE task1 2020-01-12 DONE task2 2020-02-01 CANCELLED task3 So it is indeed a datetree file where I can revisit the past :) if you will= . The problem with habits and repeated tasks is that they don't get archived when DONE... They get archived once the task is cancelled or completed as a whole, all under the day the task stopped continuing, under which I have all the logged individual completion. It would be desirable to have each "completion" archived under its corresponding datetree, it is more meaningful :) Hope it is clear now, thanks so much for any help! GM So even if I have beeng doing the task every wednesday for a year, it won't be archived El mar., 3 nov. 2020 a las 7:53, Ihor Radchenko () escribi=C3=B3: > > It would be great if each of these individual "task > > happenings" were archived under the date and time they were completed > > individually, and not just all as one block. This way I could get weekl= y > > reviews that take those into account. > > What about trying to do your weekly review using org-agenda? You can > show the task every day you complete it by enabling org-agenda-log-mode > in your weekly agenda (v l). If your tasks are also archived regularly, > you may also need "v A" to include archive files into agenda view. > > Best, > Ihor > > > Gerardo Moro writes: > > > Dear all, > > > > I am resending this as I believe it's a useful concept to implement, > > especially by those who track their tasks and do weekly/monthly reviews= . > > > > When I archive a repeated task (let's say, a learning project of 15 > minutes > > every Wednesday day for 2 months), the task gets archived in a date tre= e > > all under the day it was closed (cancelled) as a whole. This means that > all > > the LOGGED individual instances of repetition are archived on the day t= he > > project got completed. It would be great if each of these individual > "task > > happenings" were archived under the date and time they were completed > > individually, and not just all as one block. This way I could get weekl= y > > reviews that take those into account. Not sure if I made myself > understood! > > :)) > > > > Thanks! > > G > --000000000000b4986d05b3e44aba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks, Ihor.
Indeed, that is an excellent feature of = agenda. I use it sometimes=C2=A0 to visualize what I have DONE during the w= eek on the sopt.
What I aim to accomplish however is a more syste= matic log of all the DONE tasks, this is, to have an archive file where to = archive all tasks.
This file is in the format:

2020
=C2=A0 =C2=A02020-01-01 DONE task1
=C2=A0 = =C2=A02020-01-12 DONE task2
=C2=A0 =C2=A02020-02-01 CANCELLED= task3

So it is indeed a datetree file where I= can revisit the past :) if you will.
The problem with habits and= repeated tasks is that they don't get archived when DONE...=C2=A0
They get archived once the task is cancelled or completed as a whole,= all under the day the task stopped continuing, under which I have all the = logged individual=C2=A0completion.
It would be desirable to have = each "completion" archived under its corresponding datetree, it i= s more meaningful :)

Hope it is clear now, thanks = so much for any help!
GM
So even if I have beeng doing = the task every wednesday for a year, it won't be archived
El mar.,= 3 nov. 2020 a las 7:53, Ihor Radchenko (<yantar92@gmail.com>) escribi=C3=B3:
> It would be great if each of these = individual "task
> happenings" were archived under the date and time they were compl= eted
> individually, and not just all as one block. This way I could get week= ly
> reviews that take those into account.

What about trying to do your weekly review using org-agenda? You can
show the task every day you complete it by enabling org-agenda-log-mode
in your weekly agenda (v l). If your tasks are also archived regularly,
you may also need "v A" to include archive files into agenda view= .

Best,
Ihor


Gerardo Moro <gerardomoro37@gmail.com> writes:

> Dear all,
>
> I am resending this as I believe it's a useful concept to implemen= t,
> especially by those who track their tasks and do weekly/monthly review= s.
>
> When I archive a repeated task (let's say, a learning project of 1= 5 minutes
> every Wednesday day for 2 months), the task gets archived in a date tr= ee
> all under the day it was closed (cancelled) as a whole. This means tha= t all
> the LOGGED individual instances of repetition are archived on the day = the
> project got completed. It would be great if each of these individual &= quot;task
> happenings" were archived under the date and time they were compl= eted
> individually, and not just all as one block. This way I could get week= ly
> reviews that take those into account. Not sure if I made myself unders= tood!
> :))
>
> Thanks!
> G
--000000000000b4986d05b3e44aba--